Em 9/2/14, 17:27, Sande Gilda escreveu:
Who does this?
It looks that it is under my responsibility. I
though that it was part
of the productization procedure as WFK and forgot about this for EAP.
Is this something I should be doing?
Nope.
The archetypes are still using branch 6.2.x. Looks like we missed
6.3.x. :-(
I'll wait for the 6.2.0 to become available at
http://search.maven.org/#search%7Cga%7C1%7Corg.jboss.archetype.eap -
check the other Thread
then I'll work on 6.3.0 with the latest changes - synched with 6.3.0
Quickstarts and pom.xml injection.
and merge this PR
https://github.com/jboss-developer/jboss-stacks/pull/31 to stacks.yaml
On 09/02/2014 10:53 AM, Rafael Benevides wrote:
> yes. EAP Archetypes should be release together with EAP Quickstart.
>
> It already happens for WFK Archetypes..
>
> Em 9/2/14, 11:50, Sande Gilda escreveu:
>> Thanks Rafael. That clarifies things.
>>
>> I've always been unclear about the Archetype releases. Do they
>> coincide with the JBoss EAP release cycle or the JBoss Developer
>> release cycle? When do we normally tag and branch? It seems like
>> they are tightly coupled to the quickstarts, so should we be
>> tagging, branching, and releasing them with the quickstarts?
>>
>>
>> On 09/02/2014 10:38 AM, Rafael Benevides wrote:
>>> It was changed on this commit at 11 Feb 2014 for EAP 6.2 :
>>>
https://github.com/jboss-developer/jboss-eap-archetypes/commit/e9b78e807d...
>>>
>>> After that I sent several emails asking about the Archetype
>>> productization release process and had no replies. So we haven't
>>> any archetypes releases (but -build-x) after that as you can see
>>> at:
>>>
https://github.com/jboss-developer/jboss-eap-archetypes/commits/6.2.x-dev...
>>>
>>>
>>> Em 9/2/14, 11:25, Sande Gilda escreveu:
>>>> Rafael, when where the Archetypes changed? The JBoss EAP 6 Java EE
>>>> Web Project doesn't do this in JBoss Tools 3.2.x or JBoss
>>>> Developer Studio 7.1.GA.
>>>>
>>>>
>>>> On 08/27/2014 01:29 PM, Rafael Benevides wrote:
>>>>> We need also to consider that the actual generated project by the
>>>>> latests Archetypes already uses <repository /> on its pom.xml.
>>>>>
>>>>> So I assume that we're already somehow encouraging them to do
it.
>>>>>
>>>>> More inline..
>>>>>
>>>>> Em 8/27/14, 13:26, Sande Gilda escreveu:
>>>>>>> For our products we have the obligation to keep it for 5
years,
>>>>>>> so we already can't change the repo URL. Plus the fact
that our
>>>>>>> quickstarts are not available through the Maven Central.
>>>>>> don't know where you get 5 years from - they need to be much
>>>>>> longer.
>>>>> You're right. If we consider the ELS of some products it can
>>>>> easily get more than 10 years!
>>>>>> Anyway - I believe for the released runtime pom's we cnanot
add
>>>>>> the repository urls but for the quickstart examples it is okey
>>>>>> because of the usability aspect.
>>>>>>
>>>>> +1
>>>>>> /max
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>