During the Archetypes tests I had problem building the Enterprise
version because BOMs 1.0.4.Final-redhat-wfk-1 wasn't released yet.
We had similar problem like the one opened by Max Andersen on
https://issues.jboss.org/browse/JDF-230 - I'm adding him to this thread.
Shouldn't in this case use the BOM from WFK 2.1
http://maven.repository.redhat.com/techpreview/wfk2/2.1.0/maven-repositor...
? - But that would cause another problem with the actual archetypes
because the groupId was changed from org.jboss.bom to
com.redhat.jboss.wfk.boms - The archetype bom references
https://github.com/rafabene/jboss-as-archetype/blob/3d9a6f3d9313515354b74...
I think that we'll need to keep EAP bom '1.0.2.Final-redhat-1' like
described on JDF-230 and them think a little bit more on how to have
these archetypes aligned to WFK.
Em 18/04/13 09:57, Rafael Benevides escreveu:
Makes sense! I'll update the PR.
Em 18/04/13 09:13, Pete Muir escreveu:
> Right, that one is WFK, so it should track WFK.
>
> On 18 Apr 2013, at 04:09, Karel Piwko <kpiwko(a)redhat.com> wrote:
>
>> My understanding of the situation was the archetype contains it its
>> metadata
>> line [1]:
>>
>> Target Product: WFK
>>
>> Therefore, archetype should take precedence of WFK BOM version over
>> EAP BOM
>> version if it exists for particular BOM.
>>
>> So BOM version will differ per archetype. Sometimes, we'll even have
>> two
>> versions, as products do no distribute all BOM set anymore.
>>
>> Karel
>>
>> [1]
>>
https://github.com/rafabene/jboss-as-archetype/blob/3d9a6f3d9313515354b74...
>>
>>
>>
>> On Wed, 17 Apr 2013 13:28:44 -0300
>> Rafael Benevides <benevides(a)redhat.com> wrote:
>>
>>> Today Karel made a comment on a Archetype PR that needs an answer:
>>>
>>> The Archetypes uses the 1.0.2.Final-redhat-1 version to as the
>>> "jboss-bom-enterprise-version" from EAP
>>>
>>> But Karel asked if shouldn't it use 1.0.4.Final-redhat-wfk-1 from WFK?
>>>
>>> What it the supposed version for "jboss-bom-enterprise-version" in
>>> Archetypes ?
>>>
>>> Thanks
>>>