From sgilda at redhat.com  Tue Sep  2 10:25:54 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 02 Sep 2014 10:25:54 -0400
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <53FE1595.10401@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>
	<53FDC68C.8060100@redhat.com> <53FDDF30.5060307@redhat.com>
	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>
	<53FE06C3.6070907@redhat.com> <53FE1595.10401@redhat.com>
Message-ID: <5405D372.5080200@redhat.com>

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
>
>
>
>
>


From benevides at redhat.com  Tue Sep  2 10:38:02 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 02 Sep 2014 11:38:02 -0300
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <5405D372.5080200@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>
	<53FDC68C.8060100@redhat.com> <53FDDF30.5060307@redhat.com>
	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>
	<53FE06C3.6070907@redhat.com> <53FE1595.10401@redhat.com>
	<5405D372.5080200@redhat.com>
Message-ID: <5405D64A.8080808@redhat.com>

It was changed on this commit at 11 Feb 2014 for EAP 6.2 : 
https://github.com/jboss-developer/jboss-eap-archetypes/commit/e9b78e807d16d8c2a6c84c36b836908e1cd86e12

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-develop


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
>>
>>
>>
>>
>>
>


From benevides at redhat.com  Tue Sep  2 10:49:27 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 02 Sep 2014 11:49:27 -0300
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <5405D64A.8080808@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>	<53FDC68C.8060100@redhat.com>
	<53FDDF30.5060307@redhat.com>	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>	<53FE06C3.6070907@redhat.com>
	<53FE1595.10401@redhat.com>	<5405D372.5080200@redhat.com>
	<5405D64A.8080808@redhat.com>
Message-ID: <5405D8F7.9050202@redhat.com>

A correction:

They were released here: 
https://repository.jboss.org/nexus/content/groups/public/org/jboss/archetype/eap/

I'll check why they haven't become available and why the tag isn't at 
the github.

I'll also resend the email with the Thread where it was discussed.

Em 9/2/14, 11:38, Rafael Benevides escreveu:
> It was changed on this commit at 11 Feb 2014 for EAP 6.2 :
> https://github.com/jboss-developer/jboss-eap-archetypes/commit/e9b78e807d16d8c2a6c84c36b836908e1cd86e12
>
> 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-develop
>
>
> 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
>>>
>>>
>>>
>>>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


From sgilda at redhat.com  Tue Sep  2 10:50:30 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 02 Sep 2014 10:50:30 -0400
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <5405D64A.8080808@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>
	<53FDC68C.8060100@redhat.com> <53FDDF30.5060307@redhat.com>
	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>
	<53FE06C3.6070907@redhat.com> <53FE1595.10401@redhat.com>
	<5405D372.5080200@redhat.com> <5405D64A.8080808@redhat.com>
Message-ID: <5405D936.9010109@redhat.com>

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/e9b78e807d16d8c2a6c84c36b836908e1cd86e12
>
> 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-develop
>
>
> 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
>>>
>>>
>>>
>>>
>>>
>>
>


From benevides at redhat.com  Tue Sep  2 10:52:00 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 02 Sep 2014 11:52:00 -0300
Subject: [jbossdeveloper] EAP 6.2 Archetypes
In-Reply-To: <52B05395.1080702@redhat.com>
References: <52A61D6F.5030007@redhat.com> <52A87250.7040904@redhat.com>
	<D4156F12-D7C7-41BE-85D8-E98D06D4EFAF@redhat.com>
	<52AB090D.2030109@redhat.com>
	<A34F4EDB-F837-40A5-B609-5EAF7BDFA0F2@redhat.com>
	<717CC29D-B14E-479B-803B-A3166F1DCDDA@redhat.com>
	<52AB1169.3080807@redhat.com>
	<A7EDC576-D189-496B-A5E4-B59588641E13@redhat.com>
	<52AB13BE.1020504@redhat.com>
	<D0BDE916-6B86-4D5B-B264-A6B5F729AAFB@redhat.com>
	<52AB1C6E.7030205@redhat.com>
	<27F9BE2B-FFCE-48E2-91C8-D344D57A19E0@redhat.com>
	<52AEE67C.1030901@redhat.com> <52AF0612.4030707@redhat.com>
	<52AF0A43.2060300@redhat.com>
	<67CDC314-7766-43CB-AA45-2DF1850EB561@redhat.com>
	<52B05395.1080702@redhat.com>
Message-ID: <5405D990.9030606@redhat.com>

I'll check why those archetypes were not synchronized with Maven Central...

Em 12/17/13, 11:37, Rafael Benevides escreveu:
> Archetypes released at: 
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/archetype/eap/
>
> Now I'll wait to it be available on Maven Central so I can merge 
> stacks.yaml
>
>
> Thanks
>
> Em 17/12/13 05:29, Martin Malina escreveu:
>>
>> On 16. 12. 2013, at 15:12, Rafael Benevides <benevides at redhat.com 
>> <mailto:benevides at redhat.com>> wrote:
>>
>>>
>>> Thanks Fred and Martin!
>>
>> You?re welcome.
>>
>>> 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?
>>
>> Yes, I believe so.
>>
>> -Martin
>>
>>>
>>>
>>> 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#L2190-L2199 
>>>>>
>>>>>
>>>>> ,6.2.0 points to the new archetypes:
>>>>> https://github.com/rafabene/jdf-stack/blob/eap62Archetypes/stacks.yaml#L2229-L2234 
>>>>>
>>>>>
>>>>> 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 at redhat.com 
>>>>>> <mailto:benevides at redhat.com>
>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>> <mailto:benevides at 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/CONTRIBUTING.md 
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 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 at redhat.com
>>>>>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>>>>>> <mailto:pmuir at redhat.com>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Martin, are you able to test this out?
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 13 Dec 2013, at 13:18, Rafael Benevides
>>>>>>>>>>>>> <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi guys.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I did:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 1 - Prepared EAP 6.2 Archetypes:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Synch:
>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/commit/d532e54d6c4a5fb038b8f8376d4dffba8430f42d 
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Tag:
>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA 
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2- Release EAP 6.2 Archetype in a staged repo:
>>>>>>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2274/ 
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 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
>>
>>
>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140902/da555dd5/attachment-0001.html 

From benevides at redhat.com  Tue Sep  2 10:53:09 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 02 Sep 2014 11:53:09 -0300
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <5405D936.9010109@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>
	<53FDC68C.8060100@redhat.com> <53FDDF30.5060307@redhat.com>
	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>
	<53FE06C3.6070907@redhat.com> <53FE1595.10401@redhat.com>
	<5405D372.5080200@redhat.com> <5405D64A.8080808@redhat.com>
	<5405D936.9010109@redhat.com>
Message-ID: <5405D9D5.4060000@redhat.com>

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/e9b78e807d16d8c2a6c84c36b836908e1cd86e12
>>
>> 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-develop
>>
>>
>> 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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>


From pmuir at redhat.com  Tue Sep  2 15:31:44 2014
From: pmuir at redhat.com (Pete Muir)
Date: Tue, 2 Sep 2014 20:31:44 +0100
Subject: [jbossdeveloper] Two site updates
Message-ID: <4DA43F36-4F26-4AD2-B50D-986C5A44D5EF@redhat.com>

1) We now have a password vault, which provides you with all the keys you need to build the site. If you want adding to it, please take a look at the readme, or ping me on IRC.
2) We switched to a new cache format. If you get some file incompatible error whilst building, just do a rake clean[all]

From sgilda at redhat.com  Tue Sep  2 16:27:03 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 02 Sep 2014 16:27:03 -0400
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <5405D9D5.4060000@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>
	<53FDC68C.8060100@redhat.com> <53FDDF30.5060307@redhat.com>
	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>
	<53FE06C3.6070907@redhat.com> <53FE1595.10401@redhat.com>
	<5405D372.5080200@redhat.com> <5405D64A.8080808@redhat.com>
	<5405D936.9010109@redhat.com> <5405D9D5.4060000@redhat.com>
Message-ID: <54062817.8000801@redhat.com>

Who does this? Is this something I should be doing? The archetypes are 
still using branch 6.2.x. Looks like we missed 6.3.x. :-(

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/e9b78e807d16d8c2a6c84c36b836908e1cd86e12
>>>
>>> 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-develop
>>>
>>>
>>> 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
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>


From benevides at redhat.com  Tue Sep  2 16:32:52 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 02 Sep 2014 17:32:52 -0300
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <54062817.8000801@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>
	<53FDC68C.8060100@redhat.com> <53FDDF30.5060307@redhat.com>
	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>
	<53FE06C3.6070907@redhat.com> <53FE1595.10401@redhat.com>
	<5405D372.5080200@redhat.com> <5405D64A.8080808@redhat.com>
	<5405D936.9010109@redhat.com> <5405D9D5.4060000@redhat.com>
	<54062817.8000801@redhat.com>
Message-ID: <54062974.5050703@redhat.com>


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/e9b78e807d16d8c2a6c84c36b836908e1cd86e12
>>>>
>>>> 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-develop
>>>>
>>>>
>>>> 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
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>


From sgilda at redhat.com  Tue Sep  2 18:26:01 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 02 Sep 2014 18:26:01 -0400
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <54062974.5050703@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>
	<53FDC68C.8060100@redhat.com> <53FDDF30.5060307@redhat.com>
	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>
	<53FE06C3.6070907@redhat.com> <53FE1595.10401@redhat.com>
	<5405D372.5080200@redhat.com> <5405D64A.8080808@redhat.com>
	<5405D936.9010109@redhat.com> <5405D9D5.4060000@redhat.com>
	<54062817.8000801@redhat.com> <54062974.5050703@redhat.com>
Message-ID: <540643F9.7020004@redhat.com>

Rafael, I'm happy to help if I can. Ping me when you're ready and I'll 
do what I can.

On 09/02/2014 04:32 PM, Rafael Benevides wrote:
>
> 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/e9b78e807d16d8c2a6c84c36b836908e1cd86e12
>>>>>
>>>>> 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-develop
>>>>>
>>>>>
>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>


From mnovotny at redhat.com  Wed Sep  3 05:56:17 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Wed, 03 Sep 2014 11:56:17 +0200
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <54062974.5050703@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>	<53FDC68C.8060100@redhat.com>
	<53FDDF30.5060307@redhat.com>	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>	<53FE06C3.6070907@redhat.com>
	<53FE1595.10401@redhat.com>	<5405D372.5080200@redhat.com>
	<5405D64A.8080808@redhat.com>	<5405D936.9010109@redhat.com>
	<5405D9D5.4060000@redhat.com>	<54062817.8000801@redhat.com>
	<54062974.5050703@redhat.com>
Message-ID: <5406E5C1.3010100@redhat.com>

On 2.9.2014 22:32, Rafael Benevides wrote:
> 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.
It means that you need to delegate releasing of EAP archetypes to Paul
Gier's team transparently as you did with me ;)


-- 
Marek Novotny
--
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno


From mnovotny at redhat.com  Wed Sep  3 05:59:33 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Wed, 03 Sep 2014 11:59:33 +0200
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <5405D9D5.4060000@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>	<53FDC68C.8060100@redhat.com>
	<53FDDF30.5060307@redhat.com>	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>	<53FE06C3.6070907@redhat.com>
	<53FE1595.10401@redhat.com>	<5405D372.5080200@redhat.com>
	<5405D64A.8080808@redhat.com>	<5405D936.9010109@redhat.com>
	<5405D9D5.4060000@redhat.com>
Message-ID: <5406E685.7060604@redhat.com>

I think we sligthly changed the process to release WFK archetypes around
GA release, so I think EAP can handle the release same way. Archetypes
need to be derived from final quickstarts commit/tag and should be only
in one version - more than 1 release of archetype for the version is
confusing for end user IMHO.

On 2.9.2014 16:53, Rafael Benevides wrote:
> yes. EAP Archetypes should be release together with EAP Quickstart.
>
> It already happens for WFK Archetypes..
>


-- 
Marek Novotny
--
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno


From benevides at redhat.com  Wed Sep  3 07:31:45 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Wed, 03 Sep 2014 08:31:45 -0300
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <5406E685.7060604@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>	<53FDC68C.8060100@redhat.com>	<53FDDF30.5060307@redhat.com>	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>	<53FE06C3.6070907@redhat.com>	<53FE1595.10401@redhat.com>	<5405D372.5080200@redhat.com>	<5405D64A.8080808@redhat.com>	<5405D936.9010109@redhat.com>	<5405D9D5.4060000@redhat.com>
	<5406E685.7060604@redhat.com>
Message-ID: <5406FC21.5090008@redhat.com>

+1

Paul Gier,

Will you be happy to handle the EAP Archetypes? We need to release 6.3.0 
Archetypes so I'll be glad to guide you.

Em 9/3/14, 6:59, Marek Novotny escreveu:
> I think we sligthly changed the process to release WFK archetypes around
> GA release, so I think EAP can handle the release same way. Archetypes
> need to be derived from final quickstarts commit/tag and should be only
> in one version - more than 1 release of archetype for the version is
> confusing for end user IMHO.
>
> On 2.9.2014 16:53, Rafael Benevides wrote:
>> yes. EAP Archetypes should be release together with EAP Quickstart.
>>
>> It already happens for WFK Archetypes..
>>
>


From benevides at redhat.com  Wed Sep  3 08:37:45 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Wed, 03 Sep 2014 09:37:45 -0300
Subject: [jbossdeveloper] EAP 6.2 Archetypes
In-Reply-To: <5405D990.9030606@redhat.com>
References: <52A61D6F.5030007@redhat.com> <52A87250.7040904@redhat.com>
	<D4156F12-D7C7-41BE-85D8-E98D06D4EFAF@redhat.com>
	<52AB090D.2030109@redhat.com>
	<A34F4EDB-F837-40A5-B609-5EAF7BDFA0F2@redhat.com>
	<717CC29D-B14E-479B-803B-A3166F1DCDDA@redhat.com>
	<52AB1169.3080807@redhat.com>
	<A7EDC576-D189-496B-A5E4-B59588641E13@redhat.com>
	<52AB13BE.1020504@redhat.com>
	<D0BDE916-6B86-4D5B-B264-A6B5F729AAFB@redhat.com>
	<52AB1C6E.7030205@redhat.com>
	<27F9BE2B-FFCE-48E2-91C8-D344D57A19E0@redhat.com>
	<52AEE67C.1030901@redhat.com> <52AF0612.4030707@redhat.com>
	<52AF0A43.2060300@redhat.com>
	<67CDC314-7766-43CB-AA45-2DF1850EB561@redhat.com>
	<52B05395.1080702@redhat.com> <5405D990.9030606@redhat.com>
Message-ID: <54070B99.1030404@redhat.com>

EAP 6.2.0 Archetypes are at maven central: 
http://search.maven.org/#search%7Cga%7C1%7Corg.jboss.archetype.eap

Archetypes repo tag: 
https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA

Stacks updated: 
https://github.com/jboss-developer/jboss-stacks/commit/cc6ac1ac6


Em 9/2/14, 11:52, Rafael Benevides escreveu:
> I'll check why those archetypes were not synchronized with Maven 
> Central...
>
> Em 12/17/13, 11:37, Rafael Benevides escreveu:
>> Archetypes released at: 
>> https://repository.jboss.org/nexus/content/groups/public/org/jboss/archetype/eap/
>>
>> Now I'll wait to it be available on Maven Central so I can merge 
>> stacks.yaml
>>
>>
>> Thanks
>>
>> Em 17/12/13 05:29, Martin Malina escreveu:
>>>
>>> On 16. 12. 2013, at 15:12, Rafael Benevides <benevides at redhat.com 
>>> <mailto:benevides at redhat.com>> wrote:
>>>
>>>>
>>>> Thanks Fred and Martin!
>>>
>>> You?re welcome.
>>>
>>>> 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?
>>>
>>> Yes, I believe so.
>>>
>>> -Martin
>>>
>>>>
>>>>
>>>> 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#L2190-L2199 
>>>>>>
>>>>>>
>>>>>> ,6.2.0 points to the new archetypes:
>>>>>> https://github.com/rafabene/jdf-stack/blob/eap62Archetypes/stacks.yaml#L2229-L2234 
>>>>>>
>>>>>>
>>>>>> 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 at redhat.com <mailto:benevides at redhat.com>
>>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>>> <mailto:benevides at 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/CONTRIBUTING.md 
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 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 at redhat.com
>>>>>>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>>>>>>> <mailto:pmuir at redhat.com>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Martin, are you able to test this out?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 13 Dec 2013, at 13:18, Rafael Benevides
>>>>>>>>>>>>>> <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi guys.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I did:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 1 - Prepared EAP 6.2 Archetypes:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Synch:
>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/commit/d532e54d6c4a5fb038b8f8376d4dffba8430f42d 
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Tag:
>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA 
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2- Release EAP 6.2 Archetype in a staged repo:
>>>>>>>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2274/ 
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 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
>>>
>>>
>>>
>>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140903/458e42c3/attachment-0001.html 

From pmuir at redhat.com  Wed Sep  3 08:38:23 2014
From: pmuir at redhat.com (Pete Muir)
Date: Wed, 3 Sep 2014 13:38:23 +0100
Subject: [jbossdeveloper] EAP 6.2 Archetypes
In-Reply-To: <54070B99.1030404@redhat.com>
References: <52A61D6F.5030007@redhat.com> <52A87250.7040904@redhat.com>
	<D4156F12-D7C7-41BE-85D8-E98D06D4EFAF@redhat.com>
	<52AB090D.2030109@redhat.com>
	<A34F4EDB-F837-40A5-B609-5EAF7BDFA0F2@redhat.com>
	<717CC29D-B14E-479B-803B-A3166F1DCDDA@redhat.com>
	<52AB1169.3080807@redhat.com>
	<A7EDC576-D189-496B-A5E4-B59588641E13@redhat.com>
	<52AB13BE.1020504@redhat.com>
	<D0BDE916-6B86-4D5B-B264-A6B5F729AAFB@redhat.com>
	<52AB1C6E.7030205@redhat.com>
	<27F9BE2B-FFCE-48E2-91C8-D344D57A19E0@redhat.com>
	<52AEE67C.1030901@redhat.com> <52AF0612.4030707@redhat.com>
	<52AF0A43.2060300@redhat.com>
	<67CDC314-7766-43CB-AA45-2DF1850EB561@redhat.com>
	<52B05395.1080702@redhat.com> <5405D990.9030606@redhat.com>
	<54070B99.1030404@redhat.com>
Message-ID: <73E5CF4F-A61A-40EA-A90F-DA4B95D940A7@redhat.com>

Thanks Rafael!

On 3 Sep 2014, at 13:37, Rafael Benevides <benevides at redhat.com> wrote:

> EAP 6.2.0 Archetypes are at maven central: http://search.maven.org/#search%7Cga%7C1%7Corg.jboss.archetype.eap
> 
> Archetypes repo tag: https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA
> 
> Stacks updated: https://github.com/jboss-developer/jboss-stacks/commit/cc6ac1ac6
> 
> 
> Em 9/2/14, 11:52, Rafael Benevides escreveu:
>> I'll check why those archetypes were not synchronized with Maven Central...
>> 
>> Em 12/17/13, 11:37, Rafael Benevides escreveu:
>>> Archetypes released at: https://repository.jboss.org/nexus/content/groups/public/org/jboss/archetype/eap/
>>> 
>>> Now I'll wait to it be available on Maven Central so I can merge stacks.yaml
>>> 
>>> 
>>> Thanks
>>> 
>>> Em 17/12/13 05:29, Martin Malina escreveu:
>>>> 
>>>> On 16. 12. 2013, at 15:12, Rafael Benevides <benevides at redhat.com> wrote:
>>>> 
>>>>> 
>>>>> Thanks Fred and Martin!
>>>> 
>>>> You?re welcome.
>>>> 
>>>>> 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?
>>>> 
>>>> Yes, I believe so.
>>>> 
>>>> -Martin
>>>> 
>>>>> 
>>>>> 
>>>>> 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#L2190-L2199 
>>>>>>> 
>>>>>>> ,6.2.0 points to the new archetypes:
>>>>>>> https://github.com/rafabene/jdf-stack/blob/eap62Archetypes/stacks.yaml#L2229-L2234 
>>>>>>> 
>>>>>>> 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 at redhat.com
>>>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>>>> <mailto:benevides at 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/CONTRIBUTING.md 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 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 at redhat.com
>>>>>>>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>>>>>>>> <mailto:pmuir at redhat.com>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Martin, are you able to test this out?
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On 13 Dec 2013, at 13:18, Rafael Benevides
>>>>>>>>>>>>>>> <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Hi guys.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> I did:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 1 - Prepared EAP 6.2 Archetypes:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Synch:
>>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/commit/d532e54d6c4a5fb038b8f8376d4dffba8430f42d 
>>>>>>>>>>>>>>>> Tag:
>>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 2- Release EAP 6.2 Archetype in a staged repo:
>>>>>>>>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2274/ 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 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
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>> 
> 



From benevides at redhat.com  Wed Sep  3 10:13:56 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Wed, 03 Sep 2014 11:13:56 -0300
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <5406FC21.5090008@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>	<53FDC68C.8060100@redhat.com>	<53FDDF30.5060307@redhat.com>	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>	<53FE06C3.6070907@redhat.com>	<53FE1595.10401@redhat.com>	<5405D372.5080200@redhat.com>	<5405D64A.8080808@redhat.com>	<5405D936.9010109@redhat.com>	<5405D9D5.4060000@redhat.com>
	<5406E685.7060604@redhat.com> <5406FC21.5090008@redhat.com>
Message-ID: <54072224.8030501@redhat.com>

Including Paul Gier
Em 9/3/14, 8:31, Rafael Benevides escreveu:
> +1
>
> Paul Gier,
>
> Will you be happy to handle the EAP Archetypes? We need to release 
> 6.3.0 Archetypes so I'll be glad to guide you.
>
> Em 9/3/14, 6:59, Marek Novotny escreveu:
>> I think we sligthly changed the process to release WFK archetypes around
>> GA release, so I think EAP can handle the release same way. Archetypes
>> need to be derived from final quickstarts commit/tag and should be only
>> in one version - more than 1 release of archetype for the version is
>> confusing for end user IMHO.
>>
>> On 2.9.2014 16:53, Rafael Benevides wrote:
>>> yes. EAP Archetypes should be release together with EAP Quickstart.
>>>
>>> It already happens for WFK Archetypes..
>>>
>>
>


From pgier at redhat.com  Wed Sep  3 10:15:32 2014
From: pgier at redhat.com (Paul Gier)
Date: Wed, 03 Sep 2014 09:15:32 -0500
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <54072224.8030501@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>	<53FDC68C.8060100@redhat.com>	<53FDDF30.5060307@redhat.com>	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>	<53FE06C3.6070907@redhat.com>	<53FE1595.10401@redhat.com>	<5405D372.5080200@redhat.com>	<5405D64A.8080808@redhat.com>	<5405D936.9010109@redhat.com>	<5405D9D5.4060000@redhat.com>
	<5406E685.7060604@redhat.com> <5406FC21.5090008@redhat.com>
	<54072224.8030501@redhat.com>
Message-ID: <54072284.3060705@redhat.com>

Yes, I think prod can release the archetypes along with the other stuff.

On 09/03/2014 09:13 AM, Rafael Benevides wrote:
> Including Paul Gier
> Em 9/3/14, 8:31, Rafael Benevides escreveu:
>> +1
>>
>> Paul Gier,
>>
>> Will you be happy to handle the EAP Archetypes? We need to release
>> 6.3.0 Archetypes so I'll be glad to guide you.
>>
>> Em 9/3/14, 6:59, Marek Novotny escreveu:
>>> I think we sligthly changed the process to release WFK archetypes around
>>> GA release, so I think EAP can handle the release same way. Archetypes
>>> need to be derived from final quickstarts commit/tag and should be only
>>> in one version - more than 1 release of archetype for the version is
>>> confusing for end user IMHO.
>>>
>>> On 2.9.2014 16:53, Rafael Benevides wrote:
>>>> yes. EAP Archetypes should be release together with EAP Quickstart.
>>>>
>>>> It already happens for WFK Archetypes..
>>>>
>>>
>>
> 

From sgilda at redhat.com  Wed Sep  3 10:23:06 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 03 Sep 2014 10:23:06 -0400
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <54072284.3060705@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>	<53FDC68C.8060100@redhat.com>	<53FDDF30.5060307@redhat.com>	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>	<53FE06C3.6070907@redhat.com>	<53FE1595.10401@redhat.com>	<5405D372.5080200@redhat.com>	<5405D64A.8080808@redhat.com>	<5405D936.9010109@redhat.com>	<5405D9D5.4060000@redhat.com>	<5406E685.7060604@redhat.com>
	<5406FC21.5090008@redhat.com>	<54072224.8030501@redhat.com>
	<54072284.3060705@redhat.com>
Message-ID: <5407244A.3050801@redhat.com>

Paul, do you need any help from me to do this?

On 09/03/2014 10:15 AM, Paul Gier wrote:
> Yes, I think prod can release the archetypes along with the other stuff.
>
> On 09/03/2014 09:13 AM, Rafael Benevides wrote:
>> Including Paul Gier
>> Em 9/3/14, 8:31, Rafael Benevides escreveu:
>>> +1
>>>
>>> Paul Gier,
>>>
>>> Will you be happy to handle the EAP Archetypes? We need to release
>>> 6.3.0 Archetypes so I'll be glad to guide you.
>>>
>>> Em 9/3/14, 6:59, Marek Novotny escreveu:
>>>> I think we sligthly changed the process to release WFK archetypes around
>>>> GA release, so I think EAP can handle the release same way. Archetypes
>>>> need to be derived from final quickstarts commit/tag and should be only
>>>> in one version - more than 1 release of archetype for the version is
>>>> confusing for end user IMHO.
>>>>
>>>> On 2.9.2014 16:53, Rafael Benevides wrote:
>>>>> yes. EAP Archetypes should be release together with EAP Quickstart.
>>>>>
>>>>> It already happens for WFK Archetypes..
>>>>>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


From benevides at redhat.com  Thu Sep  4 09:27:52 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Thu, 04 Sep 2014 10:27:52 -0300
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <54072284.3060705@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>	<53FDC68C.8060100@redhat.com>	<53FDDF30.5060307@redhat.com>	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>	<53FE06C3.6070907@redhat.com>	<53FE1595.10401@redhat.com>	<5405D372.5080200@redhat.com>	<5405D64A.8080808@redhat.com>	<5405D936.9010109@redhat.com>	<5405D9D5.4060000@redhat.com>
	<5406E685.7060604@redhat.com> <5406FC21.5090008@redhat.com>
	<54072224.8030501@redhat.com> <54072284.3060705@redhat.com>
Message-ID: <540868D8.5020601@redhat.com>

Yesterday Paul and I did the release of EAP 6.3.0 Archetypes.

They're now available at Maven Central and I just commited the 
stacks.yaml: 
https://github.com/jboss-developer/jboss-stacks/commit/29a753da4

 From this release the <repository /> is injected at pom.xml of the  
archetype generated project as discussed in other threads.

Em 9/3/14, 11:15, Paul Gier escreveu:
> Yes, I think prod can release the archetypes along with the other stuff.
>
> On 09/03/2014 09:13 AM, Rafael Benevides wrote:
>> Including Paul Gier
>> Em 9/3/14, 8:31, Rafael Benevides escreveu:
>>> +1
>>>
>>> Paul Gier,
>>>
>>> Will you be happy to handle the EAP Archetypes? We need to release
>>> 6.3.0 Archetypes so I'll be glad to guide you.
>>>
>>> Em 9/3/14, 6:59, Marek Novotny escreveu:
>>>> I think we sligthly changed the process to release WFK archetypes around
>>>> GA release, so I think EAP can handle the release same way. Archetypes
>>>> need to be derived from final quickstarts commit/tag and should be only
>>>> in one version - more than 1 release of archetype for the version is
>>>> confusing for end user IMHO.
>>>>
>>>> On 2.9.2014 16:53, Rafael Benevides wrote:
>>>>> yes. EAP Archetypes should be release together with EAP Quickstart.
>>>>>
>>>>> It already happens for WFK Archetypes..
>>>>>


From benevides at redhat.com  Thu Sep  4 09:33:38 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Thu, 04 Sep 2014 10:33:38 -0300
Subject: [jbossdeveloper] EAP 6.3 Archetypes
In-Reply-To: <73E5CF4F-A61A-40EA-A90F-DA4B95D940A7@redhat.com>
References: <52A61D6F.5030007@redhat.com> <52A87250.7040904@redhat.com>
	<D4156F12-D7C7-41BE-85D8-E98D06D4EFAF@redhat.com>
	<52AB090D.2030109@redhat.com>
	<A34F4EDB-F837-40A5-B609-5EAF7BDFA0F2@redhat.com>
	<717CC29D-B14E-479B-803B-A3166F1DCDDA@redhat.com>
	<52AB1169.3080807@redhat.com>
	<A7EDC576-D189-496B-A5E4-B59588641E13@redhat.com>
	<52AB13BE.1020504@redhat.com>
	<D0BDE916-6B86-4D5B-B264-A6B5F729AAFB@redhat.com>
	<52AB1C6E.7030205@redhat.com>
	<27F9BE2B-FFCE-48E2-91C8-D344D57A19E0@redhat.com>
	<52AEE67C.1030901@redhat.com> <52AF0612.4030707@redhat.com>
	<52AF0A43.2060300@redhat.com>
	<67CDC314-7766-43CB-AA45-2DF1850EB561@redhat.com>
	<52B05395.1080702@redhat.com> <5405D990.9030606@redhat.com>
	<54070B99.1030404@redhat.com>
	<73E5CF4F-A61A-40EA-A90F-DA4B95D940A7@redhat.com>
Message-ID: <54086A32.6050607@redhat.com>

Yesterday Paul and I did the release of EAP 6.3.0 Archetypes.

They're now available at Maven Central and I just commited the stacks.yaml:
https://github.com/jboss-developer/jboss-stacks/commit/29a753da4

  From this release the <repository /> is injected at pom.xml of the archetype generated project as discussed in other threads.

Em 9/3/14, 9:38, Pete Muir escreveu:
> Thanks Rafael!
>
> On 3 Sep 2014, at 13:37, Rafael Benevides <benevides at redhat.com> wrote:
>
>> EAP 6.2.0 Archetypes are at maven central: http://search.maven.org/#search%7Cga%7C1%7Corg.jboss.archetype.eap
>>
>> Archetypes repo tag: https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA
>>
>> Stacks updated: https://github.com/jboss-developer/jboss-stacks/commit/cc6ac1ac6
>>
>>
>> Em 9/2/14, 11:52, Rafael Benevides escreveu:
>>> I'll check why those archetypes were not synchronized with Maven Central...
>>>
>>> Em 12/17/13, 11:37, Rafael Benevides escreveu:
>>>> Archetypes released at: https://repository.jboss.org/nexus/content/groups/public/org/jboss/archetype/eap/
>>>>
>>>> Now I'll wait to it be available on Maven Central so I can merge stacks.yaml
>>>>
>>>>
>>>> Thanks
>>>>
>>>> Em 17/12/13 05:29, Martin Malina escreveu:
>>>>> On 16. 12. 2013, at 15:12, Rafael Benevides <benevides at redhat.com> wrote:
>>>>>
>>>>>> Thanks Fred and Martin!
>>>>> You?re welcome.
>>>>>
>>>>>> 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?
>>>>> Yes, I believe so.
>>>>>
>>>>> -Martin
>>>>>
>>>>>>
>>>>>> 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#L2190-L2199
>>>>>>>>
>>>>>>>> ,6.2.0 points to the new archetypes:
>>>>>>>> https://github.com/rafabene/jdf-stack/blob/eap62Archetypes/stacks.yaml#L2229-L2234
>>>>>>>>
>>>>>>>> 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 at redhat.com
>>>>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>>>>> <mailto:benevides at 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/CONTRIBUTING.md
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 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 at redhat.com
>>>>>>>>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>>>>>>>>> <mailto:pmuir at redhat.com>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Martin, are you able to test this out?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 13 Dec 2013, at 13:18, Rafael Benevides
>>>>>>>>>>>>>>>> <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi guys.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I did:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 1 - Prepared EAP 6.2 Archetypes:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Synch:
>>>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/commit/d532e54d6c4a5fb038b8f8376d4dffba8430f42d
>>>>>>>>>>>>>>>>> Tag:
>>>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 2- Release EAP 6.2 Archetype in a staged repo:
>>>>>>>>>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2274/
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>>


From sgilda at redhat.com  Thu Sep  4 11:01:12 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 04 Sep 2014 11:01:12 -0400
Subject: [jbossdeveloper] EAP 6.3 Archetypes
In-Reply-To: <54086A32.6050607@redhat.com>
References: <52A61D6F.5030007@redhat.com> <52A87250.7040904@redhat.com>
	<D4156F12-D7C7-41BE-85D8-E98D06D4EFAF@redhat.com>
	<52AB090D.2030109@redhat.com>
	<A34F4EDB-F837-40A5-B609-5EAF7BDFA0F2@redhat.com>
	<717CC29D-B14E-479B-803B-A3166F1DCDDA@redhat.com>
	<52AB1169.3080807@redhat.com>
	<A7EDC576-D189-496B-A5E4-B59588641E13@redhat.com>
	<52AB13BE.1020504@redhat.com>
	<D0BDE916-6B86-4D5B-B264-A6B5F729AAFB@redhat.com>
	<52AB1C6E.7030205@redhat.com>
	<27F9BE2B-FFCE-48E2-91C8-D344D57A19E0@redhat.com>
	<52AEE67C.1030901@redhat.com> <52AF0612.4030707@redhat.com>
	<52AF0A43.2060300@redhat.com>
	<67CDC314-7766-43CB-AA45-2DF1850EB561@redhat.com>
	<52B05395.1080702@redhat.com> <5405D990.9030606@redhat.com>
	<54070B99.1030404@redhat.com>
	<73E5CF4F-A61A-40EA-A90F-DA4B95D940A7@redhat.com>
	<54086A32.6050607@redhat.com>
Message-ID: <54087EB8.8050308@redhat.com>

Thanks Rafael and Paul!

On 09/04/2014 09:33 AM, Rafael Benevides wrote:
> Yesterday Paul and I did the release of EAP 6.3.0 Archetypes.
>
> They're now available at Maven Central and I just commited the 
> stacks.yaml:
> https://github.com/jboss-developer/jboss-stacks/commit/29a753da4
>
>  From this release the <repository /> is injected at pom.xml of the 
> archetype generated project as discussed in other threads.
>
> Em 9/3/14, 9:38, Pete Muir escreveu:
>> Thanks Rafael!
>>
>> On 3 Sep 2014, at 13:37, Rafael Benevides <benevides at redhat.com> wrote:
>>
>>> EAP 6.2.0 Archetypes are at maven central: 
>>> http://search.maven.org/#search%7Cga%7C1%7Corg.jboss.archetype.eap
>>>
>>> Archetypes repo tag: 
>>> https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA
>>>
>>> Stacks updated: 
>>> https://github.com/jboss-developer/jboss-stacks/commit/cc6ac1ac6
>>>
>>>
>>> Em 9/2/14, 11:52, Rafael Benevides escreveu:
>>>> I'll check why those archetypes were not synchronized with Maven 
>>>> Central...
>>>>
>>>> Em 12/17/13, 11:37, Rafael Benevides escreveu:
>>>>> Archetypes released at: 
>>>>> https://repository.jboss.org/nexus/content/groups/public/org/jboss/archetype/eap/
>>>>>
>>>>> Now I'll wait to it be available on Maven Central so I can merge 
>>>>> stacks.yaml
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>> Em 17/12/13 05:29, Martin Malina escreveu:
>>>>>> On 16. 12. 2013, at 15:12, Rafael Benevides 
>>>>>> <benevides at redhat.com> wrote:
>>>>>>
>>>>>>> Thanks Fred and Martin!
>>>>>> You?re welcome.
>>>>>>
>>>>>>> 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?
>>>>>> Yes, I believe so.
>>>>>>
>>>>>> -Martin
>>>>>>
>>>>>>>
>>>>>>> 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#L2190-L2199 
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ,6.2.0 points to the new archetypes:
>>>>>>>>> https://github.com/rafabene/jdf-stack/blob/eap62Archetypes/stacks.yaml#L2229-L2234 
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 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 at redhat.com
>>>>>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>>>>>> <mailto:benevides at 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/CONTRIBUTING.md 
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 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 at redhat.com
>>>>>>>>>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>>>>>>>>>> <mailto:pmuir at redhat.com>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Martin, are you able to test this out?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 13 Dec 2013, at 13:18, Rafael Benevides
>>>>>>>>>>>>>>>>> <benevides at redhat.com <mailto:benevides at redhat.com>> 
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi guys.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I did:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 1 - Prepared EAP 6.2 Archetypes:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Synch:
>>>>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/commit/d532e54d6c4a5fb038b8f8376d4dffba8430f42d 
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Tag:
>>>>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA 
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 2- Release EAP 6.2 Archetype in a staged repo:
>>>>>>>>>>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2274/ 
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 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
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>


From bsutter at redhat.com  Thu Sep  4 11:29:16 2014
From: bsutter at redhat.com (Burr Sutter)
Date: Thu, 4 Sep 2014 11:29:16 -0400
Subject: [jbossdeveloper] EAP 6.3 Archetypes
In-Reply-To: <54086A32.6050607@redhat.com>
References: <52A61D6F.5030007@redhat.com> <52A87250.7040904@redhat.com>
	<D4156F12-D7C7-41BE-85D8-E98D06D4EFAF@redhat.com>
	<52AB090D.2030109@redhat.com>
	<A34F4EDB-F837-40A5-B609-5EAF7BDFA0F2@redhat.com>
	<717CC29D-B14E-479B-803B-A3166F1DCDDA@redhat.com>
	<52AB1169.3080807@redhat.com>
	<A7EDC576-D189-496B-A5E4-B59588641E13@redhat.com>
	<52AB13BE.1020504@redhat.com>
	<D0BDE916-6B86-4D5B-B264-A6B5F729AAFB@redhat.com>
	<52AB1C6E.7030205@redhat.com>
	<27F9BE2B-FFCE-48E2-91C8-D344D57A19E0@redhat.com>
	<52AEE67C.1030901@redhat.com> <52AF0612.4030707@redhat.com>
	<52AF0A43.2060300@redhat.com>
	<67CDC314-7766-43CB-AA45-2DF1850EB561@redhat.com>
	<52B05395.1080702@redhat.com> <5405D990.9030606@redhat.com>
	<54070B99.1030404@redhat.com>
	<73E5CF4F-A61A-40EA-A90F-DA4B95D940A7@redhat.com>
	<54086A32.6050607@redhat.com>
Message-ID: <8C1C5EED-2B26-492C-ADD3-3228677761E6@redhat.com>

Very good news!

On Sep 4, 2014, at 9:33 AM, Rafael Benevides <benevides at redhat.com> wrote:

> Yesterday Paul and I did the release of EAP 6.3.0 Archetypes.
> 
> They're now available at Maven Central and I just commited the stacks.yaml:
> https://github.com/jboss-developer/jboss-stacks/commit/29a753da4
> 
> From this release the <repository /> is injected at pom.xml of the archetype generated project as discussed in other threads.
> 
> Em 9/3/14, 9:38, Pete Muir escreveu:
>> Thanks Rafael!
>> 
>> On 3 Sep 2014, at 13:37, Rafael Benevides <benevides at redhat.com> wrote:
>> 
>>> EAP 6.2.0 Archetypes are at maven central: http://search.maven.org/#search%7Cga%7C1%7Corg.jboss.archetype.eap
>>> 
>>> Archetypes repo tag: https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA
>>> 
>>> Stacks updated: https://github.com/jboss-developer/jboss-stacks/commit/cc6ac1ac6
>>> 
>>> 
>>> Em 9/2/14, 11:52, Rafael Benevides escreveu:
>>>> I'll check why those archetypes were not synchronized with Maven Central...
>>>> 
>>>> Em 12/17/13, 11:37, Rafael Benevides escreveu:
>>>>> Archetypes released at: https://repository.jboss.org/nexus/content/groups/public/org/jboss/archetype/eap/
>>>>> 
>>>>> Now I'll wait to it be available on Maven Central so I can merge stacks.yaml
>>>>> 
>>>>> 
>>>>> Thanks
>>>>> 
>>>>> Em 17/12/13 05:29, Martin Malina escreveu:
>>>>>> On 16. 12. 2013, at 15:12, Rafael Benevides <benevides at redhat.com> wrote:
>>>>>> 
>>>>>>> Thanks Fred and Martin!
>>>>>> You?re welcome.
>>>>>> 
>>>>>>> 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?
>>>>>> Yes, I believe so.
>>>>>> 
>>>>>> -Martin
>>>>>> 
>>>>>>> 
>>>>>>> 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#L2190-L2199
>>>>>>>>> 
>>>>>>>>> ,6.2.0 points to the new archetypes:
>>>>>>>>> https://github.com/rafabene/jdf-stack/blob/eap62Archetypes/stacks.yaml#L2229-L2234
>>>>>>>>> 
>>>>>>>>> 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 at redhat.com
>>>>>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>>>>>> <mailto:benevides at 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/CONTRIBUTING.md
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 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 at redhat.com
>>>>>>>>>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>>>>>>>>>> <mailto:pmuir at redhat.com>> wrote:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Martin, are you able to test this out?
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> On 13 Dec 2013, at 13:18, Rafael Benevides
>>>>>>>>>>>>>>>>> <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Hi guys.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> I did:
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 1 - Prepared EAP 6.2 Archetypes:
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Synch:
>>>>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/commit/d532e54d6c4a5fb038b8f8376d4dffba8430f42d
>>>>>>>>>>>>>>>>>> Tag:
>>>>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 2- Release EAP 6.2 Archetype in a staged repo:
>>>>>>>>>>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2274/
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 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
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
> 



From manderse at redhat.com  Fri Sep  5 06:56:03 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 05 Sep 2014 12:56:03 +0200
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <540868D8.5020601@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>
	<53FDC68C.8060100@redhat.com> <53FDDF30.5060307@redhat.com>
	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>
	<53FE06C3.6070907@redhat.com> <53FE1595.10401@redhat.com>
	<5405D372.5080200@redhat.com> <5405D64A.8080808@redhat.com>
	<5405D936.9010109@redhat.com> <5405D9D5.4060000@redhat.com>
	<5406E685.7060604@redhat.com> <5406FC21.5090008@redhat.com>
	<54072224.8030501@redhat.com> <54072284.3060705@redhat.com>
	<540868D8.5020601@redhat.com>
Message-ID: <177901A1-A389-49FE-8CAB-05E994531E64@redhat.com>

On 4 Sep 2014, at 15:27, Rafael Benevides wrote:

> Yesterday Paul and I did the release of EAP 6.3.0 Archetypes.
>
> They're now available at Maven Central and I just commited the
> stacks.yaml:
> https://github.com/jboss-developer/jboss-stacks/commit/29a753da4
>
> From this release the <repository /> is injected at pom.xml of the
> archetype generated project as discussed in other threads.

cool.

where is the easiest way for me to see the injected result ?

would like to be sure its using the same id and url as we are in the 
tools and other places.

/max

>
> Em 9/3/14, 11:15, Paul Gier escreveu:
>> Yes, I think prod can release the archetypes along with the other 
>> stuff.
>>
>> On 09/03/2014 09:13 AM, Rafael Benevides wrote:
>>> Including Paul Gier
>>> Em 9/3/14, 8:31, Rafael Benevides escreveu:
>>>> +1
>>>>
>>>> Paul Gier,
>>>>
>>>> Will you be happy to handle the EAP Archetypes? We need to release
>>>> 6.3.0 Archetypes so I'll be glad to guide you.
>>>>
>>>> Em 9/3/14, 6:59, Marek Novotny escreveu:
>>>>> I think we sligthly changed the process to release WFK archetypes 
>>>>> around
>>>>> GA release, so I think EAP can handle the release same way. 
>>>>> Archetypes
>>>>> need to be derived from final quickstarts commit/tag and should be 
>>>>> only
>>>>> in one version - more than 1 release of archetype for the version 
>>>>> is
>>>>> confusing for end user IMHO.
>>>>>
>>>>> On 2.9.2014 16:53, Rafael Benevides wrote:
>>>>>> yes. EAP Archetypes should be release together with EAP 
>>>>>> Quickstart.
>>>>>>
>>>>>> It already happens for WFK Archetypes..
>>>>>>
>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


/max
http://about.me/maxandersen

From benevides at redhat.com  Fri Sep  5 07:26:34 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 05 Sep 2014 08:26:34 -0300
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <177901A1-A389-49FE-8CAB-05E994531E64@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>
	<53FDC68C.8060100@redhat.com> <53FDDF30.5060307@redhat.com>
	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>
	<53FE06C3.6070907@redhat.com> <53FE1595.10401@redhat.com>
	<5405D372.5080200@redhat.com> <5405D64A.8080808@redhat.com>
	<5405D936.9010109@redhat.com> <5405D9D5.4060000@redhat.com>
	<5406E685.7060604@redhat.com> <5406FC21.5090008@redhat.com>
	<54072224.8030501@redhat.com> <54072284.3060705@redhat.com>
	<540868D8.5020601@redhat.com>
	<177901A1-A389-49FE-8CAB-05E994531E64@redhat.com>
Message-ID: <54099DEA.3060905@redhat.com>

Well, the patch that "injectes" the repo is this: 
https://github.com/jboss-developer/jboss-eap-archetypes/blob/6.4.x-develop/jboss-javaee6-webapp-archetype/jboss-repositories-webapp.diff#L56-L70


Em 9/5/14, 7:56, Max Rydahl Andersen escreveu:
> On 4 Sep 2014, at 15:27, Rafael Benevides wrote:
>
>> Yesterday Paul and I did the release of EAP 6.3.0 Archetypes.
>>
>> They're now available at Maven Central and I just commited the
>> stacks.yaml:
>> https://github.com/jboss-developer/jboss-stacks/commit/29a753da4
>>
>> From this release the <repository /> is injected at pom.xml of the
>> archetype generated project as discussed in other threads.
>
> cool.
>
> where is the easiest way for me to see the injected result ?
>
> would like to be sure its using the same id and url as we are in the 
> tools and other places.
>
> /max
>
>>
>> Em 9/3/14, 11:15, Paul Gier escreveu:
>>> Yes, I think prod can release the archetypes along with the other 
>>> stuff.
>>>
>>> On 09/03/2014 09:13 AM, Rafael Benevides wrote:
>>>> Including Paul Gier
>>>> Em 9/3/14, 8:31, Rafael Benevides escreveu:
>>>>> +1
>>>>>
>>>>> Paul Gier,
>>>>>
>>>>> Will you be happy to handle the EAP Archetypes? We need to release
>>>>> 6.3.0 Archetypes so I'll be glad to guide you.
>>>>>
>>>>> Em 9/3/14, 6:59, Marek Novotny escreveu:
>>>>>> I think we sligthly changed the process to release WFK archetypes 
>>>>>> around
>>>>>> GA release, so I think EAP can handle the release same way. 
>>>>>> Archetypes
>>>>>> need to be derived from final quickstarts commit/tag and should 
>>>>>> be only
>>>>>> in one version - more than 1 release of archetype for the version is
>>>>>> confusing for end user IMHO.
>>>>>>
>>>>>> On 2.9.2014 16:53, Rafael Benevides wrote:
>>>>>>> yes. EAP Archetypes should be release together with EAP Quickstart.
>>>>>>>
>>>>>>> It already happens for WFK Archetypes..
>>>>>>>
>>
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
>
> /max
> http://about.me/maxandersen


From manderse at redhat.com  Fri Sep  5 07:47:29 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 05 Sep 2014 13:47:29 +0200
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <54099DEA.3060905@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>
	<53FDC68C.8060100@redhat.com> <53FDDF30.5060307@redhat.com>
	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>
	<53FE06C3.6070907@redhat.com> <53FE1595.10401@redhat.com>
	<5405D372.5080200@redhat.com> <5405D64A.8080808@redhat.com>
	<5405D936.9010109@redhat.com> <5405D9D5.4060000@redhat.com>
	<5406E685.7060604@redhat.com> <5406FC21.5090008@redhat.com>
	<54072224.8030501@redhat.com> <54072284.3060705@redhat.com>
	<540868D8.5020601@redhat.com>
	<177901A1-A389-49FE-8CAB-05E994531E64@redhat.com>
	<54099DEA.3060905@redhat.com>
Message-ID: <D2D53978-355C-4F16-B73A-87FF211028E9@redhat.com>

On 5 Sep 2014, at 13:26, Rafael Benevides wrote:

> Well, the patch that "injectes" the repo is this: 
> https://github.com/jboss-developer/jboss-eap-archetypes/blob/6.4.x-develop/jboss-javaee6-webapp-archetype/jboss-repositories-webapp.diff#L56-L70

so a few things:

in stacks.yml the id is 'redhat-techpreview-all-repository' and in this 
patch it is 'jboss-products-ga-repo' but it is still using the 
techpreview url (/techpreview/all).

I can also see that earlyaccess is now enabled by default on 
https://github.com/jboss-developer/jboss-eap-quickstarts/commit/35847933994901f2ff29e0de20de1845f7972708 
is that expected ?

Anyways:

1) can we agree on aligning the id's ? (just so we are in sync)

2) is it expected the id says 'ga' but the url is not that ?

For #1 we should look at updating that in stacks.yml so we add it with 
the same id.

Before changing stacks.yml I want to be sure #2 was consistent choice we 
wanted to make for that?

ps. we actually also add this repo as a plugin repository - not sure if 
that matters for you?

/max

>
> Em 9/5/14, 7:56, Max Rydahl Andersen escreveu:
>> On 4 Sep 2014, at 15:27, Rafael Benevides wrote:
>>
>>> Yesterday Paul and I did the release of EAP 6.3.0 Archetypes.
>>>
>>> They're now available at Maven Central and I just commited the
>>> stacks.yaml:
>>> https://github.com/jboss-developer/jboss-stacks/commit/29a753da4
>>>
>>> From this release the <repository /> is injected at pom.xml of the
>>> archetype generated project as discussed in other threads.
>>
>> cool.
>>
>> where is the easiest way for me to see the injected result ?
>>
>> would like to be sure its using the same id and url as we are in the 
>> tools and other places.
>>
>> /max
>>
>>>
>>> Em 9/3/14, 11:15, Paul Gier escreveu:
>>>> Yes, I think prod can release the archetypes along with the other 
>>>> stuff.
>>>>
>>>> On 09/03/2014 09:13 AM, Rafael Benevides wrote:
>>>>> Including Paul Gier
>>>>> Em 9/3/14, 8:31, Rafael Benevides escreveu:
>>>>>> +1
>>>>>>
>>>>>> Paul Gier,
>>>>>>
>>>>>> Will you be happy to handle the EAP Archetypes? We need to 
>>>>>> release
>>>>>> 6.3.0 Archetypes so I'll be glad to guide you.
>>>>>>
>>>>>> Em 9/3/14, 6:59, Marek Novotny escreveu:
>>>>>>> I think we sligthly changed the process to release WFK 
>>>>>>> archetypes around
>>>>>>> GA release, so I think EAP can handle the release same way. 
>>>>>>> Archetypes
>>>>>>> need to be derived from final quickstarts commit/tag and should 
>>>>>>> be only
>>>>>>> in one version - more than 1 release of archetype for the 
>>>>>>> version is
>>>>>>> confusing for end user IMHO.
>>>>>>>
>>>>>>> On 2.9.2014 16:53, Rafael Benevides wrote:
>>>>>>>> yes. EAP Archetypes should be release together with EAP 
>>>>>>>> Quickstart.
>>>>>>>>
>>>>>>>> It already happens for WFK Archetypes..
>>>>>>>>
>>>
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>
>>
>> /max
>> http://about.me/maxandersen


/max
http://about.me/maxandersen


From benevides at redhat.com  Fri Sep  5 07:58:28 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 05 Sep 2014 08:58:28 -0300
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <D2D53978-355C-4F16-B73A-87FF211028E9@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>
	<53FDC68C.8060100@redhat.com> <53FDDF30.5060307@redhat.com>
	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>
	<53FE06C3.6070907@redhat.com> <53FE1595.10401@redhat.com>
	<5405D372.5080200@redhat.com> <5405D64A.8080808@redhat.com>
	<5405D936.9010109@redhat.com> <5405D9D5.4060000@redhat.com>
	<5406E685.7060604@redhat.com> <5406FC21.5090008@redhat.com>
	<54072224.8030501@redhat.com> <54072284.3060705@redhat.com>
	<540868D8.5020601@redhat.com>
	<177901A1-A389-49FE-8CAB-05E994531E64@redhat.com>
	<54099DEA.3060905@redhat.com>
	<D2D53978-355C-4F16-B73A-87FF211028E9@redhat.com>
Message-ID: <5409A564.9020504@redhat.com>


Em 9/5/14, 8:47, Max Rydahl Andersen escreveu:
> so a few things:
>
> in stacks.yml the id is 'redhat-techpreview-all-repository' and in 
> this patch it is 'jboss-products-ga-repo' but it is still using the 
> techpreview url (/techpreview/all).
>
Since the Archtypes were released, should I update the Stacks to ` 
jboss-product-repository`  for those archtypes only ? Then I update the 
patch for 'redhat-techpreview-all-repository' for the next EAP 6.4 release ?
> I can also see that earlyaccess is now enabled by default on 
> https://github.com/jboss-developer/jboss-eap-quickstarts/commit/35847933994901f2ff29e0de20de1845f7972708 
> is that expected ?
I don't know.
>
> Anyways:
>
> 1) can we agree on aligning the id's ? (just so we are in sync)
Yeap. For sure! I'll update the patch file now for to 
'redhat-techpreview-all-repository' as I just said..
>
> 2) is it expected the id says 'ga' but the url is not that ?

Once that we change to ' redhat-techpreview-all-repository' it won't 
matter anymore.
>
> For #1 we should look at updating that in stacks.yml so we add it with 
> the same id.
>
> Before changing stacks.yml I want to be sure #2 was consistent choice 
> we wanted to make for that?
>
> ps. we actually also add this repo as a plugin repository - not sure 
> if that matters for you?
I don't think it matters since the tests worked fine.

So that's my plan:

1 - Update the patch file to use 'redhat-techpreview-all-repository' as 
repo id instead of 'jboss-products-ga-repo'. It will be available for 
next EAP 6.4 Archtype release.

2 - Wait for your answer if we should update stacks.yaml  repo to ' 
jboss-products-ga-repo' for EAP 6.3 Archetypes only

Is that right ?
>
> /max 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140905/cf2034d9/attachment.html 

From sgilda at redhat.com  Fri Sep  5 08:52:15 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 05 Sep 2014 08:52:15 -0400
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <5409A564.9020504@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>	<53FDC68C.8060100@redhat.com>
	<53FDDF30.5060307@redhat.com>	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>	<53FE06C3.6070907@redhat.com>
	<53FE1595.10401@redhat.com>	<5405D372.5080200@redhat.com>
	<5405D64A.8080808@redhat.com>	<5405D936.9010109@redhat.com>
	<5405D9D5.4060000@redhat.com>	<5406E685.7060604@redhat.com>
	<5406FC21.5090008@redhat.com>	<54072224.8030501@redhat.com>
	<54072284.3060705@redhat.com>	<540868D8.5020601@redhat.com>	<177901A1-A389-49FE-8CAB-05E994531E64@redhat.com>	<54099DEA.3060905@redhat.com>	<D2D53978-355C-4F16-B73A-87FF211028E9@redhat.com>
	<5409A564.9020504@redhat.com>
Message-ID: <5409B1FF.6090707@redhat.com>

Hi Rafael and everyone,

Do I need to change the 6.4.x-develop branch of the quickstarts at this 
point? And if so, what do I need to do?

  * Do I need to add the repository to all the POM files?
  * Should I update all the README files to mention that it is not a
    good practice to add the repository to the POM files?
  * Should I remove the settings.xml file?

Thanks,
Sande

On 09/05/2014 07:58 AM, Rafael Benevides wrote:
>
> Em 9/5/14, 8:47, Max Rydahl Andersen escreveu:
>> so a few things:
>>
>> in stacks.yml the id is 'redhat-techpreview-all-repository' and in 
>> this patch it is 'jboss-products-ga-repo' but it is still using the 
>> techpreview url (/techpreview/all).
>>
> Since the Archtypes were released, should I update the Stacks to ` 
> jboss-product-repository`  for those archtypes only ? Then I update 
> the patch for 'redhat-techpreview-all-repository' for the next EAP 6.4 
> release ?
>> I can also see that earlyaccess is now enabled by default on 
>> https://github.com/jboss-developer/jboss-eap-quickstarts/commit/35847933994901f2ff29e0de20de1845f7972708 
>> is that expected ?
> I don't know.
>>
>> Anyways:
>>
>> 1) can we agree on aligning the id's ? (just so we are in sync)
> Yeap. For sure! I'll update the patch file now for to 
> 'redhat-techpreview-all-repository' as I just said..
>>
>> 2) is it expected the id says 'ga' but the url is not that ?
>
> Once that we change to ' redhat-techpreview-all-repository' it won't 
> matter anymore.
>>
>> For #1 we should look at updating that in stacks.yml so we add it 
>> with the same id.
>>
>> Before changing stacks.yml I want to be sure #2 was consistent choice 
>> we wanted to make for that?
>>
>> ps. we actually also add this repo as a plugin repository - not sure 
>> if that matters for you?
> I don't think it matters since the tests worked fine.
>
> So that's my plan:
>
> 1 - Update the patch file to use 'redhat-techpreview-all-repository' 
> as repo id instead of 'jboss-products-ga-repo'. It will be available 
> for next EAP 6.4 Archtype release.
>
> 2 - Wait for your answer if we should update stacks.yaml  repo to ' 
> jboss-products-ga-repo' for EAP 6.3 Archetypes only
>
> Is that right ?
>>
>> /max 
>
>
>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140905/a308f310/attachment.html 

From benevides at redhat.com  Fri Sep  5 08:59:57 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 05 Sep 2014 09:59:57 -0300
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <5409B1FF.6090707@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>	<53FDC68C.8060100@redhat.com>
	<53FDDF30.5060307@redhat.com>	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>	<53FE06C3.6070907@redhat.com>
	<53FE1595.10401@redhat.com>	<5405D372.5080200@redhat.com>
	<5405D64A.8080808@redhat.com>	<5405D936.9010109@redhat.com>
	<5405D9D5.4060000@redhat.com>	<5406E685.7060604@redhat.com>
	<5406FC21.5090008@redhat.com>	<54072224.8030501@redhat.com>
	<54072284.3060705@redhat.com>	<540868D8.5020601@redhat.com>	<177901A1-A389-49FE-8CAB-05E994531E64@redhat.com>	<54099DEA.3060905@redhat.com>	<D2D53978-355C-4F16-B73A-87FF211028E9@redhat.com>
	<5409A564.9020504@redhat.com> <5409B1FF.6090707@redhat.com>
Message-ID: <5409B3CD.1020505@redhat.com>


Em 9/5/14, 9:52, Sande Gilda escreveu:
> Hi Rafael and everyone,
>
> Do I need to change the 6.4.x-develop branch of the quickstarts at 
> this point? And if so, what do I need to do?
Idk
>
>   * Do I need to add the repository to all the POM files?
>
I'm improving QSTools to do that for us: 
https://issues.jboss.org/browse/JDF-762
>
>   * Should I update all the README files to mention that it is not a
>     good practice to add the repository to the POM files?
>
I think so as one of the goals of the Quickstarts is to "tech" users 
about the best practices. But  we should make it clear why we took this 
decision so it won't be something like : "Do what We say, not what We do".
>
>   * Should I remove the settings.xml file?
>
Maybe after we run QSTools to "inject" the repository into the Quickstarts.
>
> Thanks,
> Sande
>
> On 09/05/2014 07:58 AM, Rafael Benevides wrote:
>>
>> Em 9/5/14, 8:47, Max Rydahl Andersen escreveu:
>>> so a few things:
>>>
>>> in stacks.yml the id is 'redhat-techpreview-all-repository' and in 
>>> this patch it is 'jboss-products-ga-repo' but it is still using the 
>>> techpreview url (/techpreview/all).
>>>
>> Since the Archtypes were released, should I update the Stacks to ` 
>> jboss-product-repository`  for those archtypes only ? Then I update 
>> the patch for 'redhat-techpreview-all-repository' for the next EAP 
>> 6.4 release ?
>>> I can also see that earlyaccess is now enabled by default on 
>>> https://github.com/jboss-developer/jboss-eap-quickstarts/commit/35847933994901f2ff29e0de20de1845f7972708 
>>> is that expected ?
>> I don't know.
>>>
>>> Anyways:
>>>
>>> 1) can we agree on aligning the id's ? (just so we are in sync)
>> Yeap. For sure! I'll update the patch file now for to 
>> 'redhat-techpreview-all-repository' as I just said..
>>>
>>> 2) is it expected the id says 'ga' but the url is not that ?
>>
>> Once that we change to ' redhat-techpreview-all-repository' it won't 
>> matter anymore.
>>>
>>> For #1 we should look at updating that in stacks.yml so we add it 
>>> with the same id.
>>>
>>> Before changing stacks.yml I want to be sure #2 was consistent 
>>> choice we wanted to make for that?
>>>
>>> ps. we actually also add this repo as a plugin repository - not sure 
>>> if that matters for you?
>> I don't think it matters since the tests worked fine.
>>
>> So that's my plan:
>>
>> 1 - Update the patch file to use 'redhat-techpreview-all-repository' 
>> as repo id instead of 'jboss-products-ga-repo'. It will be available 
>> for next EAP 6.4 Archtype release.
>>
>> 2 - Wait for your answer if we should update stacks.yaml  repo to ' 
>> jboss-products-ga-repo' for EAP 6.3 Archetypes only
>>
>> Is that right ?
>>>
>>> /max 
>>
>>
>>
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140905/11dfbb2a/attachment-0001.html 

From benevides at redhat.com  Fri Sep  5 09:01:34 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 05 Sep 2014 10:01:34 -0300
Subject: [jbossdeveloper] Maven Configuration - preferred method
In-Reply-To: <5409B3CD.1020505@redhat.com>
References: <5FAFFB03-D040-4C87-9B6C-6005BF31C9F0@redhat.com>	<53FDC68C.8060100@redhat.com>	<53FDDF30.5060307@redhat.com>	<E66AFF77-5AFC-4E60-B896-38E1CDAC8AB0@redhat.com>	<53FE06C3.6070907@redhat.com>	<53FE1595.10401@redhat.com>	<5405D372.5080200@redhat.com>	<5405D64A.8080808@redhat.com>	<5405D936.9010109@redhat.com>	<5405D9D5.4060000@redhat.com>	<5406E685.7060604@redhat.com>	<5406FC21.5090008@redhat.com>	<54072224.8030501@redhat.com>	<54072284.3060705@redhat.com>	<540868D8.5020601@redhat.com>	<177901A1-A389-49FE-8CAB-05E994531E64@redhat.com>	<54099DEA.3060905@redhat.com>	<D2D53978-355C-4F16-B73A-87FF211028E9@redhat.com>	<5409A564.9020504@redhat.com>
	<5409B1FF.6090707@redhat.com> <5409B3CD.1020505@redhat.com>
Message-ID: <5409B42E.50205@redhat.com>

/s/tech/teach

Em 9/5/14, 9:59, Rafael Benevides escreveu:
>
> Em 9/5/14, 9:52, Sande Gilda escreveu:
>> Hi Rafael and everyone,
>>
>> Do I need to change the 6.4.x-develop branch of the quickstarts at 
>> this point? And if so, what do I need to do?
> Idk
>>
>>   * Do I need to add the repository to all the POM files?
>>
> I'm improving QSTools to do that for us: 
> https://issues.jboss.org/browse/JDF-762
>>
>>   * Should I update all the README files to mention that it is not a
>>     good practice to add the repository to the POM files?
>>
> I think so as one of the goals of the Quickstarts is to "tech" users 
> about the best practices. But  we should make it clear why we took 
> this decision so it won't be something like : "Do what We say, not 
> what We do".
>>
>>   * Should I remove the settings.xml file?
>>
> Maybe after we run QSTools to "inject" the repository into the 
> Quickstarts.
>>
>> Thanks,
>> Sande
>>
>> On 09/05/2014 07:58 AM, Rafael Benevides wrote:
>>>
>>> Em 9/5/14, 8:47, Max Rydahl Andersen escreveu:
>>>> so a few things:
>>>>
>>>> in stacks.yml the id is 'redhat-techpreview-all-repository' and in 
>>>> this patch it is 'jboss-products-ga-repo' but it is still using the 
>>>> techpreview url (/techpreview/all).
>>>>
>>> Since the Archtypes were released, should I update the Stacks to ` 
>>> jboss-product-repository`  for those archtypes only ? Then I update 
>>> the patch for 'redhat-techpreview-all-repository' for the next EAP 
>>> 6.4 release ?
>>>> I can also see that earlyaccess is now enabled by default on 
>>>> https://github.com/jboss-developer/jboss-eap-quickstarts/commit/35847933994901f2ff29e0de20de1845f7972708 
>>>> is that expected ?
>>> I don't know.
>>>>
>>>> Anyways:
>>>>
>>>> 1) can we agree on aligning the id's ? (just so we are in sync)
>>> Yeap. For sure! I'll update the patch file now for to 
>>> 'redhat-techpreview-all-repository' as I just said..
>>>>
>>>> 2) is it expected the id says 'ga' but the url is not that ?
>>>
>>> Once that we change to ' redhat-techpreview-all-repository' it won't 
>>> matter anymore.
>>>>
>>>> For #1 we should look at updating that in stacks.yml so we add it 
>>>> with the same id.
>>>>
>>>> Before changing stacks.yml I want to be sure #2 was consistent 
>>>> choice we wanted to make for that?
>>>>
>>>> ps. we actually also add this repo as a plugin repository - not 
>>>> sure if that matters for you?
>>> I don't think it matters since the tests worked fine.
>>>
>>> So that's my plan:
>>>
>>> 1 - Update the patch file to use 'redhat-techpreview-all-repository' 
>>> as repo id instead of 'jboss-products-ga-repo'. It will be available 
>>> for next EAP 6.4 Archtype release.
>>>
>>> 2 - Wait for your answer if we should update stacks.yaml  repo to ' 
>>> jboss-products-ga-repo' for EAP 6.3 Archetypes only
>>>
>>> Is that right ?
>>>>
>>>> /max 
>>>
>>>
>>>
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>
>
>
>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140905/13676ef4/attachment.html 

From benevides at redhat.com  Mon Sep  8 11:51:09 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Mon, 08 Sep 2014 12:51:09 -0300
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
Message-ID: <540DD06D.2090806@redhat.com>

After working on a PoC, I prepared QSTools to inject the <repository /> 
definition in a _separated profile_ as we do for Archetypes: 
https://github.com/jboss-developer/jboss-eap-archetypes/blob/6.4.x-develop/jboss-javaee6-webapp-archetype/jboss-repositories-webapp.diff

QSTools ticket: https://issues.jboss.org/browse/JDF-762

But after placing http://maven.repository.redhat.com/techpreview/all/ at 
the Quickstarts, I realized that we won't solve the user experience 
issues without adding - https://maven.repository.redhat.com/earlyaccess/ 
and
- http://jboss-developer.github.io/temp-maven-repo/ also
for the -develop branch.

This will generate a management issue because those extra repos will 
need to be removed for Quickstarts .GA distribution.

If we instruct contributors to place the earlyaccess and temp-maven-repo 
on settings.xml and add techpreview to pom.xml it can become confusing.

*Summary*: I think that injecting <repository /> would be nice but it 
will bring an extra management effort and/or some sort of confusion. So 
it has more cons than pros.

Well, JBDS already brings a Wizard to customize the settings.xml. I 
think that CLI users have the expertise to know that it's probably a 
missing configuration than a Quickstarts bug.

Maybe we need to think a little bit more on other solutions for this 
issue for CLI users.

Em 8/27/14, 12:18, Pete Muir escreveu:
> I think it is simpler to put the repo in the POM. We have to explain either approach to our users, so we should go with the simpler to explain and understand.
>
> On 27 Aug 2014, at 13:29, Paul Robinson <paul.robinson at redhat.com> wrote:
>
>> Pete,
>>
>> You mentioned this week that you no longer think the maven plugin was a good idea. What's your thinking now?
>>
>> On 27 Aug 2014, at 12:52, Sande Gilda <sgilda at redhat.com> wrote:
>>
>>> Pete suggested this approach last fall. I will forward that email.
>>>
>>> Rafael, separately I am also forwarding the email discussed the cons of
>>> adding the <repository/> to the POM files. :-)
>>>
>>>
>>> On 08/27/2014 04:32 AM, Darran Lofthouse wrote:
>>>> Wonder if there is any maven plug in that can output a nice message if
>>>> a condition is not met.
>>>>
>>>> Regards,
>>>> Darran Lofthouse.
>>>>
>>>>
>>>> On 26/08/14 22:27, Rafael Benevides wrote:
>>>>> Em 8/26/14, 17:56, Sande Gilda escreveu:
>>>>>> So they, like me, don't RTFM? :-)
>>>>> ahahahah
>>>>>> I didn't realize it was an issue. Who is fielding the complaints for
>>>>>> this? I haven't been aware of any. And is it primarily people who use
>>>>>> the Maven command line or JDBS?
>>>>> I believe that it comes mostly by people using CLI since JBDS helps
>>>>> on this.
>>>>>
>>>>> This $subject was reborn by a request from Arun Gupta. It seems that
>>>>> someone tried to use our Quickstarts and had issues because e forgot to
>>>>> RTFM :)
>>>>>> Wouldn't it be easier to try to make the Maven setting configuration
>>>>>> requirements more prominent? I really don't like the idea of adding
>>>>>> the Maven repository to the POM files and then telling them it's not a
>>>>>> good practice. If they see something, they will repeat it because, as
>>>>>> you said, they don't read the instructions. The whole purpose of the
>>>>>> quickstarts is to show how to code using best practices.
>>>>> It's the kind of relax thing that I don't think we will regret because
>>>>> it has the advantages that I mentioned. Besides the "not being
>>>>> recommended" I don't see any potential issues for us.
>>>>>
>>>>> I remember that you sent me  (more than a year ago) some URLs that
>>>>> mention the cons on having <repository /> on pom.xml file. Do you mind
>>>>> sharing it again ?
>>>>>
>>>>> Thanks
>>>>>>
>>>>>> On 08/26/2014 04:44 PM, Rafael Benevides wrote:
>>>>>>> The problem that we're trying to solve is that users don't read the
>>>>>>> instructions :)
>>>>>>>
>>>>>>> So, they don't know that they have to configure the settings.xml until
>>>>>>> they face a build problem.
>>>>>>>
>>>>>>> Em 8/26/14, 14:33, Sande Gilda escreveu:
>>>>>>>> Sorry, I'm just back from PTO and catching up on this thread.
>>>>>>>>
>>>>>>>> I have run the quickstarts using both command line and JDBS without
>>>>>>>> running into any problems, so I'm not really clear what problem we
>>>>>>>> are
>>>>>>>> trying to solve. Are there issues with asking the user to
>>>>>>>> configure the
>>>>>>>> settings.xml file with the content we provide?
>>>>>>>>
>>>>>>>> I'm adding Paul and Nikoleta to the thread to see how this might
>>>>>>>> impact
>>>>>>>> the quickstart testing and release process.
>>>>>>>>
>>>>>>>> On 08/26/2014 05:27 AM, Pete Muir wrote:
>>>>>>>>> On 26 Aug 2014, at 10:26, Paul Robinson <paul.robinson at redhat.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> On 26 Aug 2014, at 10:18, Pete Muir <pmuir at redhat.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> On 26 Aug 2014, at 09:27, Paul Robinson
>>>>>>>>>>> <paul.robinson at redhat.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Rafael,
>>>>>>>>>>>>
>>>>>>>>>>>> It'd be worth reading the "[Wolf] Revisting embedding
>>>>>>>>>>>> repositories in POMs for developer materials" thread on
>>>>>>>>>>>> enterprise-maven-list at redhat.com. There was quite a bit of
>>>>>>>>>>>> discussion about doing this. The general opinion was that it
>>>>>>>>>>>> would be a huge win for usability, but there are quite a few
>>>>>>>>>>>> subtle problems with the approach. For example, productization
>>>>>>>>>>>> are currently stripping off these repository definitions from
>>>>>>>>>>>> quickstarts, so any solution is going to need to work for them.
>>>>>>>>>>> We don?t currently put any repo definitions in quickstarts...
>>>>>>>>>> Sorry, I should have been clearer. Productization would remove
>>>>>>>>>> them if they exist. Quote from Julian Coleman:
>>>>>>>>>>
>>>>>>>>>>      Right.  Note, also, that the vman tool will strip out the
>>>>>>>>>> <repositories>
>>>>>>>>>>      from the POM files that it processes.  This means that all POM
>>>>>>>>>> files for
>>>>>>>>>>      the IP builds (FSW/DV/BPMS) will not contain repositories.
>>>>>>>>>> So, adding
>>>>>>>>>>      this information to settings.xml seems the only sensible
>>>>>>>>>> option.
>>>>>>>>> Not all platforms use vman afaik.
>>>>>>>>>
>>>>>>>>>>>> Pete came up with an alternative approach that helps to educate
>>>>>>>>>>>> the developer about the configuration, in a better way then we
>>>>>>>>>>>> have ATM (expecting them to read the docs). This approach was to
>>>>>>>>>>>> include a plugin (that lives in maven central). This plugin
>>>>>>>>>>>> would detect missing dependencies that would be available had
>>>>>>>>>>>> the correct repository been defined in the settings.xml. There
>>>>>>>>>>>> might also be an option to fix the configuration automatically?
>>>>>>>>>>> I?m not so sure about this any more.
>>>>>>>>>>>
>>>>>>>>>>>> Paul.
>>>>>>>>>>>>
>>>>>>>>>>>> On 25 Aug 2014, at 13:50, Rafael Benevides
>>>>>>>>>>>> <benevides at redhat.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>
>>>>>>>>>>>>> On a look for a continuous improvement on developer user
>>>>>>>>>>>>> experience and also because we have been constantly asked to
>>>>>>>>>>>>> support issues related to the setup of
>>>>>>>>>>>>> https://access.redhat.com/maven-repository to make the
>>>>>>>>>>>>> quickstarts work, we want to include the <repository />
>>>>>>>>>>>>> definition on quickstarts pom.xml
>>>>>>>>>>>>>
>>>>>>>>>>>>> Actually the Archetypes already have the <repository /> on the
>>>>>>>>>>>>> pom.xml file of the generated project.
>>>>>>>>>>>>>
>>>>>>>>>>>>> The idea here is to have the <repository /> with the
>>>>>>>>>>>>> https://maven.repository.redhat.com/techpreview/all/ defined on
>>>>>>>>>>>>> every quickstarts's pom.xml file with a comment on top of it
>>>>>>>>>>>>> saying that this approach is not recommended but we included it
>>>>>>>>>>>>> so users can test the quickstarts without further setup and
>>>>>>>>>>>>> that it's recommended to use settings.xml.
>>>>>>>>>>>>>
>>>>>>>>>>>>> It will bring the following advantages:
>>>>>>>>>>>>> - It will make ease to contributors and users
>>>>>>>>>>>>> - Simplify the build.
>>>>>>>>>>>>> - Simplify the Archetype synch process / No need to inject the
>>>>>>>>>>>>> repo since it will come from the Quickstarts
>>>>>>>>>>>>> - We can add a pre-defined comment above the pom.xml repository
>>>>>>>>>>>>> definition to explain that we don't recommend that.
>>>>>>>>>>>>> - We can also add this "comment" to QSTools to check/fix it.
>>>>>>>>>>>>>
>>>>>>>>>>>>> As a roadmap for it:
>>>>>>>>>>>>> - We need to document that at the
>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-developer-shared-resources
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> - We need to update the contributing guides
>>>>>>>>>>>>> - We need to update QSTools to do this update on all
>>>>>>>>>>>>> quickstarts for us.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Max, Is there any restrictions on JBDS side ?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Anyone else have any objections/comments on this $subject ?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>
>>>>>>>>>>>>> Rafael Benevides | Senior Software Engineer
>>>>>>>>>>>>> JBoss Developer
>>>>>>>>>>>>> M: +55-61-9269-6576
>>>>>>>>>>>>>
>>>>>>>>>>>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Better technology. Faster innovation. Powered by community
>>>>>>>>>>>>> collaboration.
>>>>>>>>>>>>> See how it works at www.redhat.com
>>>>>>>>>>>>>
>>>>>>>>>>>>> <linkedin.png> <youtube.png>
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>>>>> Paul.
>>>>>>>>>>>>
>>>>>>>>>>>> -- 
>>>>>>>>>>>> Paul Robinson
>>>>>>>>>>>> JBoss Developer Team Lead (www.jboss.org)
>>>>>>>>>>>>
>>>>>>>>>>>> JBoss, a Division of Red Hat
>>>>>>>>>>>> Registered in England and Wales under Company Registration No.
>>>>>>>>>>>> 03798903
>>>>>>>>>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt
>>>>>>>>>>>> Parson (US), Paul Hickey (Ireland)
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>>> Paul.
>>>>>>>>>>
>>>>>>>>>> -- 
>>>>>>>>>> Paul Robinson
>>>>>>>>>> JBoss Developer Team Lead (www.jboss.org)
>>>>>>>>>>
>>>>>>>>>> JBoss, a Division of Red Hat
>>>>>>>>>> Registered in England and Wales under Company Registration No.
>>>>>>>>>> 03798903
>>>>>>>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt
>>>>>>>>>> Parson (US), Paul Hickey (Ireland)
>>>>>>>>> _______________________________________________
>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>> _______________________________________________
>>>>>>>> jbossdeveloper mailing list
>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>> _______________________________________________
>>>>>>> jbossdeveloper mailing list
>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>> _______________________________________________
>>>>> jbossdeveloper mailing list
>>>>> jbossdeveloper at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>
>> Paul.
>>
>> -- 
>> Paul Robinson
>> JBoss Developer Team Lead (www.jboss.org)
>>
>> JBoss, a Division of Red Hat
>> Registered in England and Wales under Company Registration No. 03798903
>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140908/6f8c3486/attachment-0001.html 

From sgilda at redhat.com  Mon Sep  8 12:03:13 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 08 Sep 2014 12:03:13 -0400
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <540DD06D.2090806@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
Message-ID: <540DD341.80101@redhat.com>

+1.

1. It is not a good practice and we would have to explain why we are 
doing something that is not a best practice.
2. It will just substitute one confusing configuration issue with 
another possibly more confusing configuration issue.


On 09/08/2014 11:51 AM, Rafael Benevides wrote:
> After working on a PoC, I prepared QSTools to inject the <repository 
> /> definition in a _separated profile_ as we do for Archetypes: 
> https://github.com/jboss-developer/jboss-eap-archetypes/blob/6.4.x-develop/jboss-javaee6-webapp-archetype/jboss-repositories-webapp.diff
>
> QSTools ticket: https://issues.jboss.org/browse/JDF-762
>
> But after placing http://maven.repository.redhat.com/techpreview/all/ 
> at the Quickstarts, I realized that we won't solve the user experience 
> issues without adding - 
> https://maven.repository.redhat.com/earlyaccess/ and
> - http://jboss-developer.github.io/temp-maven-repo/ also
> for the -develop branch.
>
> This will generate a management issue because those extra repos will 
> need to be removed for Quickstarts .GA distribution.
>
> If we instruct contributors to place the earlyaccess and 
> temp-maven-repo on settings.xml and add techpreview to pom.xml it can 
> become confusing.
>
> *Summary*: I think that injecting <repository /> would be nice but it 
> will bring an extra management effort and/or some sort of confusion. 
> So it has more cons than pros.
>
> Well, JBDS already brings a Wizard to customize the settings.xml. I 
> think that CLI users have the expertise to know that it's probably a 
> missing configuration than a Quickstarts bug.
>
> Maybe we need to think a little bit more on other solutions for this 
> issue for CLI users.
>
> Em 8/27/14, 12:18, Pete Muir escreveu:
>> I think it is simpler to put the repo in the POM. We have to explain either approach to our users, so we should go with the simpler to explain and understand.
>>
>> On 27 Aug 2014, at 13:29, Paul Robinson<paul.robinson at redhat.com>  wrote:
>>
>>> Pete,
>>>
>>> You mentioned this week that you no longer think the maven plugin was a good idea. What's your thinking now?
>>>
>>> On 27 Aug 2014, at 12:52, Sande Gilda<sgilda at redhat.com>  wrote:
>>>
>>>> Pete suggested this approach last fall. I will forward that email.
>>>>
>>>> Rafael, separately I am also forwarding the email discussed the cons of
>>>> adding the <repository/> to the POM files. :-)
>>>>
>>>>
>>>> On 08/27/2014 04:32 AM, Darran Lofthouse wrote:
>>>>> Wonder if there is any maven plug in that can output a nice message if
>>>>> a condition is not met.
>>>>>
>>>>> Regards,
>>>>> Darran Lofthouse.
>>>>>
>>>>>
>>>>> On 26/08/14 22:27, Rafael Benevides wrote:
>>>>>> Em 8/26/14, 17:56, Sande Gilda escreveu:
>>>>>>> So they, like me, don't RTFM? :-)
>>>>>> ahahahah
>>>>>>> I didn't realize it was an issue. Who is fielding the complaints for
>>>>>>> this? I haven't been aware of any. And is it primarily people who use
>>>>>>> the Maven command line or JDBS?
>>>>>> I believe that it comes mostly by people using CLI since JBDS helps
>>>>>> on this.
>>>>>>
>>>>>> This $subject was reborn by a request from Arun Gupta. It seems that
>>>>>> someone tried to use our Quickstarts and had issues because e forgot to
>>>>>> RTFM :)
>>>>>>> Wouldn't it be easier to try to make the Maven setting configuration
>>>>>>> requirements more prominent? I really don't like the idea of adding
>>>>>>> the Maven repository to the POM files and then telling them it's not a
>>>>>>> good practice. If they see something, they will repeat it because, as
>>>>>>> you said, they don't read the instructions. The whole purpose of the
>>>>>>> quickstarts is to show how to code using best practices.
>>>>>> It's the kind of relax thing that I don't think we will regret because
>>>>>> it has the advantages that I mentioned. Besides the "not being
>>>>>> recommended" I don't see any potential issues for us.
>>>>>>
>>>>>> I remember that you sent me  (more than a year ago) some URLs that
>>>>>> mention the cons on having <repository /> on pom.xml file. Do you mind
>>>>>> sharing it again ?
>>>>>>
>>>>>> Thanks
>>>>>>> On 08/26/2014 04:44 PM, Rafael Benevides wrote:
>>>>>>>> The problem that we're trying to solve is that users don't read the
>>>>>>>> instructions :)
>>>>>>>>
>>>>>>>> So, they don't know that they have to configure the settings.xml until
>>>>>>>> they face a build problem.
>>>>>>>>
>>>>>>>> Em 8/26/14, 14:33, Sande Gilda escreveu:
>>>>>>>>> Sorry, I'm just back from PTO and catching up on this thread.
>>>>>>>>>
>>>>>>>>> I have run the quickstarts using both command line and JDBS without
>>>>>>>>> running into any problems, so I'm not really clear what problem we
>>>>>>>>> are
>>>>>>>>> trying to solve. Are there issues with asking the user to
>>>>>>>>> configure the
>>>>>>>>> settings.xml file with the content we provide?
>>>>>>>>>
>>>>>>>>> I'm adding Paul and Nikoleta to the thread to see how this might
>>>>>>>>> impact
>>>>>>>>> the quickstart testing and release process.
>>>>>>>>>
>>>>>>>>> On 08/26/2014 05:27 AM, Pete Muir wrote:
>>>>>>>>>> On 26 Aug 2014, at 10:26, Paul Robinson<paul.robinson at redhat.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> On 26 Aug 2014, at 10:18, Pete Muir<pmuir at redhat.com>  wrote:
>>>>>>>>>>>
>>>>>>>>>>>> On 26 Aug 2014, at 09:27, Paul Robinson
>>>>>>>>>>>> <paul.robinson at redhat.com>  wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Rafael,
>>>>>>>>>>>>>
>>>>>>>>>>>>> It'd be worth reading the "[Wolf] Revisting embedding
>>>>>>>>>>>>> repositories in POMs for developer materials" thread on
>>>>>>>>>>>>> enterprise-maven-list at redhat.com. There was quite a bit of
>>>>>>>>>>>>> discussion about doing this. The general opinion was that it
>>>>>>>>>>>>> would be a huge win for usability, but there are quite a few
>>>>>>>>>>>>> subtle problems with the approach. For example, productization
>>>>>>>>>>>>> are currently stripping off these repository definitions from
>>>>>>>>>>>>> quickstarts, so any solution is going to need to work for them.
>>>>>>>>>>>> We don?t currently put any repo definitions in quickstarts...
>>>>>>>>>>> Sorry, I should have been clearer. Productization would remove
>>>>>>>>>>> them if they exist. Quote from Julian Coleman:
>>>>>>>>>>>
>>>>>>>>>>>      Right.  Note, also, that the vman tool will strip out the
>>>>>>>>>>> <repositories>
>>>>>>>>>>>      from the POM files that it processes.  This means that all POM
>>>>>>>>>>> files for
>>>>>>>>>>>      the IP builds (FSW/DV/BPMS) will not contain repositories.
>>>>>>>>>>> So, adding
>>>>>>>>>>>      this information to settings.xml seems the only sensible
>>>>>>>>>>> option.
>>>>>>>>>> Not all platforms use vman afaik.
>>>>>>>>>>
>>>>>>>>>>>>> Pete came up with an alternative approach that helps to educate
>>>>>>>>>>>>> the developer about the configuration, in a better way then we
>>>>>>>>>>>>> have ATM (expecting them to read the docs). This approach was to
>>>>>>>>>>>>> include a plugin (that lives in maven central). This plugin
>>>>>>>>>>>>> would detect missing dependencies that would be available had
>>>>>>>>>>>>> the correct repository been defined in the settings.xml. There
>>>>>>>>>>>>> might also be an option to fix the configuration automatically?
>>>>>>>>>>>> I?m not so sure about this any more.
>>>>>>>>>>>>
>>>>>>>>>>>>> Paul.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 25 Aug 2014, at 13:50, Rafael Benevides
>>>>>>>>>>>>> <benevides at redhat.com>  wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On a look for a continuous improvement on developer user
>>>>>>>>>>>>>> experience and also because we have been constantly asked to
>>>>>>>>>>>>>> support issues related to the setup of
>>>>>>>>>>>>>> https://access.redhat.com/maven-repository  to make the
>>>>>>>>>>>>>> quickstarts work, we want to include the <repository />
>>>>>>>>>>>>>> definition on quickstarts pom.xml
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Actually the Archetypes already have the <repository /> on the
>>>>>>>>>>>>>> pom.xml file of the generated project.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The idea here is to have the <repository /> with the
>>>>>>>>>>>>>> https://maven.repository.redhat.com/techpreview/all/  defined on
>>>>>>>>>>>>>> every quickstarts's pom.xml file with a comment on top of it
>>>>>>>>>>>>>> saying that this approach is not recommended but we included it
>>>>>>>>>>>>>> so users can test the quickstarts without further setup and
>>>>>>>>>>>>>> that it's recommended to use settings.xml.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> It will bring the following advantages:
>>>>>>>>>>>>>> - It will make ease to contributors and users
>>>>>>>>>>>>>> - Simplify the build.
>>>>>>>>>>>>>> - Simplify the Archetype synch process / No need to inject the
>>>>>>>>>>>>>> repo since it will come from the Quickstarts
>>>>>>>>>>>>>> - We can add a pre-defined comment above the pom.xml repository
>>>>>>>>>>>>>> definition to explain that we don't recommend that.
>>>>>>>>>>>>>> - We can also add this "comment" to QSTools to check/fix it.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> As a roadmap for it:
>>>>>>>>>>>>>> - We need to document that at the
>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-developer-shared-resources  
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> - We need to update the contributing guides
>>>>>>>>>>>>>> - We need to update QSTools to do this update on all
>>>>>>>>>>>>>> quickstarts for us.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Max, Is there any restrictions on JBDS side ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Anyone else have any objections/comments on this $subject ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Rafael Benevides | Senior Software Engineer
>>>>>>>>>>>>>> JBoss Developer
>>>>>>>>>>>>>> M: +55-61-9269-6576
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Better technology. Faster innovation. Powered by community
>>>>>>>>>>>>>> collaboration.
>>>>>>>>>>>>>> See how it works atwww.redhat.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <linkedin.png> <youtube.png>
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>>>>>> Paul.
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- 
>>>>>>>>>>>>> Paul Robinson
>>>>>>>>>>>>> JBoss Developer Team Lead (www.jboss.org)
>>>>>>>>>>>>>
>>>>>>>>>>>>> JBoss, a Division of Red Hat
>>>>>>>>>>>>> Registered in England and Wales under Company Registration No.
>>>>>>>>>>>>> 03798903
>>>>>>>>>>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt
>>>>>>>>>>>>> Parson (US), Paul Hickey (Ireland)
>>>>>>>>>>>>>
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>>>> Paul.
>>>>>>>>>>>
>>>>>>>>>>> -- 
>>>>>>>>>>> Paul Robinson
>>>>>>>>>>> JBoss Developer Team Lead (www.jboss.org)
>>>>>>>>>>>
>>>>>>>>>>> JBoss, a Division of Red Hat
>>>>>>>>>>> Registered in England and Wales under Company Registration No.
>>>>>>>>>>> 03798903
>>>>>>>>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt
>>>>>>>>>>> Parson (US), Paul Hickey (Ireland)
>>>>>>>>>> _______________________________________________
>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>> _______________________________________________
>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>> _______________________________________________
>>>>>>>> jbossdeveloper mailing list
>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>> _______________________________________________
>>>>>> jbossdeveloper mailing list
>>>>>> jbossdeveloper at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>
>>>> _______________________________________________
>>>> jbossdeveloper mailing list
>>>> jbossdeveloper at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>> Paul.
>>>
>>> -- 
>>> Paul Robinson
>>> JBoss Developer Team Lead (www.jboss.org)
>>>
>>> JBoss, a Division of Red Hat
>>> Registered in England and Wales under Company Registration No. 03798903
>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
>>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140908/0c069d49/attachment-0001.html 

From benevides at redhat.com  Mon Sep  8 12:03:35 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Mon, 08 Sep 2014 13:03:35 -0300
Subject: [jbossdeveloper] EAP 6.3 Archetypes
In-Reply-To: <8C1C5EED-2B26-492C-ADD3-3228677761E6@redhat.com>
References: <52A61D6F.5030007@redhat.com> <52A87250.7040904@redhat.com>
	<D4156F12-D7C7-41BE-85D8-E98D06D4EFAF@redhat.com>
	<52AB090D.2030109@redhat.com>
	<A34F4EDB-F837-40A5-B609-5EAF7BDFA0F2@redhat.com>
	<717CC29D-B14E-479B-803B-A3166F1DCDDA@redhat.com>
	<52AB1169.3080807@redhat.com>
	<A7EDC576-D189-496B-A5E4-B59588641E13@redhat.com>
	<52AB13BE.1020504@redhat.com>
	<D0BDE916-6B86-4D5B-B264-A6B5F729AAFB@redhat.com>
	<52AB1C6E.7030205@redhat.com>
	<27F9BE2B-FFCE-48E2-91C8-D344D57A19E0@redhat.com>
	<52AEE67C.1030901@redhat.com> <52AF0612.4030707@redhat.com>
	<52AF0A43.2060300@redhat.com>
	<67CDC314-7766-43CB-AA45-2DF1850EB561@redhat.com>
	<52B05395.1080702@redhat.com> <5405D990.9030606@redhat.com>
	<54070B99.1030404@redhat.com>
	<73E5CF4F-A61A-40EA-A90F-DA4B95D940A7@redhat.com>
	<54086A32.6050607@redhat.com>
	<8C1C5EED-2B26-492C-ADD3-3228677761E6@redhat.com>
Message-ID: <540DD357.9000802@redhat.com>

JBoss repository ids for EAP and WFK _*Archetypes*_ update to 
*/redhat-techpreview-all-repository/*

EAP : 
https://github.com/jboss-developer/jboss-eap-archetypes/commit/14e71cc68
WFK: 
https://github.com/jboss-developer/jboss-wfk-archetypes/commit/cd57a32c0

Em 9/4/14, 12:29, Burr Sutter escreveu:
> Very good news!
>
> On Sep 4, 2014, at 9:33 AM, Rafael Benevides <benevides at redhat.com> wrote:
>
>> Yesterday Paul and I did the release of EAP 6.3.0 Archetypes.
>>
>> They're now available at Maven Central and I just commited the stacks.yaml:
>> https://github.com/jboss-developer/jboss-stacks/commit/29a753da4
>>
>>  From this release the <repository /> is injected at pom.xml of the archetype generated project as discussed in other threads.
>>
>> Em 9/3/14, 9:38, Pete Muir escreveu:
>>> Thanks Rafael!
>>>
>>> On 3 Sep 2014, at 13:37, Rafael Benevides <benevides at redhat.com> wrote:
>>>
>>>> EAP 6.2.0 Archetypes are at maven central: http://search.maven.org/#search%7Cga%7C1%7Corg.jboss.archetype.eap
>>>>
>>>> Archetypes repo tag: https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA
>>>>
>>>> Stacks updated: https://github.com/jboss-developer/jboss-stacks/commit/cc6ac1ac6
>>>>
>>>>
>>>> Em 9/2/14, 11:52, Rafael Benevides escreveu:
>>>>> I'll check why those archetypes were not synchronized with Maven Central...
>>>>>
>>>>> Em 12/17/13, 11:37, Rafael Benevides escreveu:
>>>>>> Archetypes released at: https://repository.jboss.org/nexus/content/groups/public/org/jboss/archetype/eap/
>>>>>>
>>>>>> Now I'll wait to it be available on Maven Central so I can merge stacks.yaml
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Em 17/12/13 05:29, Martin Malina escreveu:
>>>>>>> On 16. 12. 2013, at 15:12, Rafael Benevides <benevides at redhat.com> wrote:
>>>>>>>
>>>>>>>> Thanks Fred and Martin!
>>>>>>> You?re welcome.
>>>>>>>
>>>>>>>> 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?
>>>>>>> Yes, I believe so.
>>>>>>>
>>>>>>> -Martin
>>>>>>>
>>>>>>>> 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#L2190-L2199
>>>>>>>>>>
>>>>>>>>>> ,6.2.0 points to the new archetypes:
>>>>>>>>>> https://github.com/rafabene/jdf-stack/blob/eap62Archetypes/stacks.yaml#L2229-L2234
>>>>>>>>>>
>>>>>>>>>> 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 at redhat.com
>>>>>>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>>>>>>> <mailto:benevides at 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/CONTRIBUTING.md
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 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 at redhat.com
>>>>>>>>>>>>>>> <mailto:benevides at 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 at redhat.com
>>>>>>>>>>>>>>>>> <mailto:pmuir at redhat.com>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Martin, are you able to test this out?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On 13 Dec 2013, at 13:18, Rafael Benevides
>>>>>>>>>>>>>>>>>> <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Hi guys.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I did:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 1 - Prepared EAP 6.2 Archetypes:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Synch:
>>>>>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/commit/d532e54d6c4a5fb038b8f8376d4dffba8430f42d
>>>>>>>>>>>>>>>>>>> Tag:
>>>>>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.0.GA
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 2- Release EAP 6.2 Archetype in a staged repo:
>>>>>>>>>>>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2274/
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140908/e7ece701/attachment.html 

From pmuir at redhat.com  Mon Sep  8 12:40:52 2014
From: pmuir at redhat.com (Pete Muir)
Date: Mon, 8 Sep 2014 17:40:52 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <540DD06D.2090806@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
Message-ID: <E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>


On 8 Sep 2014, at 16:51, Rafael Benevides <benevides at redhat.com> wrote:

> After working on a PoC, I prepared QSTools to inject the <repository /> definition in a separated profile as we do for Archetypes: https://github.com/jboss-developer/jboss-eap-archetypes/blob/6.4.x-develop/jboss-javaee6-webapp-archetype/jboss-repositories-webapp.diff

When does the injection happen?

> 
> QSTools ticket: https://issues.jboss.org/browse/JDF-762
> 
> But after placing http://maven.repository.redhat.com/techpreview/all/ at the Quickstarts, I realized that we won't solve the user experience issues without adding - https://maven.repository.redhat.com/earlyaccess/ and 
> - http://jboss-developer.github.io/temp-maven-repo/ also 
> for the -develop branch.

I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.

> 
> This will generate a management issue because those extra repos will need to be removed for Quickstarts .GA distribution.
> 
> If we instruct contributors to place the earlyaccess and temp-maven-repo on settings.xml and add techpreview to pom.xml it can become confusing.
> 
> Summary: I think that injecting <repository /> would be nice but it will bring an extra management effort and/or some sort of confusion. So it has more cons than pros.
> 
> Well, JBDS already brings a Wizard to customize the settings.xml. I think that CLI users have the expertise to know that it's probably a missing configuration than a Quickstarts bug.
> 
> Maybe we need to think a little bit more on other solutions for this issue for CLI users.
> 
> Em 8/27/14, 12:18, Pete Muir escreveu:
>> I think it is simpler to put the repo in the POM. We have to explain either approach to our users, so we should go with the simpler to explain and understand.
>> 
>> On 27 Aug 2014, at 13:29, Paul Robinson 
>> <paul.robinson at redhat.com>
>>  wrote:
>> 
>> 
>>> Pete,
>>> 
>>> You mentioned this week that you no longer think the maven plugin was a good idea. What's your thinking now?
>>> 
>>> On 27 Aug 2014, at 12:52, Sande Gilda 
>>> <sgilda at redhat.com>
>>>  wrote:
>>> 
>>> 
>>>> Pete suggested this approach last fall. I will forward that email.
>>>> 
>>>> Rafael, separately I am also forwarding the email discussed the cons of 
>>>> adding the <repository/> to the POM files. :-)
>>>> 
>>>> 
>>>> On 08/27/2014 04:32 AM, Darran Lofthouse wrote:
>>>> 
>>>>> Wonder if there is any maven plug in that can output a nice message if 
>>>>> a condition is not met.
>>>>> 
>>>>> Regards,
>>>>> Darran Lofthouse.
>>>>> 
>>>>> 
>>>>> On 26/08/14 22:27, Rafael Benevides wrote:
>>>>> 
>>>>>> Em 8/26/14, 17:56, Sande Gilda escreveu:
>>>>>> 
>>>>>>> So they, like me, don't RTFM? :-)
>>>>>>> 
>>>>>> ahahahah
>>>>>> 
>>>>>>> I didn't realize it was an issue. Who is fielding the complaints for
>>>>>>> this? I haven't been aware of any. And is it primarily people who use
>>>>>>> the Maven command line or JDBS?
>>>>>>> 
>>>>>> I believe that it comes mostly by people using CLI since JBDS helps 
>>>>>> on this.
>>>>>> 
>>>>>> This $subject was reborn by a request from Arun Gupta. It seems that
>>>>>> someone tried to use our Quickstarts and had issues because e forgot to
>>>>>> RTFM :)
>>>>>> 
>>>>>>> Wouldn't it be easier to try to make the Maven setting configuration
>>>>>>> requirements more prominent? I really don't like the idea of adding
>>>>>>> the Maven repository to the POM files and then telling them it's not a
>>>>>>> good practice. If they see something, they will repeat it because, as
>>>>>>> you said, they don't read the instructions. The whole purpose of the
>>>>>>> quickstarts is to show how to code using best practices.
>>>>>>> 
>>>>>> It's the kind of relax thing that I don't think we will regret because
>>>>>> it has the advantages that I mentioned. Besides the "not being
>>>>>> recommended" I don't see any potential issues for us.
>>>>>> 
>>>>>> I remember that you sent me  (more than a year ago) some URLs that
>>>>>> mention the cons on having <repository /> on pom.xml file. Do you mind
>>>>>> sharing it again ?
>>>>>> 
>>>>>> Thanks
>>>>>> 
>>>>>>> 
>>>>>>> On 08/26/2014 04:44 PM, Rafael Benevides wrote:
>>>>>>> 
>>>>>>>> The problem that we're trying to solve is that users don't read the
>>>>>>>> instructions :)
>>>>>>>> 
>>>>>>>> So, they don't know that they have to configure the settings.xml until
>>>>>>>> they face a build problem.
>>>>>>>> 
>>>>>>>> Em 8/26/14, 14:33, Sande Gilda escreveu:
>>>>>>>> 
>>>>>>>>> Sorry, I'm just back from PTO and catching up on this thread.
>>>>>>>>> 
>>>>>>>>> I have run the quickstarts using both command line and JDBS without
>>>>>>>>> running into any problems, so I'm not really clear what problem we 
>>>>>>>>> are
>>>>>>>>> trying to solve. Are there issues with asking the user to 
>>>>>>>>> configure the
>>>>>>>>> settings.xml file with the content we provide?
>>>>>>>>> 
>>>>>>>>> I'm adding Paul and Nikoleta to the thread to see how this might 
>>>>>>>>> impact
>>>>>>>>> the quickstart testing and release process.
>>>>>>>>> 
>>>>>>>>> On 08/26/2014 05:27 AM, Pete Muir wrote:
>>>>>>>>> 
>>>>>>>>>> On 26 Aug 2014, at 10:26, Paul Robinson <paul.robinson at redhat.com>
>>>>>>>>>> 
>>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> On 26 Aug 2014, at 10:18, Pete Muir <pmuir at redhat.com>
>>>>>>>>>>>  wrote:
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> On 26 Aug 2014, at 09:27, Paul Robinson
>>>>>>>>>>>> 
>>>>>>>>>>>> <paul.robinson at redhat.com>
>>>>>>>>>>>>  wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>>> Rafael,
>>>>>>>>>>>>> 
>>>>>>>>>>>>> It'd be worth reading the "[Wolf] Revisting embedding
>>>>>>>>>>>>> repositories in POMs for developer materials" thread on
>>>>>>>>>>>>> 
>>>>>>>>>>>>> enterprise-maven-list at redhat.com
>>>>>>>>>>>>> . There was quite a bit of
>>>>>>>>>>>>> discussion about doing this. The general opinion was that it
>>>>>>>>>>>>> would be a huge win for usability, but there are quite a few
>>>>>>>>>>>>> subtle problems with the approach. For example, productization
>>>>>>>>>>>>> are currently stripping off these repository definitions from
>>>>>>>>>>>>> quickstarts, so any solution is going to need to work for them.
>>>>>>>>>>>>> 
>>>>>>>>>>>> We don?t currently put any repo definitions in quickstarts...
>>>>>>>>>>>> 
>>>>>>>>>>> Sorry, I should have been clearer. Productization would remove
>>>>>>>>>>> them if they exist. Quote from Julian Coleman:
>>>>>>>>>>> 
>>>>>>>>>>>     Right.  Note, also, that the vman tool will strip out the
>>>>>>>>>>> <repositories>
>>>>>>>>>>>     from the POM files that it processes.  This means that all POM
>>>>>>>>>>> files for
>>>>>>>>>>>     the IP builds (FSW/DV/BPMS) will not contain repositories.
>>>>>>>>>>> So, adding
>>>>>>>>>>>     this information to settings.xml seems the only sensible 
>>>>>>>>>>> option.
>>>>>>>>>>> 
>>>>>>>>>> Not all platforms use vman afaik.
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>>>> Pete came up with an alternative approach that helps to educate
>>>>>>>>>>>>> the developer about the configuration, in a better way then we
>>>>>>>>>>>>> have ATM (expecting them to read the docs). This approach was to
>>>>>>>>>>>>> include a plugin (that lives in maven central). This plugin
>>>>>>>>>>>>> would detect missing dependencies that would be available had
>>>>>>>>>>>>> the correct repository been defined in the settings.xml. There
>>>>>>>>>>>>> might also be an option to fix the configuration automatically?
>>>>>>>>>>>>> 
>>>>>>>>>>>> I?m not so sure about this any more.
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>>> Paul.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On 25 Aug 2014, at 13:50, Rafael Benevides
>>>>>>>>>>>>> 
>>>>>>>>>>>>> <benevides at redhat.com>
>>>>>>>>>>>>>  wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On a look for a continuous improvement on developer user
>>>>>>>>>>>>>> experience and also because we have been constantly asked to
>>>>>>>>>>>>>> support issues related to the setup of
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> https://access.redhat.com/maven-repository
>>>>>>>>>>>>>>  to make the
>>>>>>>>>>>>>> quickstarts work, we want to include the <repository />
>>>>>>>>>>>>>> definition on quickstarts pom.xml
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Actually the Archetypes already have the <repository /> on the
>>>>>>>>>>>>>> pom.xml file of the generated project.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> The idea here is to have the <repository /> with the
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> https://maven.repository.redhat.com/techpreview/all/
>>>>>>>>>>>>>>  defined on
>>>>>>>>>>>>>> every quickstarts's pom.xml file with a comment on top of it
>>>>>>>>>>>>>> saying that this approach is not recommended but we included it
>>>>>>>>>>>>>> so users can test the quickstarts without further setup and
>>>>>>>>>>>>>> that it's recommended to use settings.xml.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> It will bring the following advantages:
>>>>>>>>>>>>>> - It will make ease to contributors and users
>>>>>>>>>>>>>> - Simplify the build.
>>>>>>>>>>>>>> - Simplify the Archetype synch process / No need to inject the
>>>>>>>>>>>>>> repo since it will come from the Quickstarts
>>>>>>>>>>>>>> - We can add a pre-defined comment above the pom.xml repository
>>>>>>>>>>>>>> definition to explain that we don't recommend that.
>>>>>>>>>>>>>> - We can also add this "comment" to QSTools to check/fix it.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> As a roadmap for it:
>>>>>>>>>>>>>> - We need to document that at the
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-developer-shared-resources
>>>>>>>>>>>>>>  
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> - We need to update the contributing guides
>>>>>>>>>>>>>> - We need to update QSTools to do this update on all
>>>>>>>>>>>>>> quickstarts for us.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Max, Is there any restrictions on JBDS side ?
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Anyone else have any objections/comments on this $subject ?
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Rafael Benevides | Senior Software Engineer
>>>>>>>>>>>>>> JBoss Developer
>>>>>>>>>>>>>> M: +55-61-9269-6576
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Better technology. Faster innovation. Powered by community
>>>>>>>>>>>>>> collaboration.
>>>>>>>>>>>>>> See how it works at 
>>>>>>>>>>>>>> www.redhat.com
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> <linkedin.png> <youtube.png>
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>>>>>> Paul.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> -- 
>>>>>>>>>>>>> Paul Robinson
>>>>>>>>>>>>> JBoss Developer Team Lead (
>>>>>>>>>>>>> www.jboss.org
>>>>>>>>>>>>> )
>>>>>>>>>>>>> 
>>>>>>>>>>>>> JBoss, a Division of Red Hat
>>>>>>>>>>>>> Registered in England and Wales under Company Registration No.
>>>>>>>>>>>>> 03798903
>>>>>>>>>>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt
>>>>>>>>>>>>> Parson (US), Paul Hickey (Ireland)
>>>>>>>>>>>>> 
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>>>> 
>>>>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>>>> Paul.
>>>>>>>>>>> 
>>>>>>>>>>> -- 
>>>>>>>>>>> Paul Robinson
>>>>>>>>>>> JBoss Developer Team Lead (
>>>>>>>>>>> www.jboss.org
>>>>>>>>>>> )
>>>>>>>>>>> 
>>>>>>>>>>> JBoss, a Division of Red Hat
>>>>>>>>>>> Registered in England and Wales under Company Registration No.
>>>>>>>>>>> 03798903
>>>>>>>>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt
>>>>>>>>>>> Parson (US), Paul Hickey (Ireland)
>>>>>>>>>>> 
>>>>>>>>>> _______________________________________________
>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>> 
>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>> _______________________________________________
>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>> 
>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>> _______________________________________________
>>>>>>>> jbossdeveloper mailing list
>>>>>>>> 
>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>> _______________________________________________
>>>>>> jbossdeveloper mailing list
>>>>>> 
>>>>>> jbossdeveloper at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>> 
>>>>>> 
>>>>>> 
>>>> _______________________________________________
>>>> jbossdeveloper mailing list
>>>> 
>>>> jbossdeveloper at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>> 
>>> Paul.
>>> 
>>> -- 
>>> Paul Robinson
>>> JBoss Developer Team Lead (
>>> www.jboss.org
>>> )
>>> 
>>> JBoss, a Division of Red Hat
>>> Registered in England and Wales under Company Registration No. 03798903
>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
>>> 
>>> 
> 



From benevides at redhat.com  Mon Sep  8 12:45:19 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Mon, 08 Sep 2014 13:45:19 -0300
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
Message-ID: <540DDD1F.5020206@redhat.com>


Em 9/8/14, 13:40, Pete Muir escreveu:
> On 8 Sep 2014, at 16:51, Rafael Benevides <benevides at redhat.com> wrote:
>
>> After working on a PoC, I prepared QSTools to inject the <repository /> definition in a separated profile as we do for Archetypes: https://github.com/jboss-developer/jboss-eap-archetypes/blob/6.4.x-develop/jboss-javaee6-webapp-archetype/jboss-repositories-webapp.diff
> When does the injection happen?
For Archetypes, during the build, after QSTools synchs it with the 
Quickstarts: 
https://github.com/jboss-developer/jboss-eap-archetypes/blob/6.4.x-develop/jboss-javaee6-webapp-archetype/pom.xml#L99

For Quickstarts, it was a new Fixer added to the :fix goal. -> 
https://github.com/jboss-developer/maven-qstools-plugin/blob/1675b26cb2e3957e8edf278d8aad4c996e46a4ce/src/main/java/org/jboss/maven/plugins/qstools/fixers/RepositoryFixer.java

>
>> QSTools ticket: https://issues.jboss.org/browse/JDF-762
>>
>> But after placing http://maven.repository.redhat.com/techpreview/all/ at the Quickstarts, I realized that we won't solve the user experience issues without adding - https://maven.repository.redhat.com// and
>> - http://jboss-developer.github.io/temp-maven-repo/ also
>> for the -develop branch.
> I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
So I assume that we need to inject 
http://maven.repository.redhat.com/techpreview/all/ in pom.xml and make 
them to add the others in settings.xml
>
>> This will generate a management issue because those extra repos will need to be removed for Quickstarts .GA distribution.
>>
>> If we instruct contributors to place the earlyaccess and temp-maven-repo on settings.xml and add techpreview to pom.xml it can become confusing.
>>
>> Summary: I think that injecting <repository /> would be nice but it will bring an extra management effort and/or some sort of confusion. So it has more cons than pros.
>>
>> Well, JBDS already brings a Wizard to customize the settings.xml. I think that CLI users have the expertise to know that it's probably a missing configuration than a Quickstarts bug.
>>
>> Maybe we need to think a little bit more on other solutions for this issue for CLI users.
>>
>> Em 8/27/14, 12:18, Pete Muir escreveu:
>>> I think it is simpler to put the repo in the POM. We have to explain either approach to our users, so we should go with the simpler to explain and understand.
>>>
>>> On 27 Aug 2014, at 13:29, Paul Robinson
>>> <paul.robinson at redhat.com>
>>>   wrote:
>>>
>>>
>>>> Pete,
>>>>
>>>> You mentioned this week that you no longer think the maven plugin was a good idea. What's your thinking now?
>>>>
>>>> On 27 Aug 2014, at 12:52, Sande Gilda
>>>> <sgilda at redhat.com>
>>>>   wrote:
>>>>
>>>>
>>>>> Pete suggested this approach last fall. I will forward that email.
>>>>>
>>>>> Rafael, separately I am also forwarding the email discussed the cons of
>>>>> adding the <repository/> to the POM files. :-)
>>>>>
>>>>>
>>>>> On 08/27/2014 04:32 AM, Darran Lofthouse wrote:
>>>>>
>>>>>> Wonder if there is any maven plug in that can output a nice message if
>>>>>> a condition is not met.
>>>>>>
>>>>>> Regards,
>>>>>> Darran Lofthouse.
>>>>>>
>>>>>>
>>>>>> On 26/08/14 22:27, Rafael Benevides wrote:
>>>>>>
>>>>>>> Em 8/26/14, 17:56, Sande Gilda escreveu:
>>>>>>>
>>>>>>>> So they, like me, don't RTFM? :-)
>>>>>>>>
>>>>>>> ahahahah
>>>>>>>
>>>>>>>> I didn't realize it was an issue. Who is fielding the complaints for
>>>>>>>> this? I haven't been aware of any. And is it primarily people who use
>>>>>>>> the Maven command line or JDBS?
>>>>>>>>
>>>>>>> I believe that it comes mostly by people using CLI since JBDS helps
>>>>>>> on this.
>>>>>>>
>>>>>>> This $subject was reborn by a request from Arun Gupta. It seems that
>>>>>>> someone tried to use our Quickstarts and had issues because e forgot to
>>>>>>> RTFM :)
>>>>>>>
>>>>>>>> Wouldn't it be easier to try to make the Maven setting configuration
>>>>>>>> requirements more prominent? I really don't like the idea of adding
>>>>>>>> the Maven repository to the POM files and then telling them it's not a
>>>>>>>> good practice. If they see something, they will repeat it because, as
>>>>>>>> you said, they don't read the instructions. The whole purpose of the
>>>>>>>> quickstarts is to show how to code using best practices.
>>>>>>>>
>>>>>>> It's the kind of relax thing that I don't think we will regret because
>>>>>>> it has the advantages that I mentioned. Besides the "not being
>>>>>>> recommended" I don't see any potential issues for us.
>>>>>>>
>>>>>>> I remember that you sent me  (more than a year ago) some URLs that
>>>>>>> mention the cons on having <repository /> on pom.xml file. Do you mind
>>>>>>> sharing it again ?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>>> On 08/26/2014 04:44 PM, Rafael Benevides wrote:
>>>>>>>>
>>>>>>>>> The problem that we're trying to solve is that users don't read the
>>>>>>>>> instructions :)
>>>>>>>>>
>>>>>>>>> So, they don't know that they have to configure the settings.xml until
>>>>>>>>> they face a build problem.
>>>>>>>>>
>>>>>>>>> Em 8/26/14, 14:33, Sande Gilda escreveu:
>>>>>>>>>
>>>>>>>>>> Sorry, I'm just back from PTO and catching up on this thread.
>>>>>>>>>>
>>>>>>>>>> I have run the quickstarts using both command line and JDBS without
>>>>>>>>>> running into any problems, so I'm not really clear what problem we
>>>>>>>>>> are
>>>>>>>>>> trying to solve. Are there issues with asking the user to
>>>>>>>>>> configure the
>>>>>>>>>> settings.xml file with the content we provide?
>>>>>>>>>>
>>>>>>>>>> I'm adding Paul and Nikoleta to the thread to see how this might
>>>>>>>>>> impact
>>>>>>>>>> the quickstart testing and release process.
>>>>>>>>>>
>>>>>>>>>> On 08/26/2014 05:27 AM, Pete Muir wrote:
>>>>>>>>>>
>>>>>>>>>>> On 26 Aug 2014, at 10:26, Paul Robinson <paul.robinson at redhat.com>
>>>>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On 26 Aug 2014, at 10:18, Pete Muir <pmuir at redhat.com>
>>>>>>>>>>>>   wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> On 26 Aug 2014, at 09:27, Paul Robinson
>>>>>>>>>>>>>
>>>>>>>>>>>>> <paul.robinson at redhat.com>
>>>>>>>>>>>>>   wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Rafael,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> It'd be worth reading the "[Wolf] Revisting embedding
>>>>>>>>>>>>>> repositories in POMs for developer materials" thread on
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> enterprise-maven-list at redhat.com
>>>>>>>>>>>>>> . There was quite a bit of
>>>>>>>>>>>>>> discussion about doing this. The general opinion was that it
>>>>>>>>>>>>>> would be a huge win for usability, but there are quite a few
>>>>>>>>>>>>>> subtle problems with the approach. For example, productization
>>>>>>>>>>>>>> are currently stripping off these repository definitions from
>>>>>>>>>>>>>> quickstarts, so any solution is going to need to work for them.
>>>>>>>>>>>>>>
>>>>>>>>>>>>> We don?t currently put any repo definitions in quickstarts...
>>>>>>>>>>>>>
>>>>>>>>>>>> Sorry, I should have been clearer. Productization would remove
>>>>>>>>>>>> them if they exist. Quote from Julian Coleman:
>>>>>>>>>>>>
>>>>>>>>>>>>      Right.  Note, also, that the vman tool will strip out the
>>>>>>>>>>>> <repositories>
>>>>>>>>>>>>      from the POM files that it processes.  This means that all POM
>>>>>>>>>>>> files for
>>>>>>>>>>>>      the IP builds (FSW/DV/BPMS) will not contain repositories.
>>>>>>>>>>>> So, adding
>>>>>>>>>>>>      this information to settings.xml seems the only sensible
>>>>>>>>>>>> option.
>>>>>>>>>>>>
>>>>>>>>>>> Not all platforms use vman afaik.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>>> Pete came up with an alternative approach that helps to educate
>>>>>>>>>>>>>> the developer about the configuration, in a better way then we
>>>>>>>>>>>>>> have ATM (expecting them to read the docs). This approach was to
>>>>>>>>>>>>>> include a plugin (that lives in maven central). This plugin
>>>>>>>>>>>>>> would detect missing dependencies that would be available had
>>>>>>>>>>>>>> the correct repository been defined in the settings.xml. There
>>>>>>>>>>>>>> might also be an option to fix the configuration automatically?
>>>>>>>>>>>>>>
>>>>>>>>>>>>> I?m not so sure about this any more.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Paul.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 25 Aug 2014, at 13:50, Rafael Benevides
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <benevides at redhat.com>
>>>>>>>>>>>>>>   wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On a look for a continuous improvement on developer user
>>>>>>>>>>>>>>> experience and also because we have been constantly asked to
>>>>>>>>>>>>>>> support issues related to the setup of
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> https://access.redhat.com/maven-repository
>>>>>>>>>>>>>>>   to make the
>>>>>>>>>>>>>>> quickstarts work, we want to include the <repository />
>>>>>>>>>>>>>>> definition on quickstarts pom.xml
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Actually the Archetypes already have the <repository /> on the
>>>>>>>>>>>>>>> pom.xml file of the generated project.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The idea here is to have the <repository /> with the
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> https://maven.repository.redhat.com/techpreview/all/
>>>>>>>>>>>>>>>   defined on
>>>>>>>>>>>>>>> every quickstarts's pom.xml file with a comment on top of it
>>>>>>>>>>>>>>> saying that this approach is not recommended but we included it
>>>>>>>>>>>>>>> so users can test the quickstarts without further setup and
>>>>>>>>>>>>>>> that it's recommended to use settings.xml.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> It will bring the following advantages:
>>>>>>>>>>>>>>> - It will make ease to contributors and users
>>>>>>>>>>>>>>> - Simplify the build.
>>>>>>>>>>>>>>> - Simplify the Archetype synch process / No need to inject the
>>>>>>>>>>>>>>> repo since it will come from the Quickstarts
>>>>>>>>>>>>>>> - We can add a pre-defined comment above the pom.xml repository
>>>>>>>>>>>>>>> definition to explain that we don't recommend that.
>>>>>>>>>>>>>>> - We can also add this "comment" to QSTools to check/fix it.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> As a roadmap for it:
>>>>>>>>>>>>>>> - We need to document that at the
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-developer-shared-resources
>>>>>>>>>>>>>>>   
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> - We need to update the contributing guides
>>>>>>>>>>>>>>> - We need to update QSTools to do this update on all
>>>>>>>>>>>>>>> quickstarts for us.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Max, Is there any restrictions on JBDS side ?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Anyone else have any objections/comments on this $subject ?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Rafael Benevides | Senior Software Engineer
>>>>>>>>>>>>>>> JBoss Developer
>>>>>>>>>>>>>>> M: +55-61-9269-6576
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Better technology. Faster innovation. Powered by community
>>>>>>>>>>>>>>> collaboration.
>>>>>>>>>>>>>>> See how it works at
>>>>>>>>>>>>>>> www.redhat.com
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <linkedin.png> <youtube.png>
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>>>>>>> Paul.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>> Paul Robinson
>>>>>>>>>>>>>> JBoss Developer Team Lead (
>>>>>>>>>>>>>> www.jboss.org
>>>>>>>>>>>>>> )
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> JBoss, a Division of Red Hat
>>>>>>>>>>>>>> Registered in England and Wales under Company Registration No.
>>>>>>>>>>>>>> 03798903
>>>>>>>>>>>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt
>>>>>>>>>>>>>> Parson (US), Paul Hickey (Ireland)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>>>>> Paul.
>>>>>>>>>>>>
>>>>>>>>>>>> -- 
>>>>>>>>>>>> Paul Robinson
>>>>>>>>>>>> JBoss Developer Team Lead (
>>>>>>>>>>>> www.jboss.org
>>>>>>>>>>>> )
>>>>>>>>>>>>
>>>>>>>>>>>> JBoss, a Division of Red Hat
>>>>>>>>>>>> Registered in England and Wales under Company Registration No.
>>>>>>>>>>>> 03798903
>>>>>>>>>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt
>>>>>>>>>>>> Parson (US), Paul Hickey (Ireland)
>>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>>
>>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>>> _______________________________________________
>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>
>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>> _______________________________________________
>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>
>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>> _______________________________________________
>>>>>>> jbossdeveloper mailing list
>>>>>>>
>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>
>>>>>>>
>>>>>>>
>>>>> _______________________________________________
>>>>> jbossdeveloper mailing list
>>>>>
>>>>> jbossdeveloper at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>> Paul.
>>>>
>>>> -- 
>>>> Paul Robinson
>>>> JBoss Developer Team Lead (
>>>> www.jboss.org
>>>> )
>>>>
>>>> JBoss, a Division of Red Hat
>>>> Registered in England and Wales under Company Registration No. 03798903
>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
>>>>
>>>>


From pmuir at redhat.com  Mon Sep  8 12:48:19 2014
From: pmuir at redhat.com (Pete Muir)
Date: Mon, 8 Sep 2014 17:48:19 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <540DDD1F.5020206@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
Message-ID: <ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>


On 8 Sep 2014, at 17:45, Rafael Benevides <benevides at redhat.com> wrote:

> 
> Em 9/8/14, 13:40, Pete Muir escreveu:
>> On 8 Sep 2014, at 16:51, Rafael Benevides <benevides at redhat.com> wrote:
>> 
>>> After working on a PoC, I prepared QSTools to inject the <repository /> definition in a separated profile as we do for Archetypes: https://github.com/jboss-developer/jboss-eap-archetypes/blob/6.4.x-develop/jboss-javaee6-webapp-archetype/jboss-repositories-webapp.diff
>> When does the injection happen?
> For Archetypes, during the build, after QSTools synchs it with the Quickstarts: https://github.com/jboss-developer/jboss-eap-archetypes/blob/6.4.x-develop/jboss-javaee6-webapp-archetype/pom.xml#L99
> 
> For Quickstarts, it was a new Fixer added to the :fix goal. -> https://github.com/jboss-developer/maven-qstools-plugin/blob/1675b26cb2e3957e8edf278d8aad4c996e46a4ce/src/main/java/org/jboss/maven/plugins/qstools/fixers/RepositoryFixer.java
> 
>> 
>>> QSTools ticket: https://issues.jboss.org/browse/JDF-762
>>> 
>>> But after placing http://maven.repository.redhat.com/techpreview/all/ at the Quickstarts, I realized that we won't solve the user experience issues without adding - https://maven.repository.redhat.com// and
>>> - http://jboss-developer.github.io/temp-maven-repo/ also
>>> for the -develop branch.
>> I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
> So I assume that we need to inject http://maven.repository.redhat.com/techpreview/all/ in pom.xml and make them to add the others in settings.xml

Well, we may want to add earlyaccess too. WDYT?

>> 
>>> This will generate a management issue because those extra repos will need to be removed for Quickstarts .GA distribution.
>>> 
>>> If we instruct contributors to place the earlyaccess and temp-maven-repo on settings.xml and add techpreview to pom.xml it can become confusing.
>>> 
>>> Summary: I think that injecting <repository /> would be nice but it will bring an extra management effort and/or some sort of confusion. So it has more cons than pros.
>>> 
>>> Well, JBDS already brings a Wizard to customize the settings.xml. I think that CLI users have the expertise to know that it's probably a missing configuration than a Quickstarts bug.
>>> 
>>> Maybe we need to think a little bit more on other solutions for this issue for CLI users.
>>> 
>>> Em 8/27/14, 12:18, Pete Muir escreveu:
>>>> I think it is simpler to put the repo in the POM. We have to explain either approach to our users, so we should go with the simpler to explain and understand.
>>>> 
>>>> On 27 Aug 2014, at 13:29, Paul Robinson
>>>> <paul.robinson at redhat.com>
>>>>  wrote:
>>>> 
>>>> 
>>>>> Pete,
>>>>> 
>>>>> You mentioned this week that you no longer think the maven plugin was a good idea. What's your thinking now?
>>>>> 
>>>>> On 27 Aug 2014, at 12:52, Sande Gilda
>>>>> <sgilda at redhat.com>
>>>>>  wrote:
>>>>> 
>>>>> 
>>>>>> Pete suggested this approach last fall. I will forward that email.
>>>>>> 
>>>>>> Rafael, separately I am also forwarding the email discussed the cons of
>>>>>> adding the <repository/> to the POM files. :-)
>>>>>> 
>>>>>> 
>>>>>> On 08/27/2014 04:32 AM, Darran Lofthouse wrote:
>>>>>> 
>>>>>>> Wonder if there is any maven plug in that can output a nice message if
>>>>>>> a condition is not met.
>>>>>>> 
>>>>>>> Regards,
>>>>>>> Darran Lofthouse.
>>>>>>> 
>>>>>>> 
>>>>>>> On 26/08/14 22:27, Rafael Benevides wrote:
>>>>>>> 
>>>>>>>> Em 8/26/14, 17:56, Sande Gilda escreveu:
>>>>>>>> 
>>>>>>>>> So they, like me, don't RTFM? :-)
>>>>>>>>> 
>>>>>>>> ahahahah
>>>>>>>> 
>>>>>>>>> I didn't realize it was an issue. Who is fielding the complaints for
>>>>>>>>> this? I haven't been aware of any. And is it primarily people who use
>>>>>>>>> the Maven command line or JDBS?
>>>>>>>>> 
>>>>>>>> I believe that it comes mostly by people using CLI since JBDS helps
>>>>>>>> on this.
>>>>>>>> 
>>>>>>>> This $subject was reborn by a request from Arun Gupta. It seems that
>>>>>>>> someone tried to use our Quickstarts and had issues because e forgot to
>>>>>>>> RTFM :)
>>>>>>>> 
>>>>>>>>> Wouldn't it be easier to try to make the Maven setting configuration
>>>>>>>>> requirements more prominent? I really don't like the idea of adding
>>>>>>>>> the Maven repository to the POM files and then telling them it's not a
>>>>>>>>> good practice. If they see something, they will repeat it because, as
>>>>>>>>> you said, they don't read the instructions. The whole purpose of the
>>>>>>>>> quickstarts is to show how to code using best practices.
>>>>>>>>> 
>>>>>>>> It's the kind of relax thing that I don't think we will regret because
>>>>>>>> it has the advantages that I mentioned. Besides the "not being
>>>>>>>> recommended" I don't see any potential issues for us.
>>>>>>>> 
>>>>>>>> I remember that you sent me  (more than a year ago) some URLs that
>>>>>>>> mention the cons on having <repository /> on pom.xml file. Do you mind
>>>>>>>> sharing it again ?
>>>>>>>> 
>>>>>>>> Thanks
>>>>>>>> 
>>>>>>>>> On 08/26/2014 04:44 PM, Rafael Benevides wrote:
>>>>>>>>> 
>>>>>>>>>> The problem that we're trying to solve is that users don't read the
>>>>>>>>>> instructions :)
>>>>>>>>>> 
>>>>>>>>>> So, they don't know that they have to configure the settings.xml until
>>>>>>>>>> they face a build problem.
>>>>>>>>>> 
>>>>>>>>>> Em 8/26/14, 14:33, Sande Gilda escreveu:
>>>>>>>>>> 
>>>>>>>>>>> Sorry, I'm just back from PTO and catching up on this thread.
>>>>>>>>>>> 
>>>>>>>>>>> I have run the quickstarts using both command line and JDBS without
>>>>>>>>>>> running into any problems, so I'm not really clear what problem we
>>>>>>>>>>> are
>>>>>>>>>>> trying to solve. Are there issues with asking the user to
>>>>>>>>>>> configure the
>>>>>>>>>>> settings.xml file with the content we provide?
>>>>>>>>>>> 
>>>>>>>>>>> I'm adding Paul and Nikoleta to the thread to see how this might
>>>>>>>>>>> impact
>>>>>>>>>>> the quickstart testing and release process.
>>>>>>>>>>> 
>>>>>>>>>>> On 08/26/2014 05:27 AM, Pete Muir wrote:
>>>>>>>>>>> 
>>>>>>>>>>>> On 26 Aug 2014, at 10:26, Paul Robinson <paul.robinson at redhat.com>
>>>>>>>>>>>> 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>>> On 26 Aug 2014, at 10:18, Pete Muir <pmuir at redhat.com>
>>>>>>>>>>>>>  wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On 26 Aug 2014, at 09:27, Paul Robinson
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> <paul.robinson at redhat.com>
>>>>>>>>>>>>>>  wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Rafael,
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> It'd be worth reading the "[Wolf] Revisting embedding
>>>>>>>>>>>>>>> repositories in POMs for developer materials" thread on
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> enterprise-maven-list at redhat.com
>>>>>>>>>>>>>>> . There was quite a bit of
>>>>>>>>>>>>>>> discussion about doing this. The general opinion was that it
>>>>>>>>>>>>>>> would be a huge win for usability, but there are quite a few
>>>>>>>>>>>>>>> subtle problems with the approach. For example, productization
>>>>>>>>>>>>>>> are currently stripping off these repository definitions from
>>>>>>>>>>>>>>> quickstarts, so any solution is going to need to work for them.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> We don?t currently put any repo definitions in quickstarts...
>>>>>>>>>>>>>> 
>>>>>>>>>>>>> Sorry, I should have been clearer. Productization would remove
>>>>>>>>>>>>> them if they exist. Quote from Julian Coleman:
>>>>>>>>>>>>> 
>>>>>>>>>>>>>     Right.  Note, also, that the vman tool will strip out the
>>>>>>>>>>>>> <repositories>
>>>>>>>>>>>>>     from the POM files that it processes.  This means that all POM
>>>>>>>>>>>>> files for
>>>>>>>>>>>>>     the IP builds (FSW/DV/BPMS) will not contain repositories.
>>>>>>>>>>>>> So, adding
>>>>>>>>>>>>>     this information to settings.xml seems the only sensible
>>>>>>>>>>>>> option.
>>>>>>>>>>>>> 
>>>>>>>>>>>> Not all platforms use vman afaik.
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Pete came up with an alternative approach that helps to educate
>>>>>>>>>>>>>>> the developer about the configuration, in a better way then we
>>>>>>>>>>>>>>> have ATM (expecting them to read the docs). This approach was to
>>>>>>>>>>>>>>> include a plugin (that lives in maven central). This plugin
>>>>>>>>>>>>>>> would detect missing dependencies that would be available had
>>>>>>>>>>>>>>> the correct repository been defined in the settings.xml. There
>>>>>>>>>>>>>>> might also be an option to fix the configuration automatically?
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I?m not so sure about this any more.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Paul.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On 25 Aug 2014, at 13:50, Rafael Benevides
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> <benevides at redhat.com>
>>>>>>>>>>>>>>>  wrote:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On a look for a continuous improvement on developer user
>>>>>>>>>>>>>>>> experience and also because we have been constantly asked to
>>>>>>>>>>>>>>>> support issues related to the setup of
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> https://access.redhat.com/maven-repository
>>>>>>>>>>>>>>>>  to make the
>>>>>>>>>>>>>>>> quickstarts work, we want to include the <repository />
>>>>>>>>>>>>>>>> definition on quickstarts pom.xml
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Actually the Archetypes already have the <repository /> on the
>>>>>>>>>>>>>>>> pom.xml file of the generated project.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> The idea here is to have the <repository /> with the
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> https://maven.repository.redhat.com/techpreview/all/
>>>>>>>>>>>>>>>>  defined on
>>>>>>>>>>>>>>>> every quickstarts's pom.xml file with a comment on top of it
>>>>>>>>>>>>>>>> saying that this approach is not recommended but we included it
>>>>>>>>>>>>>>>> so users can test the quickstarts without further setup and
>>>>>>>>>>>>>>>> that it's recommended to use settings.xml.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> It will bring the following advantages:
>>>>>>>>>>>>>>>> - It will make ease to contributors and users
>>>>>>>>>>>>>>>> - Simplify the build.
>>>>>>>>>>>>>>>> - Simplify the Archetype synch process / No need to inject the
>>>>>>>>>>>>>>>> repo since it will come from the Quickstarts
>>>>>>>>>>>>>>>> - We can add a pre-defined comment above the pom.xml repository
>>>>>>>>>>>>>>>> definition to explain that we don't recommend that.
>>>>>>>>>>>>>>>> - We can also add this "comment" to QSTools to check/fix it.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> As a roadmap for it:
>>>>>>>>>>>>>>>> - We need to document that at the
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> https://github.com/jboss-developer/jboss-developer-shared-resources
>>>>>>>>>>>>>>>>  
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> - We need to update the contributing guides
>>>>>>>>>>>>>>>> - We need to update QSTools to do this update on all
>>>>>>>>>>>>>>>> quickstarts for us.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Max, Is there any restrictions on JBDS side ?
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Anyone else have any objections/comments on this $subject ?
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Rafael Benevides | Senior Software Engineer
>>>>>>>>>>>>>>>> JBoss Developer
>>>>>>>>>>>>>>>> M: +55-61-9269-6576
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Better technology. Faster innovation. Powered by community
>>>>>>>>>>>>>>>> collaboration.
>>>>>>>>>>>>>>>> See how it works at
>>>>>>>>>>>>>>>> www.redhat.com
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> <linkedin.png> <youtube.png>
>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>>>>>>>> Paul.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>>> Paul Robinson
>>>>>>>>>>>>>>> JBoss Developer Team Lead (
>>>>>>>>>>>>>>> www.jboss.org
>>>>>>>>>>>>>>> )
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> JBoss, a Division of Red Hat
>>>>>>>>>>>>>>> Registered in England and Wales under Company Registration No.
>>>>>>>>>>>>>>> 03798903
>>>>>>>>>>>>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt
>>>>>>>>>>>>>>> Parson (US), Paul Hickey (Ireland)
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>>>>>> Paul.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> -- 
>>>>>>>>>>>>> Paul Robinson
>>>>>>>>>>>>> JBoss Developer Team Lead (
>>>>>>>>>>>>> www.jboss.org
>>>>>>>>>>>>> )
>>>>>>>>>>>>> 
>>>>>>>>>>>>> JBoss, a Division of Red Hat
>>>>>>>>>>>>> Registered in England and Wales under Company Registration No.
>>>>>>>>>>>>> 03798903
>>>>>>>>>>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt
>>>>>>>>>>>>> Parson (US), Paul Hickey (Ireland)
>>>>>>>>>>>>> 
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>>> 
>>>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>>> 
>>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>>>> _______________________________________________
>>>>>>>>>> jbossdeveloper mailing list
>>>>>>>>>> 
>>>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>> _______________________________________________
>>>>>>>> jbossdeveloper mailing list
>>>>>>>> 
>>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>> _______________________________________________
>>>>>> jbossdeveloper mailing list
>>>>>> 
>>>>>> jbossdeveloper at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>> Paul.
>>>>> 
>>>>> -- 
>>>>> Paul Robinson
>>>>> JBoss Developer Team Lead (
>>>>> www.jboss.org
>>>>> )
>>>>> 
>>>>> JBoss, a Division of Red Hat
>>>>> Registered in England and Wales under Company Registration No. 03798903
>>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)



From benevides at redhat.com  Mon Sep  8 12:56:57 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Mon, 08 Sep 2014 13:56:57 -0300
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
Message-ID: <540DDFD9.3060003@redhat.com>

I could be wrong but I think that QE will not agree to have the 
"earlyaccess".  Then we will have to remove them before the Quickstarts 
is ready for G.A. Otherwise Quickstarts will be shipped with both repos. 
And removing XML snippets without breaking ( the XML or the build) is 
always harder.

Plus, it will be harder to convince other Quickstarts owners that they 
have to do the same (QSTools will complain about their QSs) because that 
it's part of our JBoss Developer Guidelines.

Em 9/8/14, 13:48, Pete Muir escreveu:
>>>> >>>But after placinghttp://maven.repository.redhat.com/techpreview/all/  at the Quickstarts, I realized that we won't solve the user experience issues without adding -https://maven.repository.redhat.com//  and
>>>> >>>-http://jboss-developer.github.io/temp-maven-repo/  also
>>>> >>>for the -develop branch.
>>> >>I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
>> >So I assume that we need to injecthttp://maven.repository.redhat.com/techpreview/all/  in pom.xml and make them to add the others in settings.xml
> Well, we may want to add earlyaccess too. WDYT?
>


From pmuir at redhat.com  Mon Sep  8 12:59:01 2014
From: pmuir at redhat.com (Pete Muir)
Date: Mon, 8 Sep 2014 17:59:01 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <540DDFD9.3060003@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540DDFD9.3060003@redhat.com>
Message-ID: <9CFCAC23-DDDB-4544-8D50-7AEBC3385B7A@redhat.com>


On 8 Sep 2014, at 17:56, Rafael Benevides <benevides at redhat.com> wrote:

> I could be wrong but I think that QE will not agree to have the "earlyaccess?.  

Tomas?

> Then we will have to remove them before the Quickstarts is ready for G.A. Otherwise Quickstarts will be shipped with both repos. And removing XML snippets without breaking ( the XML or the build) is always harder.
> 
> Plus, it will be harder to convince other Quickstarts owners that they have to do the same (QSTools will complain about their QSs) because that it's part of our JBoss Developer Guidelines.
> 
> Em 9/8/14, 13:48, Pete Muir escreveu:
>>>>> >>>But after placinghttp://maven.repository.redhat.com/techpreview/all/  at the Quickstarts, I realized that we won't solve the user experience issues without adding -https://maven.repository.redhat.com//  and
>>>>> >>>-http://jboss-developer.github.io/temp-maven-repo/  also
>>>>> >>>for the -develop branch.
>>>> >>I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
>>> >So I assume that we need to injecthttp://maven.repository.redhat.com/techpreview/all/  in pom.xml and make them to add the others in settings.xml
>> Well, we may want to add earlyaccess too. WDYT?
>> 
> 



From benevides at redhat.com  Mon Sep  8 14:30:20 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Mon, 08 Sep 2014 15:30:20 -0300
Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7
In-Reply-To: <53FB2B23.6090802@redhat.com>
References: <53FB2B23.6090802@redhat.com>
Message-ID: <540DF5BC.3020103@redhat.com>

Returning the discussion about JBoss Developer Material for Java EE 7,

Arun,

Do you have the list of the 5 features/use cases/quickstarts that we 
want to show, right?  Can you share it?

Thanks

Em 8/25/14, 9:25, Rafael Benevides escreveu:
> Hi All,
>
> We're about to start the update process of JBoss Developer Materials 
> to Java EE 7. But before put the hands on it I talked with Pete and we 
> decided that it's better to bring this $subject to discussion with 
> everyone on this list.
>
> Ticket Monster already started to be updated 
> https://issues.jboss.org/browse/JDF-754
>
> Actually our jboss-eap-quickstarts have been updated to Java EE 7.0 on 
> https://github.com/wildfly/quickstart. Anyway we still miss some Java 
> EE 7 specific features/use cases on these quickstarts.
>
> It seems that Arun Gupta has a list of about 5 features/use 
> cases/quickstarts that we want to show. The idea is to have these Java 
> EE 7 specific quickstarts to be available at www.jboss.org
>
> The main point that we should discuss are:
>
> - What are those quickstarts/features?
> - Where will we host those Java EE 7 quickstarts? 
> https://github.com/jboss-developer/jboss-sandbox-quickstarts ?
> - Paul Robinson,
>
> Considering that the jboss-sandbox-quickstarts github structure, do 
> you think that it could have any issues with it? Can we choose just 
> specific quickstarts to be present at www.jboss.org
>
> Well,
>
> This is just a starting point, so we can discuss about this update 
> process until we have a detailed plan.
>
> The Google docs with the plan is available at: 
> https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit
>
>
> -- 
>
> *Rafael Benevides | Senior Software Engineer*
> JBoss Developer
> M: +55-61-9269-6576
>
> Red Hat
>
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at www.redhat.com <http://www.redhat.com/>
>
> LinkedIn <http://www.linkedin.com/company/3258288> Youtube 
> <https://www.youtube.com/redhatlatam>
>
>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140908/50a9fdfc/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140908/50a9fdfc/attachment.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140908/50a9fdfc/attachment.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140908/50a9fdfc/attachment-0001.png 

From sgilda at redhat.com  Mon Sep  8 15:27:34 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 08 Sep 2014 15:27:34 -0400
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <9CFCAC23-DDDB-4544-8D50-7AEBC3385B7A@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540DDFD9.3060003@redhat.com>
	<9CFCAC23-DDDB-4544-8D50-7AEBC3385B7A@redhat.com>
Message-ID: <540E0326.3050208@redhat.com>

Adding Paul and Nikoleta.

On 09/08/2014 12:59 PM, Pete Muir wrote:
> On 8 Sep 2014, at 17:56, Rafael Benevides <benevides at redhat.com> wrote:
>
>> I could be wrong but I think that QE will not agree to have the "earlyaccess?.
> Tomas?
>
>> Then we will have to remove them before the Quickstarts is ready for G.A. Otherwise Quickstarts will be shipped with both repos. And removing XML snippets without breaking ( the XML or the build) is always harder.
>>
>> Plus, it will be harder to convince other Quickstarts owners that they have to do the same (QSTools will complain about their QSs) because that it's part of our JBoss Developer Guidelines.
>>
>> Em 9/8/14, 13:48, Pete Muir escreveu:
>>>>>>>>> But after placinghttp://maven.repository.redhat.com/techpreview/all/  at the Quickstarts, I realized that we won't solve the user experience issues without adding -https://maven.repository.redhat.com//  and
>>>>>>>>> -http://jboss-developer.github.io/temp-maven-repo/  also
>>>>>>>>> for the -develop branch.
>>>>>>> I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
>>>>> So I assume that we need to injecthttp://maven.repository.redhat.com/techpreview/all/  in pom.xml and make them to add the others in settings.xml
>>> Well, we may want to add earlyaccess too. WDYT?
>>>


From arun.gupta at gmail.com  Tue Sep  9 00:29:03 2014
From: arun.gupta at gmail.com (Arun Gupta)
Date: Tue, 9 Sep 2014 07:29:03 +0300
Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7
In-Reply-To: <540DF5BC.3020103@redhat.com>
References: <53FB2B23.6090802@redhat.com>
	<540DF5BC.3020103@redhat.com>
Message-ID: <CAGBoHQU93pCyWnJVrXE+FS9xT166JSbQUag2YANRcJfByBRqJg@mail.gmail.com>

Hi Rafael,

If you are looking for the top 5 features that should be highlighted in
Java EE 7, then they would be:

- WebSocket server endpoint
- Chunk style batch processing
- Object-based JSON generation and Stream-based JSON consuming
- ManagedExecutorService
- JAX-RS Client API

There are samples for each one of these at:

https://github.com/javaee-samples/javaee7-samples

I had some basic discussions with Vineet last week on where some of these
usecases can be incorporated in Ticket Monster. Please keep me involved in
the design of how TiMo is going to evolve for Java EE 7 support. Some of
the documents that would be very useful from that process are:

- How to migrate an existing Java EE 6 application to EE 7 ? This would be
very useful to our customers as well.
- Compare LOC/deployment descriptors between the EE 6 and 7 versions. These
would make nice graphs.
- Before/after code fragment for different pieces that were migrated.
- What proprietary technologies were replaced with standards-based when
using EE 7

Cheers
Arun

On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides <benevides at redhat.com>
wrote:

>  Returning the discussion about JBoss Developer Material for Java EE 7,
>
> Arun,
>
> Do you have the list of the 5 features/use cases/quickstarts that we want
> to show, right?  Can you share it?
>
> Thanks
>
> Em 8/25/14, 9:25, Rafael Benevides escreveu:
>
> Hi All,
>
> We're about to start the update process of JBoss Developer Materials to
> Java EE 7. But before put the hands on it I talked with Pete and we decided
> that it's better to bring this $subject to discussion with everyone on this
> list.
>
> Ticket Monster already started to be updated
> https://issues.jboss.org/browse/JDF-754
>
> Actually our jboss-eap-quickstarts have been updated to Java EE 7.0 on
> https://github.com/wildfly/quickstart. Anyway we still miss some Java EE
> 7 specific features/use cases on these quickstarts.
>
> It seems that Arun Gupta has a list of about 5 features/use
> cases/quickstarts that we want to show. The idea is to have these Java EE 7
> specific quickstarts to be available at www.jboss.org
>
> The main point that we should discuss are:
>
> - What are those quickstarts/features?
> - Where will we host those Java EE 7 quickstarts?
> https://github.com/jboss-developer/jboss-sandbox-quickstarts ?
> - Paul Robinson,
>
> Considering that the jboss-sandbox-quickstarts github structure, do you
> think that it could have any issues with it? Can we choose just specific
> quickstarts to be present at www.jboss.org
>
> Well,
>
> This is just a starting point, so we can discuss about this update process
> until we have a detailed plan.
>
> The Google docs with the plan is available at:
> https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit
>
>
> --
>
> *Rafael Benevides | Senior Software Engineer*
> JBoss Developer
> M: +55-61-9269-6576
>
> [image: Red Hat]
>
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at www.redhat.com
>
> [image: LinkedIn] <http://www.linkedin.com/company/3258288> [image:
> Youtube] <https://www.youtube.com/redhatlatam>
>
>
> _______________________________________________
> jbossdeveloper mailing listjbossdeveloper at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
>
>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>



-- 
http://blog.arungupta.me
http://twitter.com/arungupta
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/91fb3b6d/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/91fb3b6d/attachment.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/91fb3b6d/attachment.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/91fb3b6d/attachment-0001.png 

From mnovotny at redhat.com  Tue Sep  9 06:35:12 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Tue, 09 Sep 2014 12:35:12 +0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>	<53FCF46F.4010305@redhat.com>
	<53FCFBD2.1010005@redhat.com>	<53FD97B0.6010201@redhat.com>
	<53FDC684.1010203@redhat.com>	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>	<540DD06D.2090806@redhat.com>	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
Message-ID: <540ED7E0.2000303@redhat.com>

On 8.9.2014 18:48, Pete Muir wrote:
>>>> >>> QSTools ticket: https://issues.jboss.org/browse/JDF-762
>>>> >>> 
>>>> >>> But after placing http://maven.repository.redhat.com/techpreview/all/ at the Quickstarts, I realized that we won't solve the user experience issues without adding - https://maven.repository.redhat.com// and
>>>> >>> - http://jboss-developer.github.io/temp-maven-repo/ also
>>>> >>> for the -develop branch.
>>> >> I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
>> > So I assume that we need to inject http://maven.repository.redhat.com/techpreview/all/ in pom.xml and make them to add the others in settings.xml
> Well, we may want to add earlyaccess too. WDYT?
>
Why we should have it there for end users? earlyaccess repository is
just exceptional resource for public Betas, isn't it? Isn't that
confusing to have it there even for traditional GA releases?

-- 
Marek Novotny
--
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno


From mnovotny at redhat.com  Tue Sep  9 06:39:52 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Tue, 09 Sep 2014 12:39:52 +0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>	<53FCF46F.4010305@redhat.com>
	<53FCFBD2.1010005@redhat.com>	<53FD97B0.6010201@redhat.com>
	<53FDC684.1010203@redhat.com>	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
Message-ID: <540ED8F8.4010709@redhat.com>

On 8.9.2014 18:40, Pete Muir wrote:
>> > QSTools ticket: https://issues.jboss.org/browse/JDF-762
>> > 
>> > But after placing http://maven.repository.redhat.com/techpreview/all/ at the Quickstarts, I realized that we won't solve the user experience issues without adding - https://maven.repository.redhat.com/earlyaccess/ and 
>> > - http://jboss-developer.github.io/temp-maven-repo/ also 
>> > for the -develop branch.
> I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
>
besides that, we can't release non-GA versions (except public betas), so
external contributors won't have the versions defined in BOMs anyway.

-- 
Marek Novotny
--
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno


From pmuir at redhat.com  Tue Sep  9 07:00:11 2014
From: pmuir at redhat.com (Pete Muir)
Date: Tue, 9 Sep 2014 12:00:11 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <540ED7E0.2000303@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>	<53FCF46F.4010305@redhat.com>
	<53FCFBD2.1010005@redhat.com>	<53FD97B0.6010201@redhat.com>
	<53FDC684.1010203@redhat.com>	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>	<540DD06D.2090806@redhat.com>	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
Message-ID: <B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>


On 9 Sep 2014, at 11:35, Marek Novotny <mnovotny at redhat.com> wrote:

> On 8.9.2014 18:48, Pete Muir wrote:
>>>>>>>> QSTools ticket: https://issues.jboss.org/browse/JDF-762
>>>>>>>> 
>>>>>>>> But after placing http://maven.repository.redhat.com/techpreview/all/ at the Quickstarts, I realized that we won't solve the user experience issues without adding - https://maven.repository.redhat.com// and
>>>>>>>> - http://jboss-developer.github.io/temp-maven-repo/ also
>>>>>>>> for the -develop branch.
>>>>>> I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
>>>> So I assume that we need to inject http://maven.repository.redhat.com/techpreview/all/ in pom.xml and make them to add the others in settings.xml
>> Well, we may want to add earlyaccess too. WDYT?
>> 
> Why we should have it there for end users? earlyaccess repository is
> just exceptional resource for public Betas, isn't it? Isn't that
> confusing to have it there even for traditional GA releases?

OTOH this is not really the way Maven works. In Maven you tend to mix up all releases, and use version numbers to control what gets pulled in.

> 
> -- 
> Marek Novotny
> --
> WFK and Seam Product Lead
> 
> Red Hat Czech s.r.o.
> Purkynova 99
> 612 45 Brno
> 
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper



From benevides at redhat.com  Tue Sep  9 07:45:07 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 09 Sep 2014 08:45:07 -0300
Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7
In-Reply-To: <CAGBoHQU93pCyWnJVrXE+FS9xT166JSbQUag2YANRcJfByBRqJg@mail.gmail.com>
References: <53FB2B23.6090802@redhat.com>	<540DF5BC.3020103@redhat.com>
	<CAGBoHQU93pCyWnJVrXE+FS9xT166JSbQUag2YANRcJfByBRqJg@mail.gmail.com>
Message-ID: <540EE843.7060402@redhat.com>

Thanks!

Em 9/9/14, 1:29, Arun Gupta escreveu:
> Hi Rafael,
>
> If you are looking for the top 5 features that should be highlighted 
> in Java EE 7, then they would be:
>
> - WebSocket server endpoint
> - Chunk style batch processing
> - Object-based JSON generation and Stream-based JSON consuming
> - ManagedExecutorService
> - JAX-RS Client API
>
> There are samples for each one of these at:
>
> https://github.com/javaee-samples/javaee7-samples
>
> I had some basic discussions with Vineet last week on where some of 
> these usecases can be incorporated in Ticket Monster. Please keep me 
> involved in the design of how TiMo is going to evolve for Java EE 7 
> support. Some of the documents that would be very useful from that 
> process are:
>
> - How to migrate an existing Java EE 6 application to EE 7 ? This 
> would be very useful to our customers as well.
> - Compare LOC/deployment descriptors between the EE 6 and 7 versions. 
> These would make nice graphs.
> - Before/after code fragment for different pieces that were migrated.
> - What proprietary technologies were replaced with standards-based 
> when using EE 7
>
> Cheers
> Arun
>
> On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides <benevides at redhat.com 
> <mailto:benevides at redhat.com>> wrote:
>
>     Returning the discussion about JBoss Developer Material for Java EE 7,
>
>     Arun,
>
>     Do you have the list of the 5 features/use cases/quickstarts that
>     we want to show, right?  Can you share it?
>
>     Thanks
>
>     Em 8/25/14, 9:25, Rafael Benevides escreveu:
>>     Hi All,
>>
>>     We're about to start the update process of JBoss Developer
>>     Materials to Java EE 7. But before put the hands on it I talked
>>     with Pete and we decided that it's better to bring this $subject
>>     to discussion with everyone on this list.
>>
>>     Ticket Monster already started to be updated
>>     https://issues.jboss.org/browse/JDF-754
>>
>>     Actually our jboss-eap-quickstarts have been updated to Java EE
>>     7.0 on https://github.com/wildfly/quickstart. Anyway we still
>>     miss some Java EE 7 specific features/use cases on these quickstarts.
>>
>>     It seems that Arun Gupta has a list of about 5 features/use
>>     cases/quickstarts that we want to show. The idea is to have these
>>     Java EE 7 specific quickstarts to be available at www.jboss.org
>>     <http://www.jboss.org>
>>
>>     The main point that we should discuss are:
>>
>>     - What are those quickstarts/features?
>>     - Where will we host those Java EE 7 quickstarts?
>>     https://github.com/jboss-developer/jboss-sandbox-quickstarts ?
>>     - Paul Robinson,
>>
>>     Considering that the jboss-sandbox-quickstarts github structure,
>>     do you think that it could have any issues with it? Can we choose
>>     just specific quickstarts to be present at www.jboss.org
>>     <http://www.jboss.org>
>>
>>     Well,
>>
>>     This is just a starting point, so we can discuss about this
>>     update process until we have a detailed plan.
>>
>>     The Google docs with the plan is available at:
>>     https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit
>>
>>
>>     -- 
>>
>>     *Rafael Benevides | Senior Software Engineer*
>>     JBoss Developer
>>     M: +55-61-9269-6576 <tel:%2B55-61-9269-6576>
>>
>>     Red Hat
>>
>>     Better technology. Faster innovation. Powered by community
>>     collaboration.
>>     See how it works at www.redhat.com <http://www.redhat.com/>
>>
>>     LinkedIn <http://www.linkedin.com/company/3258288> Youtube
>>     <https://www.youtube.com/redhatlatam>
>>
>>
>>     _______________________________________________
>>     jbossdeveloper mailing list
>>     jbossdeveloper at lists.jboss.org  <mailto:jbossdeveloper at lists.jboss.org>
>>     https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
>
>     _______________________________________________
>     jbossdeveloper mailing list
>     jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
>
>
>
> -- 
> http://blog.arungupta.me
> http://twitter.com/arungupta

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/df659eeb/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/df659eeb/attachment.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/df659eeb/attachment.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/df659eeb/attachment-0001.png 

From mnovotny at redhat.com  Tue Sep  9 07:54:21 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Tue, 09 Sep 2014 13:54:21 +0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>	<53FCF46F.4010305@redhat.com>
	<53FCFBD2.1010005@redhat.com>	<53FD97B0.6010201@redhat.com>
	<53FDC684.1010203@redhat.com>	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>	<540DD06D.2090806@redhat.com>	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
Message-ID: <540EEA6D.9060108@redhat.com>

On 9.9.2014 13:00, Pete Muir wrote:
> On 9 Sep 2014, at 11:35, Marek Novotny <mnovotny at redhat.com> wrote:
>
>> On 8.9.2014 18:48, Pete Muir wrote:
>>>>>>>>> QSTools ticket: https://issues.jboss.org/browse/JDF-762
>>>>>>>>>
>>>>>>>>> But after placing http://maven.repository.redhat.com/techpreview/all/ at the Quickstarts, I realized that we won't solve the user experience issues without adding - https://maven.repository.redhat.com// and
>>>>>>>>> - http://jboss-developer.github.io/temp-maven-repo/ also
>>>>>>>>> for the -develop branch.
>>>>>>> I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
>>>>> So I assume that we need to inject http://maven.repository.redhat.com/techpreview/all/ in pom.xml and make them to add the others in settings.xml
>>> Well, we may want to add earlyaccess too. WDYT?
>>>
>> Why we should have it there for end users? earlyaccess repository is
>> just exceptional resource for public Betas, isn't it? Isn't that
>> confusing to have it there even for traditional GA releases?
> OTOH this is not really the way Maven works. In Maven you tend to mix up all releases, and use version numbers to control what gets pulled in.
Even I agree with your statement, do we have a clean description there
what could end users understand why we have a bunch or repositories
there instead of one? We declared today that you can use our product
maven repository (online techpreview/all or offline zipped repository)
plus Central and then in Quickstarts we use "another" repository.

I agree that injected repository will help to an end user, but wouldn't
it be simple just as one repository?

you can easily manage versions in BOM imports etc. but for the learning
purpose it can be confusing. WDYT?
>
>> -- 
>> Marek Novotny
>> --
>> WFK and Seam Product Lead
>>
>> Red Hat Czech s.r.o.
>> Purkynova 99
>> 612 45 Brno
>>
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


-- 
Marek Novotny
--
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno


From pmuir at redhat.com  Tue Sep  9 07:56:43 2014
From: pmuir at redhat.com (Pete Muir)
Date: Tue, 9 Sep 2014 12:56:43 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <540EEA6D.9060108@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>	<53FCF46F.4010305@redhat.com>
	<53FCFBD2.1010005@redhat.com>	<53FD97B0.6010201@redhat.com>
	<53FDC684.1010203@redhat.com>	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>	<540DD06D.2090806@redhat.com>	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
	<540EEA6D.9060108@redhat.com>
Message-ID: <34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>


On 9 Sep 2014, at 12:54, Marek Novotny <mnovotny at redhat.com> wrote:

> On 9.9.2014 13:00, Pete Muir wrote:
>> On 9 Sep 2014, at 11:35, Marek Novotny <mnovotny at redhat.com> wrote:
>> 
>>> On 8.9.2014 18:48, Pete Muir wrote:
>>>>>>>>>> QSTools ticket: https://issues.jboss.org/browse/JDF-762
>>>>>>>>>> 
>>>>>>>>>> But after placing http://maven.repository.redhat.com/techpreview/all/ at the Quickstarts, I realized that we won't solve the user experience issues without adding - https://maven.repository.redhat.com// and
>>>>>>>>>> - http://jboss-developer.github.io/temp-maven-repo/ also
>>>>>>>>>> for the -develop branch.
>>>>>>>> I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
>>>>>> So I assume that we need to inject http://maven.repository.redhat.com/techpreview/all/ in pom.xml and make them to add the others in settings.xml
>>>> Well, we may want to add earlyaccess too. WDYT?
>>>> 
>>> Why we should have it there for end users? earlyaccess repository is
>>> just exceptional resource for public Betas, isn't it? Isn't that
>>> confusing to have it there even for traditional GA releases?
>> OTOH this is not really the way Maven works. In Maven you tend to mix up all releases, and use version numbers to control what gets pulled in.
> Even I agree with your statement, do we have a clean description there
> what could end users understand why we have a bunch or repositories
> there instead of one? We declared today that you can use our product
> maven repository (online techpreview/all or offline zipped repository)
> plus Central and then in Quickstarts we use "another" repository.
> 
> I agree that injected repository will help to an end user, but wouldn't
> it be simple just as one repository?
> 
> you can easily manage versions in BOM imports etc. but for the learning
> purpose it can be confusing. WDYT?

Hmm. People are used to adding a second repo for snapshots, which is kinda similar.

>> 
>>> -- 
>>> Marek Novotny
>>> --
>>> WFK and Seam Product Lead
>>> 
>>> Red Hat Czech s.r.o.
>>> Purkynova 99
>>> 612 45 Brno
>>> 
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
> 
> 
> -- 
> Marek Novotny
> --
> WFK and Seam Product Lead
> 
> Red Hat Czech s.r.o.
> Purkynova 99
> 612 45 Brno



From mnovotny at redhat.com  Tue Sep  9 08:06:07 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Tue, 09 Sep 2014 14:06:07 +0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>	<53FCF46F.4010305@redhat.com>
	<53FCFBD2.1010005@redhat.com>	<53FD97B0.6010201@redhat.com>
	<53FDC684.1010203@redhat.com>	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>	<540DD06D.2090806@redhat.com>	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
	<540EEA6D.9060108@redhat.com>
	<34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>
Message-ID: <540EED2F.9080407@redhat.com>

On 9.9.2014 13:56, Pete Muir wrote:
> On 9 Sep 2014, at 12:54, Marek Novotny <mnovotny at redhat.com> wrote:
>
>> On 9.9.2014 13:00, Pete Muir wrote:
>>> On 9 Sep 2014, at 11:35, Marek Novotny <mnovotny at redhat.com> wrote:
>>>
>>>> On 8.9.2014 18:48, Pete Muir wrote:
>>>>>>>>>>> QSTools ticket: https://issues.jboss.org/browse/JDF-762
>>>>>>>>>>>
>>>>>>>>>>> But after placing http://maven.repository.redhat.com/techpreview/all/ at the Quickstarts, I realized that we won't solve the user experience issues without adding - https://maven.repository.redhat.com// and
>>>>>>>>>>> - http://jboss-developer.github.io/temp-maven-repo/ also
>>>>>>>>>>> for the -develop branch.
>>>>>>>>> I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
>>>>>>> So I assume that we need to inject http://maven.repository.redhat.com/techpreview/all/ in pom.xml and make them to add the others in settings.xml
>>>>> Well, we may want to add earlyaccess too. WDYT?
>>>>>
>>>> Why we should have it there for end users? earlyaccess repository is
>>>> just exceptional resource for public Betas, isn't it? Isn't that
>>>> confusing to have it there even for traditional GA releases?
>>> OTOH this is not really the way Maven works. In Maven you tend to mix up all releases, and use version numbers to control what gets pulled in.
>> Even I agree with your statement, do we have a clean description there
>> what could end users understand why we have a bunch or repositories
>> there instead of one? We declared today that you can use our product
>> maven repository (online techpreview/all or offline zipped repository)
>> plus Central and then in Quickstarts we use "another" repository.
>>
>> I agree that injected repository will help to an end user, but wouldn't
>> it be simple just as one repository?
>>
>> you can easily manage versions in BOM imports etc. but for the learning
>> purpose it can be confusing. WDYT?
> Hmm. People are used to adding a second repo for snapshots, which is kinda similar.
>
What are our target group of developers for quicksktarts? Newbies or
experienced devs?

I may see it more like short and simple bootstrap for newbies, but your
view is probably different.


-- 
Marek Novotny
--
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno


From pmuir at redhat.com  Tue Sep  9 08:27:24 2014
From: pmuir at redhat.com (Pete Muir)
Date: Tue, 9 Sep 2014 13:27:24 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <540EED2F.9080407@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>	<53FCF46F.4010305@redhat.com>
	<53FCFBD2.1010005@redhat.com>	<53FD97B0.6010201@redhat.com>
	<53FDC684.1010203@redhat.com>	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>	<540DD06D.2090806@redhat.com>	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
	<540EEA6D.9060108@redhat.com>
	<34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>
	<540EED2F.9080407@redhat.com>
Message-ID: <5280B001-83D7-491D-AB9E-EAB7258D7E3C@redhat.com>


On 9 Sep 2014, at 13:06, Marek Novotny <mnovotny at redhat.com> wrote:

> On 9.9.2014 13:56, Pete Muir wrote:
>> On 9 Sep 2014, at 12:54, Marek Novotny <mnovotny at redhat.com> wrote:
>> 
>>> On 9.9.2014 13:00, Pete Muir wrote:
>>>> On 9 Sep 2014, at 11:35, Marek Novotny <mnovotny at redhat.com> wrote:
>>>> 
>>>>> On 8.9.2014 18:48, Pete Muir wrote:
>>>>>>>>>>>> QSTools ticket: https://issues.jboss.org/browse/JDF-762
>>>>>>>>>>>> 
>>>>>>>>>>>> But after placing http://maven.repository.redhat.com/techpreview/all/ at the Quickstarts, I realized that we won't solve the user experience issues without adding - https://maven.repository.redhat.com// and
>>>>>>>>>>>> - http://jboss-developer.github.io/temp-maven-repo/ also
>>>>>>>>>>>> for the -develop branch.
>>>>>>>>>> I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
>>>>>>>> So I assume that we need to inject http://maven.repository.redhat.com/techpreview/all/ in pom.xml and make them to add the others in settings.xml
>>>>>> Well, we may want to add earlyaccess too. WDYT?
>>>>>> 
>>>>> Why we should have it there for end users? earlyaccess repository is
>>>>> just exceptional resource for public Betas, isn't it? Isn't that
>>>>> confusing to have it there even for traditional GA releases?
>>>> OTOH this is not really the way Maven works. In Maven you tend to mix up all releases, and use version numbers to control what gets pulled in.
>>> Even I agree with your statement, do we have a clean description there
>>> what could end users understand why we have a bunch or repositories
>>> there instead of one? We declared today that you can use our product
>>> maven repository (online techpreview/all or offline zipped repository)
>>> plus Central and then in Quickstarts we use "another" repository.
>>> 
>>> I agree that injected repository will help to an end user, but wouldn't
>>> it be simple just as one repository?
>>> 
>>> you can easily manage versions in BOM imports etc. but for the learning
>>> purpose it can be confusing. WDYT?
>> Hmm. People are used to adding a second repo for snapshots, which is kinda similar.
>> 
> What are our target group of developers for quicksktarts? Newbies or
> experienced devs?
> 
> I may see it more like short and simple bootstrap for newbies, but your
> view is probably different.

Agreed on newbies. Hence why we don?t want to make people add/remove repos, but have a sensible default configured for them.

> 
> 
> -- 
> Marek Novotny
> --
> WFK and Seam Product Lead
> 
> Red Hat Czech s.r.o.
> Purkynova 99
> 612 45 Brno



From benevides at redhat.com  Tue Sep  9 08:53:39 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 09 Sep 2014 09:53:39 -0300
Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7
In-Reply-To: <CAGBoHQU93pCyWnJVrXE+FS9xT166JSbQUag2YANRcJfByBRqJg@mail.gmail.com>
References: <53FB2B23.6090802@redhat.com>	<540DF5BC.3020103@redhat.com>
	<CAGBoHQU93pCyWnJVrXE+FS9xT166JSbQUag2YANRcJfByBRqJg@mail.gmail.com>
Message-ID: <540EF853.9080405@redhat.com>

I create a ticket for each one of them in case some of you want to 
follow the progress.

- WebSocket server endpoint - https://issues.jboss.org/browse/JDF-765
- Chunk style batch processing - https://issues.jboss.org/browse/JDF-766
- Object-based JSON generation and Stream-based JSON consuming - 
https://issues.jboss.org/browse/JDF-767
- ManagedExecutorService - https://issues.jboss.org/browse/JDF-768
- JAX-RS Client API - https://issues.jboss.org/browse/JDF-769


Em 9/9/14, 1:29, Arun Gupta escreveu:
> Hi Rafael,
>
> If you are looking for the top 5 features that should be highlighted 
> in Java EE 7, then they would be:
>
> - WebSocket server endpoint
> - Chunk style batch processing
> - Object-based JSON generation and Stream-based JSON consuming
> - ManagedExecutorService
> - JAX-RS Client API
>
> There are samples for each one of these at:
>
> https://github.com/javaee-samples/javaee7-samples
>
> I had some basic discussions with Vineet last week on where some of 
> these usecases can be incorporated in Ticket Monster. Please keep me 
> involved in the design of how TiMo is going to evolve for Java EE 7 
> support. Some of the documents that would be very useful from that 
> process are:
>
> - How to migrate an existing Java EE 6 application to EE 7 ? This 
> would be very useful to our customers as well.
> - Compare LOC/deployment descriptors between the EE 6 and 7 versions. 
> These would make nice graphs.
> - Before/after code fragment for different pieces that were migrated.
> - What proprietary technologies were replaced with standards-based 
> when using EE 7
>
> Cheers
> Arun
>
> On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides <benevides at redhat.com 
> <mailto:benevides at redhat.com>> wrote:
>
>     Returning the discussion about JBoss Developer Material for Java EE 7,
>
>     Arun,
>
>     Do you have the list of the 5 features/use cases/quickstarts that
>     we want to show, right?  Can you share it?
>
>     Thanks
>
>     Em 8/25/14, 9:25, Rafael Benevides escreveu:
>>     Hi All,
>>
>>     We're about to start the update process of JBoss Developer
>>     Materials to Java EE 7. But before put the hands on it I talked
>>     with Pete and we decided that it's better to bring this $subject
>>     to discussion with everyone on this list.
>>
>>     Ticket Monster already started to be updated
>>     https://issues.jboss.org/browse/JDF-754
>>
>>     Actually our jboss-eap-quickstarts have been updated to Java EE
>>     7.0 on https://github.com/wildfly/quickstart. Anyway we still
>>     miss some Java EE 7 specific features/use cases on these quickstarts.
>>
>>     It seems that Arun Gupta has a list of about 5 features/use
>>     cases/quickstarts that we want to show. The idea is to have these
>>     Java EE 7 specific quickstarts to be available at www.jboss.org
>>     <http://www.jboss.org>
>>
>>     The main point that we should discuss are:
>>
>>     - What are those quickstarts/features?
>>     - Where will we host those Java EE 7 quickstarts?
>>     https://github.com/jboss-developer/jboss-sandbox-quickstarts ?
>>     - Paul Robinson,
>>
>>     Considering that the jboss-sandbox-quickstarts github structure,
>>     do you think that it could have any issues with it? Can we choose
>>     just specific quickstarts to be present at www.jboss.org
>>     <http://www.jboss.org>
>>
>>     Well,
>>
>>     This is just a starting point, so we can discuss about this
>>     update process until we have a detailed plan.
>>
>>     The Google docs with the plan is available at:
>>     https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit
>>
>>
>>     -- 
>>
>>     *Rafael Benevides | Senior Software Engineer*
>>     JBoss Developer
>>     M: +55-61-9269-6576 <tel:%2B55-61-9269-6576>
>>
>>     Red Hat
>>
>>     Better technology. Faster innovation. Powered by community
>>     collaboration.
>>     See how it works at www.redhat.com <http://www.redhat.com/>
>>
>>     LinkedIn <http://www.linkedin.com/company/3258288> Youtube
>>     <https://www.youtube.com/redhatlatam>
>>
>>
>>     _______________________________________________
>>     jbossdeveloper mailing list
>>     jbossdeveloper at lists.jboss.org  <mailto:jbossdeveloper at lists.jboss.org>
>>     https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
>
>     _______________________________________________
>     jbossdeveloper mailing list
>     jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
>
>
>
> -- 
> http://blog.arungupta.me
> http://twitter.com/arungupta

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/00dbe320/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/00dbe320/attachment-0001.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/00dbe320/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/00dbe320/attachment-0003.png 

From arun.gupta at gmail.com  Tue Sep  9 09:07:58 2014
From: arun.gupta at gmail.com (Arun Gupta)
Date: Tue, 9 Sep 2014 16:07:58 +0300
Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7
In-Reply-To: <540EF853.9080405@redhat.com>
References: <53FB2B23.6090802@redhat.com> <540DF5BC.3020103@redhat.com>
	<CAGBoHQU93pCyWnJVrXE+FS9xT166JSbQUag2YANRcJfByBRqJg@mail.gmail.com>
	<540EF853.9080405@redhat.com>
Message-ID: <CAGBoHQVoM6vgDnppe3MGCywtQN6Uxjg8zFiD74xaPo4yn81gmQ@mail.gmail.com>

Thanks, now watching!

On Tue, Sep 9, 2014 at 3:53 PM, Rafael Benevides <benevides at redhat.com>
wrote:

>  I create a ticket for each one of them in case some of you want to follow
> the progress.
>
> - WebSocket server endpoint - https://issues.jboss.org/browse/JDF-765
> - Chunk style batch processing - https://issues.jboss.org/browse/JDF-766
> - Object-based JSON generation and Stream-based JSON consuming -
> https://issues.jboss.org/browse/JDF-767
> - ManagedExecutorService - https://issues.jboss.org/browse/JDF-768
> - JAX-RS Client API - https://issues.jboss.org/browse/JDF-769
>
>
> Em 9/9/14, 1:29, Arun Gupta escreveu:
>
> Hi Rafael,
>
>  If you are looking for the top 5 features that should be highlighted in
> Java EE 7, then they would be:
>
>  - WebSocket server endpoint
> - Chunk style batch processing
> - Object-based JSON generation and Stream-based JSON consuming
> - ManagedExecutorService
> - JAX-RS Client API
>
>  There are samples for each one of these at:
>
>  https://github.com/javaee-samples/javaee7-samples
>
>  I had some basic discussions with Vineet last week on where some of
> these usecases can be incorporated in Ticket Monster. Please keep me
> involved in the design of how TiMo is going to evolve for Java EE 7
> support. Some of the documents that would be very useful from that process
> are:
>
>  - How to migrate an existing Java EE 6 application to EE 7 ? This would
> be very useful to our customers as well.
> - Compare LOC/deployment descriptors between the EE 6 and 7 versions.
> These would make nice graphs.
> - Before/after code fragment for different pieces that were migrated.
> - What proprietary technologies were replaced with standards-based when
> using EE 7
>
>  Cheers
> Arun
>
> On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides <benevides at redhat.com>
> wrote:
>
>>  Returning the discussion about JBoss Developer Material for Java EE 7,
>>
>> Arun,
>>
>> Do you have the list of the 5 features/use cases/quickstarts that we want
>> to show, right?  Can you share it?
>>
>> Thanks
>>
>> Em 8/25/14, 9:25, Rafael Benevides escreveu:
>>
>>  Hi All,
>>
>> We're about to start the update process of JBoss Developer Materials to
>> Java EE 7. But before put the hands on it I talked with Pete and we decided
>> that it's better to bring this $subject to discussion with everyone on this
>> list.
>>
>> Ticket Monster already started to be updated
>> https://issues.jboss.org/browse/JDF-754
>>
>> Actually our jboss-eap-quickstarts have been updated to Java EE 7.0 on
>> https://github.com/wildfly/quickstart. Anyway we still miss some Java EE
>> 7 specific features/use cases on these quickstarts.
>>
>> It seems that Arun Gupta has a list of about 5 features/use
>> cases/quickstarts that we want to show. The idea is to have these Java EE 7
>> specific quickstarts to be available at www.jboss.org
>>
>> The main point that we should discuss are:
>>
>> - What are those quickstarts/features?
>> - Where will we host those Java EE 7 quickstarts?
>> https://github.com/jboss-developer/jboss-sandbox-quickstarts ?
>> - Paul Robinson,
>>
>> Considering that the jboss-sandbox-quickstarts github structure, do you
>> think that it could have any issues with it? Can we choose just specific
>> quickstarts to be present at www.jboss.org
>>
>> Well,
>>
>> This is just a starting point, so we can discuss about this update
>> process until we have a detailed plan.
>>
>> The Google docs with the plan is available at:
>> https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit
>>
>>
>> --
>>
>> *Rafael Benevides | Senior Software Engineer*
>> JBoss Developer
>> M: +55-61-9269-6576
>>
>> [image: Red Hat]
>>
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at www.redhat.com
>>
>> [image: LinkedIn] <http://www.linkedin.com/company/3258288> [image:
>> Youtube] <https://www.youtube.com/redhatlatam>
>>
>>
>>   _______________________________________________
>> jbossdeveloper mailing listjbossdeveloper at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>
>>
>>
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>
>
>
>
>  --
> http://blog.arungupta.me
> http://twitter.com/arungupta
>
>
>


-- 
http://blog.arungupta.me
http://twitter.com/arungupta
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/64bf358b/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/64bf358b/attachment.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/64bf358b/attachment.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140909/64bf358b/attachment-0001.png 

From benevides at redhat.com  Tue Sep  9 10:07:17 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 09 Sep 2014 11:07:17 -0300
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <5280B001-83D7-491D-AB9E-EAB7258D7E3C@redhat.com>
References: <53FB3100.4020501@redhat.com>	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>	<53FCC4E6.2060603@redhat.com>	<53FCF1A1.3000101@redhat.com>	<53FCF46F.4010305@redhat.com>	<53FCFBD2.1010005@redhat.com>	<53FD97B0.6010201@redhat.com>	<53FDC684.1010203@redhat.com>	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>	<540DD06D.2090806@redhat.com>	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>	<540DDD1F.5020206@redhat.com>	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>	<540ED7E0.2000303@redhat.com>	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>	<540EEA6D.9060108@redhat.com>	<34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>	<540EED2F.9080407@redhat.com>
	<5280B001-83D7-491D-AB9E-EAB7258D7E3C@redhat.com>
Message-ID: <540F0995.9030201@redhat.com>

We also need to check that with JBDS, because it's odd that stacks only 
uses "redhat-techpreview-all-repository" as additional repository.

Max/Fred,

Is there any issues having 
https://maven.repository.redhat.com/earlyaccess/all/ as declared inside 
quickstarts pom.xml ?


Em 9/9/14, 9:27, Pete Muir escreveu:
> On 9 Sep 2014, at 13:06, Marek Novotny <mnovotny at redhat.com> wrote:
>
>> On 9.9.2014 13:56, Pete Muir wrote:
>>> On 9 Sep 2014, at 12:54, Marek Novotny <mnovotny at redhat.com> wrote:
>>>
>>>> On 9.9.2014 13:00, Pete Muir wrote:
>>>>> On 9 Sep 2014, at 11:35, Marek Novotny <mnovotny at redhat.com> wrote:
>>>>>
>>>>>> On 8.9.2014 18:48, Pete Muir wrote:
>>>>>>>>>>>>> QSTools ticket: https://issues.jboss.org/browse/JDF-762
>>>>>>>>>>>>>
>>>>>>>>>>>>> But after placing http://maven.repository.redhat.com/techpreview/all/ at the Quickstarts, I realized that we won't solve the user experience issues without adding - https://maven.repository.redhat.com// and
>>>>>>>>>>>>> - http://jboss-developer.github.io/temp-maven-repo/ also
>>>>>>>>>>>>> for the -develop branch.
>>>>>>>>>>> I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
>>>>>>>>> So I assume that we need to inject http://maven.repository.redhat.com/techpreview/all/ in pom.xml and make them to add the others in settings.xml
>>>>>>> Well, we may want to add earlyaccess too. WDYT?
>>>>>>>
>>>>>> Why we should have it there for end users? earlyaccess repository is
>>>>>> just exceptional resource for public Betas, isn't it? Isn't that
>>>>>> confusing to have it there even for traditional GA releases?
>>>>> OTOH this is not really the way Maven works. In Maven you tend to mix up all releases, and use version numbers to control what gets pulled in.
>>>> Even I agree with your statement, do we have a clean description there
>>>> what could end users understand why we have a bunch or repositories
>>>> there instead of one? We declared today that you can use our product
>>>> maven repository (online techpreview/all or offline zipped repository)
>>>> plus Central and then in Quickstarts we use "another" repository.
>>>>
>>>> I agree that injected repository will help to an end user, but wouldn't
>>>> it be simple just as one repository?
>>>>
>>>> you can easily manage versions in BOM imports etc. but for the learning
>>>> purpose it can be confusing. WDYT?
>>> Hmm. People are used to adding a second repo for snapshots, which is kinda similar.
>>>
>> What are our target group of developers for quicksktarts? Newbies or
>> experienced devs?
>>
>> I may see it more like short and simple bootstrap for newbies, but your
>> view is probably different.
> Agreed on newbies. Hence why we don?t want to make people add/remove repos, but have a sensible default configured for them.
>
>>
>> -- 
>> Marek Novotny
>> --
>> WFK and Seam Product Lead
>>
>> Red Hat Czech s.r.o.
>> Purkynova 99
>> 612 45 Brno
>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


From pmuir at redhat.com  Tue Sep 16 05:56:52 2014
From: pmuir at redhat.com (Pete Muir)
Date: Tue, 16 Sep 2014 10:56:52 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <0A6DCC3F-CE9F-45F8-B474-9EE865F382A4@redhat.com>
References: <53FB3100.4020501@redhat.com>
	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>
	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>
	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>
	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>
	<53FCC4E6.2060603@redhat.com> <53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
	<540EEA6D.9060108@redhat.com>
	<34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>
	<540EED2F.9080407@redhat.com>
	<5280B001-83D7-491D-AB9E-EAB7258D7E3C@redhat.com>
	<540F0995.9030201@redhat.com>
	<0A6DCC3F-CE9F-45F8-B474-9EE865F382A4! @redhat.com>
Message-ID: <A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>


On 16 Sep 2014, at 00:27, Max Rydahl Andersen <max.andersen at redhat.com> wrote:

> On 9 Sep 2014, at 16:07, Rafael Benevides wrote:
> 
>> We also need to check that with JBDS, because it's odd that stacks only
>> uses "redhat-techpreview-all-repository" as additional repository.
> 
> because it was the only thing we needed originally.
> 
>> Max/Fred,
>> 
>> Is there any issues having
>> https://maven.repository.redhat.com/earlyaccess/all/ as declared inside
>> quickstarts pom.xml ?
> 
> sorry - but I need to grok when earlyaccess/all is even needed  before answering that ? :)
> 
> My default position would be that if you need earlyaccess you are expected to be able to understand why you need it.
> 
> But i'm not sure if that is true anymore - hence wanting to ask why/when earlyaccess is ever needed ?
> is it for running quickstarts targeting a beta version of EAP ? (meaning no snapshots, but actual all releases in it?)

Right, it?s where we put beta and alpha releases.

> 
> If yes, why doesn't /all get split up in /supported and /earlyaccess and /all will serve the combined result ?

Propose this on the wolf list?

> 
> Meaning we remove the need to have two different repos always handed around but allow those who want the separation to just use /supported if need be.
> 
> i.e. do what maven normally does (use version numbers to separate things) and stop having it be a complex setup for the default case ?
> 
> /max
> 
>> 
>> Em 9/9/14, 9:27, Pete Muir escreveu:
>>> On 9 Sep 2014, at 13:06, Marek Novotny <mnovotny at redhat.com> wrote:
>>> 
>>>> On 9.9.2014 13:56, Pete Muir wrote:
>>>>> On 9 Sep 2014, at 12:54, Marek Novotny <mnovotny at redhat.com> wrote:
>>>>> 
>>>>>> On 9.9.2014 13:00, Pete Muir wrote:
>>>>>>> On 9 Sep 2014, at 11:35, Marek Novotny <mnovotny at redhat.com> wrote:
>>>>>>> 
>>>>>>>> On 8.9.2014 18:48, Pete Muir wrote:
>>>>>>>>>>>>>>> QSTools ticket: https://issues.jboss.org/browse/JDF-762
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> But after placing http://maven.repository.redhat.com/techpreview/all/ at the Quickstarts, I realized that we won't solve the user experience issues without adding - https://maven.repository.redhat.com// and
>>>>>>>>>>>>>>> - http://jboss-developer.github.io/temp-maven-repo/ also
>>>>>>>>>>>>>>> for the -develop branch.
>>>>>>>>>>>>> I?m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
>>>>>>>>>>> So I assume that we need to inject http://maven.repository.redhat.com/techpreview/all/ in pom.xml and make them to add the others in settings.xml
>>>>>>>>> Well, we may want to add earlyaccess too. WDYT?
>>>>>>>>> 
>>>>>>>> Why we should have it there for end users? earlyaccess repository is
>>>>>>>> just exceptional resource for public Betas, isn't it? Isn't that
>>>>>>>> confusing to have it there even for traditional GA releases?
>>>>>>> OTOH this is not really the way Maven works. In Maven you tend to mix up all releases, and use version numbers to control what gets pulled in.
>>>>>> Even I agree with your statement, do we have a clean description there
>>>>>> what could end users understand why we have a bunch or repositories
>>>>>> there instead of one? We declared today that you can use our product
>>>>>> maven repository (online techpreview/all or offline zipped repository)
>>>>>> plus Central and then in Quickstarts we use "another" repository.
>>>>>> 
>>>>>> I agree that injected repository will help to an end user, but wouldn't
>>>>>> it be simple just as one repository?
>>>>>> 
>>>>>> you can easily manage versions in BOM imports etc. but for the learning
>>>>>> purpose it can be confusing. WDYT?
>>>>> Hmm. People are used to adding a second repo for snapshots, which is kinda similar.
>>>>> 
>>>> What are our target group of developers for quicksktarts? Newbies or
>>>> experienced devs?
>>>> 
>>>> I may see it more like short and simple bootstrap for newbies, but your
>>>> view is probably different.
>>> Agreed on newbies. Hence why we don?t want to make people add/remove repos, but have a sensible default configured for them.
>>> 
>>>> 
>>>> -- 
>>>> Marek Novotny
>>>> --
>>>> WFK and Seam Product Lead
>>>> 
>>>> Red Hat Czech s.r.o.
>>>> Purkynova 99
>>>> 612 45 Brno
>>> 
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>> 
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
> 
> 
> /max
> http://about.me/maxandersen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140916/a63e6100/attachment.html 

From paul.robinson at redhat.com  Fri Sep 19 06:56:04 2014
From: paul.robinson at redhat.com (Paul Robinson)
Date: Fri, 19 Sep 2014 11:56:04 +0100
Subject: [jbossdeveloper] Google Books API
Message-ID: <D2FFCB4F-43B3-450E-AD6D-FEFE74277914@redhat.com>

Pete, Jason,

I've temporarily enabled authentication on the Google Books API. We are getting zero builds through at the moment. I'm hoping this will at least get us a new quota that we can use today. I want to get the new FeedHenry banner out and also a preview of the Mobile product pages for review.

FYI: We are using my branch of AwePlug ATM, as a temporary solution.

Pete, you mentioned that the quota is lower for authenticated users? Are you sure about this, I struggled to find any docs to support this. Even if it is, enabling authentication should buy us a few requests to be getting on with.

Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140919/6e77b4d3/attachment.html 

From paul.robinson at redhat.com  Fri Sep 19 07:01:32 2014
From: paul.robinson at redhat.com (Paul Robinson)
Date: Fri, 19 Sep 2014 12:01:32 +0100
Subject: [jbossdeveloper] Google Books API
In-Reply-To: <D2FFCB4F-43B3-450E-AD6D-FEFE74277914@redhat.com>
References: <D2FFCB4F-43B3-450E-AD6D-FEFE74277914@redhat.com>
Message-ID: <8310585B-2A17-4A1D-82C3-11A57453DE60@redhat.com>

I also disabled the periodic build on the production CI job. I didn't want to waste our limited API requests on builds that potentially have no changes. We can run that job on demand until we get a better solution for this issue.

Paul.


On 19 Sep 2014, at 11:56, Paul Robinson <paul.robinson at redhat.com> wrote:

> Pete, Jason,
> 
> I've temporarily enabled authentication on the Google Books API. We are getting zero builds through at the moment. I'm hoping this will at least get us a new quota that we can use today. I want to get the new FeedHenry banner out and also a preview of the Mobile product pages for review.
> 
> FYI: We are using my branch of AwePlug ATM, as a temporary solution.
> 
> Pete, you mentioned that the quota is lower for authenticated users? Are you sure about this, I struggled to find any docs to support this. Even if it is, enabling authentication should buy us a few requests to be getting on with.
> 
> Paul.
> 
> -- 
> Paul Robinson
> JBoss Developer Team Lead (www.jboss.org)
> 
> JBoss, a Division of Red Hat
> Registered in England and Wales under Company Registration No. 03798903
> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
> 
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140919/c0763b7a/attachment-0001.html 

From pmuir at redhat.com  Fri Sep 19 09:33:23 2014
From: pmuir at redhat.com (Pete Muir)
Date: Fri, 19 Sep 2014 14:33:23 +0100
Subject: [jbossdeveloper] Google Books API
In-Reply-To: <D2FFCB4F-43B3-450E-AD6D-FEFE74277914@redhat.com>
References: <D2FFCB4F-43B3-450E-AD6D-FEFE74277914@redhat.com>
Message-ID: <549F74EB-2CCE-4A29-A263-DD32F2D576E0@redhat.com>

Yes, the rate for authenticated users is 1000/day.

On 19 Sep 2014, at 11:56, Paul Robinson <paul.robinson at redhat.com> wrote:

> Pete, Jason,
> 
> I've temporarily enabled authentication on the Google Books API. We are getting zero builds through at the moment. I'm hoping this will at least get us a new quota that we can use today. I want to get the new FeedHenry banner out and also a preview of the Mobile product pages for review.
> 
> FYI: We are using my branch of AwePlug ATM, as a temporary solution.
> 
> Pete, you mentioned that the quota is lower for authenticated users? Are you sure about this, I struggled to find any docs to support this. Even if it is, enabling authentication should buy us a few requests to be getting on with.
> 
> Paul.
> 
> -- 
> Paul Robinson
> JBoss Developer Team Lead (www.jboss.org)
> 
> JBoss, a Division of Red Hat
> Registered in England and Wales under Company Registration No. 03798903
> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140919/03459785/attachment.html 

From pmuir at redhat.com  Fri Sep 19 09:35:54 2014
From: pmuir at redhat.com (Pete Muir)
Date: Fri, 19 Sep 2014 14:35:54 +0100
Subject: [jbossdeveloper] Google Books API
In-Reply-To: <549F74EB-2CCE-4A29-A263-DD32F2D576E0@redhat.com>
References: <D2FFCB4F-43B3-450E-AD6D-FEFE74277914@redhat.com>
	<549F74EB-2CCE-4A29-A263-DD32F2D576E0@redhat.com>
Message-ID: <A0ACF905-2892-4D4A-8EAA-00C8ACB0D8BA@redhat.com>

This is about 25 builds, including any non-cached local builds.

On 19 Sep 2014, at 14:33, Pete Muir <pmuir at redhat.com> wrote:

> Yes, the rate for authenticated users is 1000/day.
> 
> On 19 Sep 2014, at 11:56, Paul Robinson <paul.robinson at redhat.com> wrote:
> 
>> Pete, Jason,
>> 
>> I've temporarily enabled authentication on the Google Books API. We are getting zero builds through at the moment. I'm hoping this will at least get us a new quota that we can use today. I want to get the new FeedHenry banner out and also a preview of the Mobile product pages for review.
>> 
>> FYI: We are using my branch of AwePlug ATM, as a temporary solution.
>> 
>> Pete, you mentioned that the quota is lower for authenticated users? Are you sure about this, I struggled to find any docs to support this. Even if it is, enabling authentication should buy us a few requests to be getting on with.
>> 
>> Paul.
>> 
>> -- 
>> Paul Robinson
>> JBoss Developer Team Lead (www.jboss.org)
>> 
>> JBoss, a Division of Red Hat
>> Registered in England and Wales under Company Registration No. 03798903
>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
>> 
> 
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140919/8089555f/attachment.html 

From paul.robinson at redhat.com  Fri Sep 19 09:37:01 2014
From: paul.robinson at redhat.com (Paul Robinson)
Date: Fri, 19 Sep 2014 14:37:01 +0100
Subject: [jbossdeveloper] Google Books API
In-Reply-To: <549F74EB-2CCE-4A29-A263-DD32F2D576E0@redhat.com>
References: <D2FFCB4F-43B3-450E-AD6D-FEFE74277914@redhat.com>
	<549F74EB-2CCE-4A29-A263-DD32F2D576E0@redhat.com>
Message-ID: <1BC12FAD-5863-4C83-BC43-3510EBC7D5B9@redhat.com>

How many does an un-authenticated user get?

On 19 Sep 2014, at 14:33, Pete Muir <pmuir at redhat.com> wrote:

> Yes, the rate for authenticated users is 1000/day.
> 
> On 19 Sep 2014, at 11:56, Paul Robinson <paul.robinson at redhat.com> wrote:
> 
>> Pete, Jason,
>> 
>> I've temporarily enabled authentication on the Google Books API. We are getting zero builds through at the moment. I'm hoping this will at least get us a new quota that we can use today. I want to get the new FeedHenry banner out and also a preview of the Mobile product pages for review.
>> 
>> FYI: We are using my branch of AwePlug ATM, as a temporary solution.
>> 
>> Pete, you mentioned that the quota is lower for authenticated users? Are you sure about this, I struggled to find any docs to support this. Even if it is, enabling authentication should buy us a few requests to be getting on with.
>> 
>> Paul.
>> 
>> -- 
>> Paul Robinson
>> JBoss Developer Team Lead (www.jboss.org)
>> 
>> JBoss, a Division of Red Hat
>> Registered in England and Wales under Company Registration No. 03798903
>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
>> 
> 


Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140919/7e7bff18/attachment.html 

From paul.robinson at redhat.com  Fri Sep 19 09:40:54 2014
From: paul.robinson at redhat.com (Paul Robinson)
Date: Fri, 19 Sep 2014 14:40:54 +0100
Subject: [jbossdeveloper] Google Books API
In-Reply-To: <1BC12FAD-5863-4C83-BC43-3510EBC7D5B9@redhat.com>
References: <D2FFCB4F-43B3-450E-AD6D-FEFE74277914@redhat.com>
	<549F74EB-2CCE-4A29-A263-DD32F2D576E0@redhat.com>
	<1BC12FAD-5863-4C83-BC43-3510EBC7D5B9@redhat.com>
Message-ID: <6C417C6D-BDE9-431F-BCA1-0CA2985C94B0@redhat.com>

OK, I get your point now.

By authenticating these requests, we make all dev builds go through the same user and thus consume the same quota. Without authentication, dev builds consume separate quotas.

On 19 Sep 2014, at 14:37, Paul Robinson <paul.robinson at redhat.com> wrote:

> How many does an un-authenticated user get?
> 
> On 19 Sep 2014, at 14:33, Pete Muir <pmuir at redhat.com> wrote:
> 
>> Yes, the rate for authenticated users is 1000/day.
>> 
>> On 19 Sep 2014, at 11:56, Paul Robinson <paul.robinson at redhat.com> wrote:
>> 
>>> Pete, Jason,
>>> 
>>> I've temporarily enabled authentication on the Google Books API. We are getting zero builds through at the moment. I'm hoping this will at least get us a new quota that we can use today. I want to get the new FeedHenry banner out and also a preview of the Mobile product pages for review.
>>> 
>>> FYI: We are using my branch of AwePlug ATM, as a temporary solution.
>>> 
>>> Pete, you mentioned that the quota is lower for authenticated users? Are you sure about this, I struggled to find any docs to support this. Even if it is, enabling authentication should buy us a few requests to be getting on with.
>>> 
>>> Paul.
>>> 
>>> -- 
>>> Paul Robinson
>>> JBoss Developer Team Lead (www.jboss.org)
>>> 
>>> JBoss, a Division of Red Hat
>>> Registered in England and Wales under Company Registration No. 03798903
>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
>>> 
>> 
> 
> 
> Paul.
> 
> -- 
> Paul Robinson
> JBoss Developer Team Lead (www.jboss.org)
> 
> JBoss, a Division of Red Hat
> Registered in England and Wales under Company Registration No. 03798903
> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
> 
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140919/751b0a8a/attachment-0001.html 

From pmuir at redhat.com  Fri Sep 19 10:10:57 2014
From: pmuir at redhat.com (Pete Muir)
Date: Fri, 19 Sep 2014 15:10:57 +0100
Subject: [jbossdeveloper] Google Books API
In-Reply-To: <1BC12FAD-5863-4C83-BC43-3510EBC7D5B9@redhat.com>
References: <D2FFCB4F-43B3-450E-AD6D-FEFE74277914@redhat.com>
	<549F74EB-2CCE-4A29-A263-DD32F2D576E0@redhat.com>
	<1BC12FAD-5863-4C83-BC43-3510EBC7D5B9@redhat.com>
Message-ID: <2BF4D232-DE97-405A-AFEC-84020C898513@redhat.com>

Unknown, but it?s a lot lot more than 1000/day spread between every IP we use. The only reason SIN fails is because it?s all reporting as the same IP (RH network exit point).

On 19 Sep 2014, at 14:37, Paul Robinson <paul.robinson at redhat.com> wrote:

> How many does an un-authenticated user get?
> 
> On 19 Sep 2014, at 14:33, Pete Muir <pmuir at redhat.com> wrote:
> 
>> Yes, the rate for authenticated users is 1000/day.
>> 
>> On 19 Sep 2014, at 11:56, Paul Robinson <paul.robinson at redhat.com> wrote:
>> 
>>> Pete, Jason,
>>> 
>>> I've temporarily enabled authentication on the Google Books API. We are getting zero builds through at the moment. I'm hoping this will at least get us a new quota that we can use today. I want to get the new FeedHenry banner out and also a preview of the Mobile product pages for review.
>>> 
>>> FYI: We are using my branch of AwePlug ATM, as a temporary solution.
>>> 
>>> Pete, you mentioned that the quota is lower for authenticated users? Are you sure about this, I struggled to find any docs to support this. Even if it is, enabling authentication should buy us a few requests to be getting on with.
>>> 
>>> Paul.
>>> 
>>> -- 
>>> Paul Robinson
>>> JBoss Developer Team Lead (www.jboss.org)
>>> 
>>> JBoss, a Division of Red Hat
>>> Registered in England and Wales under Company Registration No. 03798903
>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
>>> 
>> 
> 
> 
> Paul.
> 
> -- 
> Paul Robinson
> JBoss Developer Team Lead (www.jboss.org)
> 
> JBoss, a Division of Red Hat
> Registered in England and Wales under Company Registration No. 03798903
> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140919/b1a9febd/attachment.html 

From max.andersen at redhat.com  Mon Sep 22 09:54:26 2014
From: max.andersen at redhat.com (Max Rydahl Andersen)
Date: Mon, 22 Sep 2014 15:54:26 +0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>
References: <53FB3100.4020501@redhat.com>
	<1CC83484-040F-4F81-AC6D-0CF06B4C9159@redhat.com>
	<54528CD2-09AF-4951-938A-B8F5FF165882@redhat.com>
	<89D205BC-CBEB-4B20-9DBA-1FA39B70863D@redhat.com>
	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>
	<53FCC4E6.2060603@redhat.com> <53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
	<540EEA6D.9060108@redhat.com>
	<34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>
	<540EED2F.9080407@redhat.com>
	<5280B001-83D7-491D-AB9E-EAB7258D7E3C@redhat.com>
	<540F0995.9030201@redhat.com>
	<0A6DCC3F-CE9F-45F8-B474-9EE865F382A4! @redhat.com>
	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>
Message-ID: <246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>

On 16 Sep 2014, at 11:56, Pete Muir wrote:

> On 16 Sep 2014, at 00:27, Max Rydahl Andersen 
> <max.andersen at redhat.com> wrote:
>
>> On 9 Sep 2014, at 16:07, Rafael Benevides wrote:
>>
>>> We also need to check that with JBDS, because it's odd that stacks 
>>> only
>>> uses "redhat-techpreview-all-repository" as additional repository.
>>
>> because it was the only thing we needed originally.
>>
>>> Max/Fred,
>>>
>>> Is there any issues having
>>> https://maven.repository.redhat.com/earlyaccess/all/ as declared 
>>> inside
>>> quickstarts pom.xml ?
>>
>> sorry - but I need to grok when earlyaccess/all is even needed  
>> before answering that ? :)
>>
>> My default position would be that if you need earlyaccess you are 
>> expected to be able to understand why you need it.
>>
>> But i'm not sure if that is true anymore - hence wanting to ask 
>> why/when earlyaccess is ever needed ?
>> is it for running quickstarts targeting a beta version of EAP ? 
>> (meaning no snapshots, but actual all releases in it?)
>
> Right, it?s where we put beta and alpha releases.
>
>>
>> If yes, why doesn't /all get split up in /supported and /earlyaccess 
>> and /all will serve the combined result ?
>
> Propose this on the wolf list?

Added as topic on tomorrows wolf call: 
http://pad.engineering.redhat.com/wolf

/max
/max
http://about.me/maxandersen

From benevides at redhat.com  Mon Sep 22 15:59:59 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Mon, 22 Sep 2014 16:59:59 -0300
Subject: [jbossdeveloper] QSTools 1.5.0.CR1 relased
Message-ID: <54207FBF.90305@redhat.com>

These is the first release for the 1.5.x series.

It includes from 1.4.1:

- ArtifactIdNameChecker can now be ignored
- Better log for ignored checkers
- https://issues.jboss.org/browse/JDF-690 - Fix for Maven plugin name 
trademark infringement
- Update from JDF to JBoss Developer Materials


Due to JDF-690, the invocation from qstools has changed from

mvn -U org.jboss.maven.plugins:maven-qstools-plugin:(check|bom-check|etc) to
mvn -U org.jboss.maven.plugins:qstools:(check|bom-check|etc)

It's actually at 
https://repository.jboss.org/nexus/content/groups/public/org/jboss/maven/plugins/qstools/ 
and should be available at Maven Central soon!

-- 

*Rafael Benevides | Senior Software Engineer*
JBoss Developer
M: +55-61-9269-6576

Red Hat

Better technology. Faster innovation. Powered by community collaboration.
See how it works at www.redhat.com <http://www.redhat.com/>

LinkedIn <http://www.linkedin.com/company/3258288> Youtube 
<https://www.youtube.com/redhatlatam>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140922/1d034293/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: {a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140922/1d034293/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linkedin.png
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140922/1d034293/attachment.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: youtube.png
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140922/1d034293/attachment-0001.png 

From sgilda at redhat.com  Mon Sep 22 21:54:02 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 22 Sep 2014 21:54:02 -0400
Subject: [jbossdeveloper] QSTools 1.5.0.CR1 relased
In-Reply-To: <54207FBF.90305@redhat.com>
References: <54207FBF.90305@redhat.com>
Message-ID: <5420D2BA.2090402@redhat.com>

Thanks Rafael!

On 09/22/2014 03:59 PM, Rafael Benevides wrote:
> These is the first release for the 1.5.x series.
>
> It includes from 1.4.1:
>
> - ArtifactIdNameChecker can now be ignored
> - Better log for ignored checkers
> - https://issues.jboss.org/browse/JDF-690 - Fix for Maven plugin name 
> trademark infringement
> - Update from JDF to JBoss Developer Materials
>
>
> Due to JDF-690, the invocation from qstools has changed from
>
> mvn -U 
> org.jboss.maven.plugins:maven-qstools-plugin:(check|bom-check|etc) to
> mvn -U org.jboss.maven.plugins:qstools:(check|bom-check|etc)
>
> It's actually at 
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/maven/plugins/qstools/ 
> and should be available at Maven Central soon!
>
> -- 
>
> *Rafael Benevides | Senior Software Engineer*
> JBoss Developer
> M: +55-61-9269-6576
>
> Red Hat
>
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at www.redhat.com <http://www.redhat.com/>
>
> LinkedIn <http://www.linkedin.com/company/3258288> Youtube 
> <https://www.youtube.com/redhatlatam>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140922/37517c52/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140922/37517c52/attachment-0001.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140922/37517c52/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140922/37517c52/attachment-0003.png 

From paul.robinson at redhat.com  Wed Sep 24 09:14:03 2014
From: paul.robinson at redhat.com (Paul Robinson)
Date: Wed, 24 Sep 2014 14:14:03 +0100
Subject: [jbossdeveloper] Don't do a "rake update"
Message-ID: <6CF2A095-CF61-49D0-884B-3B7C6C9CD849@redhat.com>

All,

There's a problem with aweplug/master ATM. Doing a "rake update" on the www.jboss.org code will pull in the latest master and fail to build.

If you see this error, you'll know you've got this problem:

> An error occurred: undefined local variable or method `site' for Aweplug::Helpers::Resources::Resource:Class

For now you can revert the Gemfile.lock change:

git checkout Gemfile.lock

I'll report bak when it's fixed or if we have a better workaround in place.

Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140924/ae1baff6/attachment.html 

From paul.robinson at redhat.com  Wed Sep 24 10:19:56 2014
From: paul.robinson at redhat.com (Paul Robinson)
Date: Wed, 24 Sep 2014 15:19:56 +0100
Subject: [jbossdeveloper] Common issues building www.jboss.org project
Message-ID: <0DCA62F0-6007-4A7A-A469-B953EBC093E9@redhat.com>

All,

I've added a common issues area to the Readme file: https://github.com/jboss-developer/www.jboss.org/blob/master/README.md. The idea is to document common issues and solutions. You should consult this area when you have an issue, and also consider contributing to it when you find a solution.

I'm not totally sure this is the right place for this type of content, but it will do for now.

Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140924/894a1bf4/attachment.html 

From paul.robinson at redhat.com  Fri Sep 26 05:55:49 2014
From: paul.robinson at redhat.com (Paul Robinson)
Date: Fri, 26 Sep 2014 10:55:49 +0100
Subject: [jbossdeveloper] Don't do a "rake update"
In-Reply-To: <6CF2A095-CF61-49D0-884B-3B7C6C9CD849@redhat.com>
References: <6CF2A095-CF61-49D0-884B-3B7C6C9CD849@redhat.com>
Message-ID: <5B8939B2-1074-4A44-96BB-204450BFAAF5@redhat.com>

This is fixed now, you can go ahead and do a "rake update".

Paul.

On 24 Sep 2014, at 14:14, Paul Robinson <paul.robinson at redhat.com> wrote:

> All,
> 
> There's a problem with aweplug/master ATM. Doing a "rake update" on the www.jboss.org code will pull in the latest master and fail to build.
> 
> If you see this error, you'll know you've got this problem:
> 
>> An error occurred: undefined local variable or method `site' for Aweplug::Helpers::Resources::Resource:Class
> 
> For now you can revert the Gemfile.lock change:
> 
> git checkout Gemfile.lock
> 
> I'll report bak when it's fixed or if we have a better workaround in place.
> 
> Paul.
> 
> -- 
> Paul Robinson
> JBoss Developer Team Lead (www.jboss.org)
> 
> JBoss, a Division of Red Hat
> Registered in England and Wales under Company Registration No. 03798903
> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
> 
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20140926/1feec804/attachment.html