<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
EAP 6.2.0 Archetypes are at maven central:
<a class="moz-txt-link-freetext" href="http://search.maven.org/#search%7Cga%7C1%7Corg.jboss.archetype.eap">http://search.maven.org/#search%7Cga%7C1%7Corg.jboss.archetype.eap</a><br>
<br>
Archetypes repo tag:
<a class="moz-txt-link-freetext" href="https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA">https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA</a><br>
<br>
Stacks updated:
<a class="moz-txt-link-freetext" href="https://github.com/jboss-developer/jboss-stacks/commit/cc6ac1ac6">https://github.com/jboss-developer/jboss-stacks/commit/cc6ac1ac6</a><br>
<br>
<br>
<div class="moz-cite-prefix">Em 9/2/14, 11:52, Rafael Benevides
escreveu:<br>
</div>
<blockquote cite="mid:5405D990.9030606@redhat.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
I'll check why those archetypes were not synchronized with Maven
Central...<br>
<br>
<div class="moz-cite-prefix">Em 12/17/13, 11:37, Rafael Benevides
escreveu:<br>
</div>
<blockquote cite="mid:52B05395.1080702@redhat.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
Archetypes released at: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://repository.jboss.org/nexus/content/groups/public/org/jboss/archetype/eap/">https://repository.jboss.org/nexus/content/groups/public/org/jboss/archetype/eap/</a><br>
<br>
Now I'll wait to it be available on Maven Central so I can merge
stacks.yaml<br>
<br>
<br>
Thanks<br>
<br>
<div class="moz-cite-prefix">Em 17/12/13 05:29, Martin Malina
escreveu:<br>
</div>
<blockquote
cite="mid:67CDC314-7766-43CB-AA45-2DF1850EB561@redhat.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<br>
<div>
<div>On 16. 12. 2013, at 15:12, Rafael Benevides <<a
moz-do-not-send="true"
href="mailto:benevides@redhat.com">benevides@redhat.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><br>
Thanks Fred and Martin!<br>
</blockquote>
<div><br>
</div>
You’re welcome.</div>
<div><br>
<blockquote type="cite">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?<br>
</blockquote>
<div><br>
</div>
Yes, I believe so.</div>
<div><br>
</div>
<div>-Martin</div>
<div><br>
<blockquote type="cite"><br>
<br>
Em 16/12/13 11:54, Fred Bricon escreveu:<br>
<blockquote type="cite">As I explained on IRC, this is
actually a regression (<a moz-do-not-send="true"
href="https://issues.jboss.org/browse/JBIDE-16292">https://issues.jboss.org/browse/JBIDE-16292</a>)
caused by the way we now handle a given project type
backed by archetypes with different GAV (only V changed
before)<br>
<br>
Shouldn't be a problem if EAP 6.2 maintained API
compatibility with 6.1<br>
<br>
<br>
Le lundi 16 décembre 2013 12:39:40, Rafael Benevides a
écrit :<br>
<blockquote type="cite">Hi Martin,<br>
<br>
That's a kind weird because in stacks file 6.1.1
points to older 7.1.3<br>
Archetypes:<br>
<a moz-do-not-send="true"
href="https://github.com/rafabene/jdf-stack/blob/eap62Archetypes/stacks.yaml#L2190-L2199">https://github.com/rafabene/jdf-stack/blob/eap62Archetypes/stacks.yaml#L2190-L2199</a>
<br>
<br>
,6.2.0 points to the new archetypes:<br>
<a moz-do-not-send="true"
href="https://github.com/rafabene/jdf-stack/blob/eap62Archetypes/stacks.yaml#L2229-L2234">https://github.com/rafabene/jdf-stack/blob/eap62Archetypes/stacks.yaml#L2229-L2234</a>
<br>
<br>
and we don't have wildfly in stacks.yaml.<br>
<br>
Isn't this runtime/archetypes relationship being
managed by jbds instead ?<br>
<br>
Em 16/12/13 09:24, Martin Malina escreveu:<br>
<blockquote type="cite">Hi Rafael,<br>
<br>
I verified that when using stacks.yaml from your PR
EAP 6.1.1 and 6.2<br>
both use the new java ee web archetype version 6.2.0
and JBoss AS<br>
7.1.1 and Wildfly and anything else uses the older
7.1.3. I was able<br>
to build & deploy & view the archetype
without any problems.<br>
<br>
Just to make sure: Is it intentional that EAP 6.1.1
also uses this<br>
new archetype?<br>
<br>
Asa far as I can see this update is only to this one
archetype,<br>
correct? Other archetypes remain unchanged.<br>
<br>
Thanks,<br>
Martin<br>
<br>
On 13. 12. 2013, at 15:40, Rafael Benevides <<a
moz-do-not-send="true"
href="mailto:benevides@redhat.com">benevides@redhat.com</a><br>
<<a moz-do-not-send="true"
href="mailto:benevides@redhat.com">mailto:benevides@redhat.com</a>>>
wrote:<br>
<br>
<blockquote type="cite">Done!<br>
<br>
<a moz-do-not-send="true"
href="https://github.com/jboss-jdf/jdf-stack/pull/31">https://github.com/jboss-jdf/jdf-stack/pull/31</a><br>
<br>
<br>
Em 13/12/13 12:16, Martin Malina escreveu:<br>
<blockquote type="cite">What I will need is an
altered stacks.yaml to point to the new<br>
archetype that I want to verify, right?<br>
And then I can start JBDS with
-Dorg.jboss.tools.stacks.url_stacks=…<br>
If I can achieve that, that would be perfect.<br>
<br>
-Martin<br>
<br>
On 13. 12. 2013, at 15:03, Rafael Benevides <<a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:benevides@redhat.com">benevides@redhat.com</a><br>
<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:benevides@redhat.com"><mailto:benevides@redhat.com></a>>
wrote:<br>
<br>
<blockquote type="cite">More or less.<br>
<br>
This test that I made are automated by JUnit,
so it's part of the<br>
build.<br>
<br>
There's also mention on how to test on the
contributing.md (step 8<br>
and 9) :<br>
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://github.com/jboss-developer/jboss-eap-archetypes/blob/master/CONTRIBUTING.md">https://github.com/jboss-developer/jboss-eap-archetypes/blob/master/CONTRIBUTING.md</a>
<br>
<br>
<br>
Em 13/12/13 11:57, Pete Muir escreveu:<br>
<blockquote type="cite">I think Martin could
do with steps to configure the staging repo,<br>
and then to alter JBoss Central to use the
archetype.<br>
<br>
Is this documented somewhere?<br>
<br>
On 13 Dec 2013, at 13:53, Rafael Benevides
<<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:benevides@redhat.com">benevides@redhat.com</a><br>
<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:benevides@redhat.com"><mailto:benevides@redhat.com></a>>
wrote:<br>
<br>
<blockquote type="cite">Well,<br>
<br>
My tests consists in creating a project
and build/deploy the<br>
created project using the CLI.<br>
I'm not sure if it's sufficient for an
Archerype.<br>
<br>
<br>
Em 13/12/13 11:51, Martin Malina escreveu:<br>
<blockquote type="cite">Yes, I can test
it, but only on Monday.<br>
Also, I will need Rafael to provide
steps to test this. Can you<br>
do that, Rafael?<br>
<br>
-Martin<br>
<br>
On 13. 12. 2013, at 14:39, Pete Muir
<<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:pmuir@redhat.com">pmuir@redhat.com</a><br>
<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:pmuir@redhat.com"><mailto:pmuir@redhat.com></a>>
wrote:<br>
<br>
<blockquote type="cite">Martin, are you
able to test this out?<br>
<br>
On 13 Dec 2013, at 13:18, Rafael
Benevides<br>
<<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:benevides@redhat.com">benevides@redhat.com</a>
<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:benevides@redhat.com"><mailto:benevides@redhat.com></a>>
wrote:<br>
<br>
<blockquote type="cite">Hi guys.<br>
<br>
I did:<br>
<br>
1 - Prepared EAP 6.2 Archetypes:<br>
<br>
Synch:<br>
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://github.com/jboss-developer/jboss-eap-archetypes/commit/d532e54d6c4a5fb038b8f8376d4dffba8430f42d">https://github.com/jboss-developer/jboss-eap-archetypes/commit/d532e54d6c4a5fb038b8f8376d4dffba8430f42d</a>
<br>
Tag:<br>
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA">https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA</a>
<br>
<br>
2- Release EAP 6.2 Archetype in a
staged repo:<br>
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2274/">https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2274/</a>
<br>
<br>
Now I need to know if will we let QE
team work on this<br>
release or if should I promote this
Archetypes based on the<br>
tests I made. I'm asking that
because I consider it isn't a<br>
community release anymore so I think
QE production tests<br>
should handle it.<br>
<br>
Thanks<br>
<blockquote type="cite">
<blockquote type="cite">Em
09/12/13 17:43, Rafael Benevides
escreveu:<br>
<blockquote type="cite">Hi guys,<br>
<br>
Sorry for the wide audience
but since EAP 6.2 was released<br>
last week, the archetypes (<br>
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://github.com/jboss-developer/jboss-eap-archetypes">https://github.com/jboss-developer/jboss-eap-archetypes</a>
)<br>
was not even mentioned.<br>
<br>
Since Archetypes are part of
the stacks, I'd like to know<br>
who in productization team
should handle the archetypes?<br>
<br>
WFK 2.4 Archetypes was
released to Maven Central
after a<br>
period in a nexus staged
repository being tested by WFK
QE<br>
team. Can I assume that we
will have the same approach
for<br>
EAP 6.2 Archetypes? If so,
there are some steps missing<br>
that it's needed and the time
is flying.<br>
<br>
1 - Prepare the EAP 6.2
Archetypes based on a EAP 6.2<br>
Quickstarts tag<br>
2 - Release EAP 6.2 Archetype
in a staged repo<br>
3 - QE test/fix cycle on the
Archetypes<br>
4 - Promote the stage repo<br>
5 - Ask to Sonatype to include
this new archetype groupId<br>
(org.jboss.archetype.eap) to
be synched with Maven Central<br>
6 - Update stacks.yaml<br>
<br>
So the purpose of this email
is bring EAP Archetypes under<br>
discussion (at least for this
release) since Pete is<br>
preparing a plan that should
work for next releases.<br>
<br>
-- <br>
<br>
Rafael Benevides | Senior
Software Engineer<br>
JBoss Developer<br>
M: +55-61-9269-6576<br>
<br>
<Mail Attachment.jpeg><br>
<br>
Better technology. Faster
innovation. Powered by
community<br>
collaboration.<br>
See how it works at <a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="http://www.redhat.com">www.redhat.com</a>
<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="http://www.redhat.com/"><http://www.redhat.com/></a><br>
<br>
<Mail Attachment.png>
<Mail Attachment.png><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
-- <br>
Martin Malina<br>
JBoss QA Engineer<br>
Red Hat Czech s.r.o.<br>
Purkynova 99<br>
612 45 Brno, Czech Republic<br>
<br>
Tel.: +420 532 294 265<br>
<br>
<br>
<br>
<br>
</blockquote>
</blockquote>
</blockquote>
<br>
</blockquote>
<br>
-- <br>
Martin Malina<br>
JBoss QA Engineer<br>
Red Hat Czech s.r.o.<br>
Purkynova 99<br>
612 45 Brno, Czech Republic<br>
<br>
Tel.: +420 532 294 265<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
-- <br>
Martin Malina<br>
JBoss QA Engineer<br>
Red Hat Czech s.r.o.<br>
Purkynova 99<br>
612 45 Brno, Czech Republic<br>
<br>
Tel.: +420 532 294 265<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</blockquote>
</div>
<br>
<div apple-content-edited="true"> <span
class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: Helvetica; font-style:
normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; "><span class="Apple-style-span"
style="border-collapse: separate; color: rgb(0, 0, 0);
font-family: Helvetica; font-style: normal;
font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-border-horizontal-spacing:
0px; -webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space; ">
<div apple-content-edited="true">
<div style="word-wrap: break-word;
-webkit-nbsp-mode: space; -webkit-line-break:
after-white-space; font-size: 12px; "><span
class="Apple-style-span" style="border-collapse:
separate; color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal;
orphans: 2; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2;
word-spacing: 0px;
-webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
<div style="word-wrap: break-word;
-webkit-nbsp-mode: space; -webkit-line-break:
after-white-space; ">
<div>--</div>
<div>Martin Malina<br>
JBoss QA Engineer<br>
Red Hat Czech s.r.o.<br>
Purkynova 99<br>
612 45 Brno, Czech Republic<br>
</div>
<div><br>
</div>
<div><span class="Apple-style-span" style=" ">Tel.:
+420 532 294 265</span></div>
<div><span class="Apple-style-span"
style="font-size: medium; "><br>
</span></div>
</div>
</span></div>
</div>
</div>
</span><br class="Apple-interchange-newline">
</span><br class="Apple-interchange-newline">
</div>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>