On 16. 12. 2013, at 15:12, Rafael Benevides <benevides(a)redhat.com> wrote:
Ok, so can I assume that I have green flag to promote staged
Archetypes and merge the PR as soon as we have it on Maven Central?
Em 16/12/13 11:54, Fred Bricon escreveu:
> As I explained on IRC, this is actually a regression
(
https://issues.jboss.org/browse/JBIDE-16292) caused by the way we now handle a given
project type backed by archetypes with different GAV (only V changed before)
>
> Shouldn't be a problem if EAP 6.2 maintained API compatibility with 6.1
>
>
> Le lundi 16 décembre 2013 12:39:40, Rafael Benevides a écrit :
>> Hi Martin,
>>
>> That's a kind weird because in stacks file 6.1.1 points to older 7.1.3
>> Archetypes:
>>
https://github.com/rafabene/jdf-stack/blob/eap62Archetypes/stacks.yaml#L2...
>>
>> ,6.2.0 points to the new archetypes:
>>
https://github.com/rafabene/jdf-stack/blob/eap62Archetypes/stacks.yaml#L2...
>>
>> and we don't have wildfly in stacks.yaml.
>>
>> Isn't this runtime/archetypes relationship being managed by jbds instead ?
>>
>> Em 16/12/13 09:24, Martin Malina escreveu:
>>> Hi Rafael,
>>>
>>> I verified that when using stacks.yaml from your PR EAP 6.1.1 and 6.2
>>> both use the new java ee web archetype version 6.2.0 and JBoss AS
>>> 7.1.1 and Wildfly and anything else uses the older 7.1.3. I was able
>>> to build & deploy & view the archetype without any problems.
>>>
>>> Just to make sure: Is it intentional that EAP 6.1.1 also uses this
>>> new archetype?
>>>
>>> Asa far as I can see this update is only to this one archetype,
>>> correct? Other archetypes remain unchanged.
>>>
>>> Thanks,
>>> Martin
>>>
>>> On 13. 12. 2013, at 15:40, Rafael Benevides <benevides(a)redhat.com
>>> <mailto:benevides@redhat.com>> wrote:
>>>
>>>> Done!
>>>>
>>>>
https://github.com/jboss-jdf/jdf-stack/pull/31
>>>>
>>>>
>>>> Em 13/12/13 12:16, Martin Malina escreveu:
>>>>> What I will need is an altered stacks.yaml to point to the new
>>>>> archetype that I want to verify, right?
>>>>> And then I can start JBDS with -Dorg.jboss.tools.stacks.url_stacks=…
>>>>> If I can achieve that, that would be perfect.
>>>>>
>>>>> -Martin
>>>>>
>>>>> On 13. 12. 2013, at 15:03, Rafael Benevides <benevides(a)redhat.com
>>>>> <mailto:benevides@redhat.com>> wrote:
>>>>>
>>>>>> More or less.
>>>>>>
>>>>>> This test that I made are automated by JUnit, so it's part of
the
>>>>>> build.
>>>>>>
>>>>>> There's also mention on how to test on the contributing.md
(step 8
>>>>>> and 9) :
>>>>>>
https://github.com/jboss-developer/jboss-eap-archetypes/blob/master/CONTR...
>>>>>>
>>>>>>
>>>>>> Em 13/12/13 11:57, Pete Muir escreveu:
>>>>>>> I think Martin could do with steps to configure the staging
repo,
>>>>>>> and then to alter JBoss Central to use the archetype.
>>>>>>>
>>>>>>> Is this documented somewhere?
>>>>>>>
>>>>>>> On 13 Dec 2013, at 13:53, Rafael Benevides
<benevides(a)redhat.com
>>>>>>> <mailto:benevides@redhat.com>> wrote:
>>>>>>>
>>>>>>>> Well,
>>>>>>>>
>>>>>>>> My tests consists in creating a project and build/deploy
the
>>>>>>>> created project using the CLI.
>>>>>>>> I'm not sure if it's sufficient for an
Archerype.
>>>>>>>>
>>>>>>>>
>>>>>>>> Em 13/12/13 11:51, Martin Malina escreveu:
>>>>>>>>> Yes, I can test it, but only on Monday.
>>>>>>>>> Also, I will need Rafael to provide steps to test
this. Can you
>>>>>>>>> do that, Rafael?
>>>>>>>>>
>>>>>>>>> -Martin
>>>>>>>>>
>>>>>>>>> On 13. 12. 2013, at 14:39, Pete Muir
<pmuir(a)redhat.com
>>>>>>>>> <mailto:pmuir@redhat.com>> wrote:
>>>>>>>>>
>>>>>>>>>> Martin, are you able to test this out?
>>>>>>>>>>
>>>>>>>>>> On 13 Dec 2013, at 13:18, Rafael Benevides
>>>>>>>>>> <benevides(a)redhat.com
<mailto:benevides@redhat.com>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi guys.
>>>>>>>>>>>
>>>>>>>>>>> I did:
>>>>>>>>>>>
>>>>>>>>>>> 1 - Prepared EAP 6.2 Archetypes:
>>>>>>>>>>>
>>>>>>>>>>> Synch:
>>>>>>>>>>>
https://github.com/jboss-developer/jboss-eap-archetypes/commit/d532e54d6c...
>>>>>>>>>>> Tag:
>>>>>>>>>>>
https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2....
>>>>>>>>>>>
>>>>>>>>>>> 2- Release EAP 6.2 Archetype in a staged
repo:
>>>>>>>>>>>
https://repository.jboss.org/nexus/content/repositories/jboss_releases_st...
>>>>>>>>>>>
>>>>>>>>>>> Now I need to know if will we let QE team
work on this
>>>>>>>>>>> release or if should I promote this
Archetypes based on the
>>>>>>>>>>> tests I made. I'm asking that because I
consider it isn't a
>>>>>>>>>>> community release anymore so I think QE
production tests
>>>>>>>>>>> should handle it.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>>> Em 09/12/13 17:43, Rafael Benevides
escreveu:
>>>>>>>>>>>>>> Hi guys,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Sorry for the wide audience but
since EAP 6.2 was released
>>>>>>>>>>>>>> last week, the archetypes (
>>>>>>>>>>>>>>
https://github.com/jboss-developer/jboss-eap-archetypes )
>>>>>>>>>>>>>> was not even mentioned.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Since Archetypes are part of the
stacks, I'd like to know
>>>>>>>>>>>>>> who in productization team should
handle the archetypes?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> WFK 2.4 Archetypes was released
to Maven Central after a
>>>>>>>>>>>>>> period in a nexus staged
repository being tested by WFK QE
>>>>>>>>>>>>>> team. Can I assume that we will
have the same approach for
>>>>>>>>>>>>>> EAP 6.2 Archetypes? If so, there
are some steps missing
>>>>>>>>>>>>>> that it's needed and the time
is flying.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 1 - Prepare the EAP 6.2
Archetypes based on a EAP 6.2
>>>>>>>>>>>>>> Quickstarts tag
>>>>>>>>>>>>>> 2 - Release EAP 6.2 Archetype in
a staged repo
>>>>>>>>>>>>>> 3 - QE test/fix cycle on the
Archetypes
>>>>>>>>>>>>>> 4 - Promote the stage repo
>>>>>>>>>>>>>> 5 - Ask to Sonatype to include
this new archetype groupId
>>>>>>>>>>>>>> (org.jboss.archetype.eap) to be
synched with Maven Central
>>>>>>>>>>>>>> 6 - Update stacks.yaml
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> So the purpose of this email is
bring EAP Archetypes under
>>>>>>>>>>>>>> discussion (at least for this
release) since Pete is
>>>>>>>>>>>>>> preparing a plan that should work
for next releases.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Rafael Benevides | Senior
Software Engineer
>>>>>>>>>>>>>> JBoss Developer
>>>>>>>>>>>>>> M: +55-61-9269-6576
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <Mail Attachment.jpeg>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Better technology. Faster
innovation. Powered by community
>>>>>>>>>>>>>> collaboration.
>>>>>>>>>>>>>> See how it works at
www.redhat.com <
http://www.redhat.com/>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <Mail Attachment.png>
<Mail Attachment.png>
>>>>>>>>> --
>>>>>>>>> Martin Malina
>>>>>>>>> JBoss QA Engineer
>>>>>>>>> Red Hat Czech s.r.o.
>>>>>>>>> Purkynova 99
>>>>>>>>> 612 45 Brno, Czech Republic
>>>>>>>>>
>>>>>>>>> Tel.: +420 532 294 265
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Martin Malina
>>>>> JBoss QA Engineer
>>>>> Red Hat Czech s.r.o.
>>>>> Purkynova 99
>>>>> 612 45 Brno, Czech Republic
>>>>>
>>>>> Tel.: +420 532 294 265
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>> --
>>> Martin Malina
>>> JBoss QA Engineer
>>> Red Hat Czech s.r.o.
>>> Purkynova 99
>>> 612 45 Brno, Czech Republic
>>>
>>> Tel.: +420 532 294 265
>>>
>>>
>>>
>>>
>>
>
>
--
Martin Malina
JBoss QA Engineer
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno, Czech Republic
Tel.: +420 532 294 265