I found a bug in m2e that drove me nuts for a while, delaying my
testing for a while :
It is here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_st...
Em 04-01-2013 07:53, Fred Bricon escreveu:
> I can't find the new richfaces archetype in the staging repo
>
https://issues.jboss.org/browse/JBIDE-13341?focusedCommentId=12743477&...
> So obviously can't vet it :/
>
> Le vendredi 4 janvier 2013 00:24:58, Brian Leathem a écrit :
>> I updated this for RichFaces, created the PR and associated jiras:
>>
https://issues.jboss.org/browse/JDF-179
>>
https://issues.jboss.org/browse/JBIDE-13341
>>
>> Does anyone from QA wants to take a look before I publish the artifact
>> out of the staging repository.
>>
>> Brian
>>
>> On 12-12-24 06:33 AM, Pete Muir wrote:
>>> RichFaces/Aerogear teams,
>>>
>>> Due to a mixup [1] the archetypes didn't get properly checked for EAP
6.0.1. As a result they are still using versions of the BOM which aren't in the EAP
6.0.1 Maven repo.
>>>
>>> Please can you update
src/main/resources/META-INF/maven/archetype-resources.xml and make sure that the
jboss-bom-enterprise-version property is set to the 1.0.2.Final-redhat-1:
>>>
>>> <requiredProperty
key="jboss-bom-enterprise-version">
>>> <defaultValue>1.0.2.Final-redhat-1</defaultValue>
>>> </requiredProperty>
>>>
>>> We'll then need you to do a release, and send a pull to stacks.yaml with
the new version of your archetype.
>>>
>>> Thanks!
>>>
>>> Pete
>>>
>>> [1] The EAP team weren't checking the archetypes were working, it only
got picked up by JBDS QE. We've asked the EAP team to start testing the archetypes as
part of the acceptance tests, and notify the JDF team (me and Rafael) of any issues, so
that we can go ahead and fix the problems.
>
> _______________________________________________
> jdf-dev mailing list
> jdf-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jdf-dev