From pmuir at redhat.com  Tue Nov  4 03:11:00 2014
From: pmuir at redhat.com (Pete Muir)
Date: Tue, 4 Nov 2014 09:11:00 +0100
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <54540075.6020403@redhat.com>
References: <54539501.8030609@redhat.com> <54540075.6020403@redhat.com>
Message-ID: <E5654E1B-5A9C-4AAF-A12D-BA5D57F7D403@redhat.com>

I believe the fuse maven repo is still valid, yes.

> On 31 Oct 2014, at 22:34, Rafael Benevides <benevides at redhat.com> wrote:
> 
> Max/Fred
> 
> Can you please review https://mojo.redhat.com/docs/DOC-997344 <https://mojo.redhat.com/docs/DOC-997344> and confirm if those ids are ok. If not, do you mind to place the right information at the document?
> 
> Pete/Max,
> 
> Do you know if Fuse maven repository still valid ?
> 
> 
> Thanks
> 
> On 10/31/14 11:56, Rafael Benevides wrote:
>> Hi all,
>> 
>> I was thinking about the implementation of the repository definition in pom.xml and I want to share my thoughts:
>> 
>> - Create a QSTools CHECKER to mark the lack of <repository /> as a guideline violation if MavenCentralChecker is disabled.
>>    - The violation message will instruct to use the new QSTools GOAL that will be created
>> 
>> - Create another QSTools GOAL to setup the repositories.
>>   - There will be a list of approved repositories and its IDs (redhat techpreview, earlyacess, jboss developer temporary, etc)
>>   - QSTools will remove all previous repositories from pom.xml and prompt which repositories should be added.
>>   - This will help Quickstarts and demos to be easily buildable from development and production branches and will also allow this list to be bulk updated to remove any previous development repository definition.
>> 
>> Please,
>> 
>> If you have any feedback on this, feel free to reply.
>> 
>> -- 
>> 
>> 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> <http://www.linkedin.com/company/3258288> <Mail Attachment.png> <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 <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/20141104/42c08c6f/attachment.html 

From benevides at redhat.com  Tue Nov  4 12:30:43 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 04 Nov 2014 15:30:43 -0200
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <E5654E1B-5A9C-4AAF-A12D-BA5D57F7D403@redhat.com>
References: <54539501.8030609@redhat.com> <54540075.6020403@redhat.com>
	<E5654E1B-5A9C-4AAF-A12D-BA5D57F7D403@redhat.com>
Message-ID: <54590D43.2070301@redhat.com>

One more question:

Do we need to setup < pluginRepositories /> also for quickstarts?

Maybe Paul Gier should know it.


On 11/4/14 06:11, Pete Muir wrote:
> I believe the fuse maven repo is still valid, yes.
>
>> On 31 Oct 2014, at 22:34, Rafael Benevides <benevides at redhat.com 
>> <mailto:benevides at redhat.com>> wrote:
>>
>> Max/Fred
>>
>> Can you please review https://mojo.redhat.com/docs/DOC-997344 and 
>> confirm if those ids are ok. If not, do you mind to place the right 
>> information at the document?
>>
>> Pete/Max,
>>
>> Do you know if Fuse maven repository still valid ?
>>
>>
>> Thanks
>>
>> On 10/31/14 11:56, Rafael Benevides wrote:
>>> Hi all,
>>>
>>> I was thinking about the implementation of the repository definition 
>>> in pom.xml and I want to share my thoughts:
>>>
>>> - Create a QSTools CHECKER to mark the lack of <repository /> as a 
>>> guideline violation if MavenCentralChecker is disabled.
>>>    - The violation message will instruct to use the new QSTools GOAL 
>>> that will be created
>>>
>>> - Create another QSTools GOAL to setup the repositories.
>>>   - There will be a list of approved repositories and its IDs 
>>> (redhat techpreview, earlyacess, jboss developer temporary, etc)
>>>   - QSTools will remove all previous repositories from pom.xml and 
>>> prompt which repositories should be added.
>>>   - This will help Quickstarts and demos to be easily buildable from 
>>> development and production branches and will also allow this list to 
>>> be bulk updated to remove any previous development repository 
>>> definition.
>>>
>>> Please,
>>>
>>> If you have any feedback on this, feel free to reply.
>>>
>>> -- 
>>>
>>> *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> <http://www.linkedin.com/company/3258288> 
>>> <Mail Attachment.png> <https://www.youtube.com/redhatlatam>
>>>
>>>
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> 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
>

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

From mnovotny at redhat.com  Wed Nov  5 03:56:04 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Wed, 05 Nov 2014 09:56:04 +0100
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <54590D43.2070301@redhat.com>
References: <54539501.8030609@redhat.com>
	<54540075.6020403@redhat.com>	<E5654E1B-5A9C-4AAF-A12D-BA5D57F7D403@redhat.com>
	<54590D43.2070301@redhat.com>
Message-ID: <5459E624.9080708@redhat.com>

On 4.11.2014 18:30, Rafael Benevides wrote:
> One more question:
>
> Do we need to setup < pluginRepositories /> also for quickstarts?
>
> Maybe Paul Gier should know it.
It depends if we use and have in Maven repository our own productized
Red Hat maven plugins. If not it is not required.

-- 
Marek Novotny
--
WFK and Seam Product Lead

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

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

From benevides at redhat.com  Wed Nov  5 16:12:48 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Wed, 05 Nov 2014 19:12:48 -0200
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <54539501.8030609@redhat.com>
References: <54539501.8030609@redhat.com>
Message-ID: <545A92D0.7050808@redhat.com>

Hi all,

This email is to inform that QSTools 1.5.0.CR2 was released. ( It's at 
https://repository.jboss.org/nexus/content/groups/public and get synched 
to Maven Central soon)

It includes a new MavenApprovedRepositoriesChecker that will verify if 
the quickstart uses the approved maven repositories (ids and urls).

The list of approved maven repositories is defined inside QSTools config 
file: 
https://github.com/jboss-developer/maven-qstools-plugin/blob/master/config/qstools_config.yaml#L23-L29

To add/remove repositories in quickstarts' pom.xml files a new goal was 
created. You can run: mvn 
org.jboss.maven.plugins:qstools:1.5.0.CR2:repositories

Can you guys try both goals (and checker) for this version before I 
release 1.5.0.Final ?

- mvn org.jboss.maven.plugins:qstools:1.5.0.CR2:check (Verify 
MavenApprovedRepositoriesChecker)
- mvn org.jboss.maven.plugins:qstools:1.5.0.CR2:repositories ( 
add/remove repositories )

Thanks

On 10/31/14 11:56, Rafael Benevides wrote:
> Hi all,
>
> I was thinking about the implementation of the repository definition 
> in pom.xml and I want to share my thoughts:
>
> - Create a QSTools CHECKER to mark the lack of <repository /> as a 
> guideline violation if MavenCentralChecker is disabled.
>    - The violation message will instruct to use the new QSTools GOAL 
> that will be created
>
> - Create another QSTools GOAL to setup the repositories.
>   - There will be a list of approved repositories and its IDs (redhat 
> techpreview, earlyacess, jboss developer temporary, etc)
>   - QSTools will remove all previous repositories from pom.xml and 
> prompt which repositories should be added.
>   - This will help Quickstarts and demos to be easily buildable from 
> development and production branches and will also allow this list to 
> be bulk updated to remove any previous development repository definition.
>
> Please,
>
> If you have any feedback on this, feel free to reply.
>
> -- 
>
> *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/20141105/62e61680/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/20141105/62e61680/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/20141105/62e61680/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/20141105/62e61680/attachment-0001.png 

From mnovotny at redhat.com  Thu Nov  6 04:43:59 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Thu, 06 Nov 2014 10:43:59 +0100
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <545A92D0.7050808@redhat.com>
References: <54539501.8030609@redhat.com> <545A92D0.7050808@redhat.com>
Message-ID: <545B42DF.5030301@redhat.com>


Rafael,

 I tried it n WFK QS and it works great.

although I have some comments to checker - I generated
http://download.eng.brq.redhat.com/scratch/mnovotny/qschecker.html
and it seems there are plenty of the following warnings even it is the
Product GAV
Dependency { ... } doesn't comes from Maven Central Repository

Could you eliminate these as they are pulled from injected repositories
in pom.xml files?

On 5.11.2014 22:12, Rafael Benevides wrote:
> Hi all,
>
> This email is to inform that QSTools 1.5.0.CR2 was released. ( It's at
> https://repository.jboss.org/nexus/content/groups/public and get
> synched to Maven Central soon)
>
> It includes a new MavenApprovedRepositoriesChecker that will verify if
> the quickstart uses the approved maven repositories (ids and urls).
>
> The list of approved maven repositories is defined inside QSTools
> config file:
> https://github.com/jboss-developer/maven-qstools-plugin/blob/master/config/qstools_config.yaml#L23-L29
>
> To add/remove repositories in quickstarts' pom.xml files a new goal
> was created. You can run: mvn
> org.jboss.maven.plugins:qstools:1.5.0.CR2:repositories
>
> Can you guys try both goals (and checker) for this version before I
> release 1.5.0.Final ?
>
> - mvn org.jboss.maven.plugins:qstools:1.5.0.CR2:check (Verify
> MavenApprovedRepositoriesChecker)
> - mvn org.jboss.maven.plugins:qstools:1.5.0.CR2:repositories (
> add/remove repositories )
>
> Thanks
>
> On 10/31/14 11:56, Rafael Benevides wrote:
>> Hi all,
>>
>> I was thinking about the implementation of the repository definition
>> in pom.xml and I want to share my thoughts:
>>
>> - Create a QSTools CHECKER to mark the lack of <repository /> as a
>> guideline violation if MavenCentralChecker is disabled.
>>    - The violation message will instruct to use the new QSTools GOAL
>> that will be created
>>
>> - Create another QSTools GOAL to setup the repositories.
>>   - There will be a list of approved repositories and its IDs (redhat
>> techpreview, earlyacess, jboss developer temporary, etc)
>>   - QSTools will remove all previous repositories from pom.xml and
>> prompt which repositories should be added.
>>   - This will help Quickstarts and demos to be easily buildable from
>> development and production branches and will also allow this list to
>> be bulk updated to remove any previous development repository definition.
>>
>> Please,
>>
>> If you have any feedback on this, feel free to reply.
>>
>> -- 
>>
>> *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
>


-- 
Marek Novotny
--
WFK and Seam Product Lead

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141106/480e0020/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/20141106/480e0020/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/20141106/480e0020/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/20141106/480e0020/attachment-0003.png 

From benevides at redhat.com  Thu Nov  6 06:41:45 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Thu, 06 Nov 2014 09:41:45 -0200
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <545B42DF.5030301@redhat.com>
References: <54539501.8030609@redhat.com> <545A92D0.7050808@redhat.com>
	<545B42DF.5030301@redhat.com>
Message-ID: <545B5E79.5030305@redhat.com>

Hi Marek,

I'm afraid that you didn't use 1.5.0.CR2 version for two reasons:

- *MavenCentralRepositoryChecker* is disabled for all quickstarts: 
https://github.com/jboss-developer/maven-qstools-plugin/blob/master/config/qstools_config.yaml#L89
- I can't see *MavenApprovedRepositoriesChecker* at the list of checkers 
that were used

Would you mind verifying it?

On 11/6/14 07:43, Marek Novotny wrote:
>
> Rafael,
>
>  I tried it n WFK QS and it works great.
>
> although I have some comments to checker - I generated 
> http://download.eng.brq.redhat.com/scratch/mnovotny/qschecker.html
> and it seems there are plenty of the following warnings even it is the 
> Product GAV
> Dependency { ... } doesn't comes from Maven Central Repository
>
> Could you eliminate these as they are pulled from injected 
> repositories in pom.xml files?
>
> On 5.11.2014 22:12, Rafael Benevides wrote:
>> Hi all,
>>
>> This email is to inform that QSTools 1.5.0.CR2 was released. ( It's 
>> at https://repository.jboss.org/nexus/content/groups/public and get 
>> synched to Maven Central soon)
>>
>> It includes a new MavenApprovedRepositoriesChecker that will verify 
>> if the quickstart uses the approved maven repositories (ids and urls).
>>
>> The list of approved maven repositories is defined inside QSTools 
>> config file: 
>> https://github.com/jboss-developer/maven-qstools-plugin/blob/master/config/qstools_config.yaml#L23-L29
>>
>> To add/remove repositories in quickstarts' pom.xml files a new goal 
>> was created. You can run: mvn 
>> org.jboss.maven.plugins:qstools:1.5.0.CR2:repositories
>>
>> Can you guys try both goals (and checker) for this version before I 
>> release 1.5.0.Final ?
>>
>> - mvn org.jboss.maven.plugins:qstools:1.5.0.CR2:check (Verify 
>> MavenApprovedRepositoriesChecker)
>> - mvn org.jboss.maven.plugins:qstools:1.5.0.CR2:repositories ( 
>> add/remove repositories )
>>
>> Thanks
>>
>> On 10/31/14 11:56, Rafael Benevides wrote:
>>> Hi all,
>>>
>>> I was thinking about the implementation of the repository definition 
>>> in pom.xml and I want to share my thoughts:
>>>
>>> - Create a QSTools CHECKER to mark the lack of <repository /> as a 
>>> guideline violation if MavenCentralChecker is disabled.
>>>    - The violation message will instruct to use the new QSTools GOAL 
>>> that will be created
>>>
>>> - Create another QSTools GOAL to setup the repositories.
>>>   - There will be a list of approved repositories and its IDs 
>>> (redhat techpreview, earlyacess, jboss developer temporary, etc)
>>>   - QSTools will remove all previous repositories from pom.xml and 
>>> prompt which repositories should be added.
>>>   - This will help Quickstarts and demos to be easily buildable from 
>>> development and production branches and will also allow this list to 
>>> be bulk updated to remove any previous development repository 
>>> definition.
>>>
>>> Please,
>>>
>>> If you have any feedback on this, feel free to reply.
>>>
>>> -- 
>>>
>>> *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
>>
>
>
> -- 
> Marek Novotny
> --
> WFK and Seam Product Lead
>
> Red Hat Czech s.r.o.
> Purkynova 99
> 612 45 Brno

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141106/97d0144c/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/20141106/97d0144c/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/20141106/97d0144c/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/20141106/97d0144c/attachment-0001.png 

From mnovotny at redhat.com  Thu Nov  6 06:53:21 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Thu, 06 Nov 2014 12:53:21 +0100
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <545B5E79.5030305@redhat.com>
References: <54539501.8030609@redhat.com> <545A92D0.7050808@redhat.com>
	<545B42DF.5030301@redhat.com> <545B5E79.5030305@redhat.com>
Message-ID: <545B6131.7080501@redhat.com>

On 6.11.2014 12:41, Rafael Benevides wrote:
> Hi Marek,
>
> I'm afraid that you didn't use 1.5.0.CR2 version for two reasons:
>
> - *MavenCentralRepositoryChecker* is disabled for all quickstarts:
> https://github.com/jboss-developer/maven-qstools-plugin/blob/master/config/qstools_config.yaml#L89
> - I can't see *MavenApprovedRepositoriesChecker* at the list of
> checkers that were used
>
> Would you mind verifying it?
I think if that wrote the version in maven plugin launching it should be
that version

Just I launched it with my version of config/qstools_config.yaml, so
that could be a reason for reporting that, I will try to rebase your
changes to config/qstools_config.yaml.

INFO]
------------------------------------------------------------------------
[INFO] Building JBoss WFK Quickstart: Parent 2.7.0-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- qstools:1.5.0.CR2:check (default-cli) @
jboss-wfk-quickstarts-parent ---
[INFO] Using the following QSTools config file:
file:/home/mnovotny/projects/git/maven-qstools-plugin/config/qstools_config.yaml
[INFO] Using the following Stacks YML file:
https://raw.github.com/jboss-jdf/jdf-stack/1.0.0.Final/stacks.yaml
[INFO] Parent project loaded from repository: org.jboss:jboss-parent:pom:8
[INFO] Running Checkers: Somes checkers could be ignored for some projects.
[INFO] Running Checker: ArtifactIdNameChecker
[INFO] Running Checker: BomVersionChecker
[INFO] Running Checker: DependencyChecker



-- 
Marek Novotny
--
WFK and Seam Product Lead

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

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

From mnovotny at redhat.com  Thu Nov  6 06:58:05 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Thu, 06 Nov 2014 12:58:05 +0100
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <545B6131.7080501@redhat.com>
References: <54539501.8030609@redhat.com> <545A92D0.7050808@redhat.com>
	<545B42DF.5030301@redhat.com> <545B5E79.5030305@redhat.com>
	<545B6131.7080501@redhat.com>
Message-ID: <545B624D.9040903@redhat.com>

On 6.11.2014 12:53, Marek Novotny wrote:
> On 6.11.2014 12:41, Rafael Benevides wrote:
>> Hi Marek,
>>
>> I'm afraid that you didn't use 1.5.0.CR2 version for two reasons:
>>
>> - *MavenCentralRepositoryChecker* is disabled for all quickstarts:
>> https://github.com/jboss-developer/maven-qstools-plugin/blob/master/config/qstools_config.yaml#L89
>> - I can't see *MavenApprovedRepositoriesChecker* at the list of
>> checkers that were used
>>
>> Would you mind verifying it?
> I think if that wrote the version in maven plugin launching it should
> be that version
>
> Just I launched it with my version of config/qstools_config.yaml, so
> that could be a reason for reporting that, I will try to rebase your
> changes to config/qstools_config.yaml.
So that did the trick, thanks Rafael! You can see the report output at
http://download.eng.brq.redhat.com/scratch/mnovotny/qschecker.html

>
> INFO]
> ------------------------------------------------------------------------
> [INFO] Building JBoss WFK Quickstart: Parent 2.7.0-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- qstools:1.5.0.CR2:check (default-cli) @
> jboss-wfk-quickstarts-parent ---
> [INFO] Using the following QSTools config file:
> file:/home/mnovotny/projects/git/maven-qstools-plugin/config/qstools_config.yaml
> [INFO] Using the following Stacks YML file:
> https://raw.github.com/jboss-jdf/jdf-stack/1.0.0.Final/stacks.yaml
> [INFO] Parent project loaded from repository: org.jboss:jboss-parent:pom:8
> [INFO] Running Checkers: Somes checkers could be ignored for some
> projects.
> [INFO] Running Checker: ArtifactIdNameChecker
> [INFO] Running Checker: BomVersionChecker
> [INFO] Running Checker: DependencyChecker
>
>
>
> -- 
> Marek Novotny
> --
> WFK and Seam Product Lead
>
> Red Hat Czech s.r.o.
> Purkynova 99
> 612 45 Brno


-- 
Marek Novotny
--
WFK and Seam Product Lead

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

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

From benevides at redhat.com  Thu Nov  6 09:32:29 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Thu, 06 Nov 2014 12:32:29 -0200
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <545B624D.9040903@redhat.com>
References: <54539501.8030609@redhat.com> <545A92D0.7050808@redhat.com>
	<545B42DF.5030301@redhat.com> <545B5E79.5030305@redhat.com>
	<545B6131.7080501@redhat.com> <545B624D.9040903@redhat.com>
Message-ID: <545B867D.3060903@redhat.com>

Marek,
Since MavenApprovedRepositoriesChecker is showing zero violations. Does 
that mean that you run Qstools:repositories to add them, right?

Sande/Paul,
Do you have time to test it also?

If is that ok, I'll release 1.5.0.Final soon.

On 11/6/14 09:58, Marek Novotny wrote:
> So that did the trick, thanks Rafael! You can see the report output at 
> http://download.eng.brq.redhat.com/scratch/mnovotny/qschecker.html


From mnovotny at redhat.com  Fri Nov  7 04:33:51 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Fri, 07 Nov 2014 10:33:51 +0100
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <545B867D.3060903@redhat.com>
References: <54539501.8030609@redhat.com> <545A92D0.7050808@redhat.com>
	<545B42DF.5030301@redhat.com> <545B5E79.5030305@redhat.com>
	<545B6131.7080501@redhat.com> <545B624D.9040903@redhat.com>
	<545B867D.3060903@redhat.com>
Message-ID: <545C91FF.6070509@redhat.com>

On 6.11.2014 15:32, Rafael Benevides wrote:
> Marek,
> Since MavenApprovedRepositoriesChecker is showing zero violations.
> Does that mean that you run Qstools:repositories to add them, right?
yes. I did run Qstools:repositories before check.
>
> Sande/Paul,
> Do you have time to test it also?
>
> If is that ok, I'll release 1.5.0.Final soon.
from my POV it is OK
>
> On 11/6/14 09:58, Marek Novotny wrote:
>> So that did the trick, thanks Rafael! You can see the report output
>> at http://download.eng.brq.redhat.com/scratch/mnovotny/qschecker.html
>


-- 
Marek Novotny
--
WFK and Seam Product Lead

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


From sgilda at redhat.com  Fri Nov  7 08:26:00 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 07 Nov 2014 08:26:00 -0500
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <545B867D.3060903@redhat.com>
References: <54539501.8030609@redhat.com> <545A92D0.7050808@redhat.com>
	<545B42DF.5030301@redhat.com> <545B5E79.5030305@redhat.com>
	<545B6131.7080501@redhat.com> <545B624D.9040903@redhat.com>
	<545B867D.3060903@redhat.com>
Message-ID: <545CC868.7070300@redhat.com>


On 11/06/2014 09:32 AM, Rafael Benevides wrote:
> Marek,
> Since MavenApprovedRepositoriesChecker is showing zero violations. 
> Does that mean that you run Qstools:repositories to add them, right?
>
> Sande/Paul,
> Do you have time to test it also?
No, I haven't. I'll try to get to it today.
>
> If is that ok, I'll release 1.5.0.Final soon.
>
> On 11/6/14 09:58, Marek Novotny wrote:
>> So that did the trick, thanks Rafael! You can see the report output 
>> at http://download.eng.brq.redhat.com/scratch/mnovotny/qschecker.html
>


From benevides at redhat.com  Fri Nov  7 08:48:12 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 07 Nov 2014 11:48:12 -0200
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <545CC868.7070300@redhat.com>
References: <54539501.8030609@redhat.com> <545A92D0.7050808@redhat.com>
	<545B42DF.5030301@redhat.com> <545B5E79.5030305@redhat.com>
	<545B6131.7080501@redhat.com> <545B624D.9040903@redhat.com>
	<545B867D.3060903@redhat.com> <545CC868.7070300@redhat.com>
Message-ID: <545CCD9C.1060709@redhat.com>


On 11/7/14 11:26, Sande Gilda wrote:
>
> On 11/06/2014 09:32 AM, Rafael Benevides wrote:
>> Marek,
>> Since MavenApprovedRepositoriesChecker is showing zero violations. 
>> Does that mean that you run Qstools:repositories to add them, right?
>>
>> Sande/Paul,
>> Do you have time to test it also?
> No, I haven't. I'll try to get to it today.
If you could try 1.5.0-SNAPSHOT from master branch it would be awesome 
since I made some improvements after 1.5.0.CR2.

Thanks for your help, Sande.

I think that this feature will be very useful for you, Paul and 
Quickstarts owners.


>>
>> If is that ok, I'll release 1.5.0.Final soon.
>>
>> On 11/6/14 09:58, Marek Novotny wrote:
>>> So that did the trick, thanks Rafael! You can see the report output 
>>> at http://download.eng.brq.redhat.com/scratch/mnovotny/qschecker.html
>>
>


From alexandre.porcelli at gmail.com  Tue Nov 11 09:37:29 2014
From: alexandre.porcelli at gmail.com (Alexandre Porcelli)
Date: Tue, 11 Nov 2014 12:37:29 -0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <5453C21D.5040203@redhat.com>
References: <53FB3100.4020501@redhat.com>
	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>
	<246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>
	<5452ADAB.2060803@redhat.com>
	<4A802246-C724-491F-8A4A-9480142A1B6A@redhat.com>
	<54534CA6.9050303@redhat.com> <54538780.5070509@redhat.com>
	<B20848FF-2F53-4AF6-9C8D-3E8CF25A1D96@redhat.com>
	<1753895673.3004550.1414762450254.JavaMail.zimbra@redhat.com>
	<638CC3E7-0036-4EF4-9C91-9F9F82DD805B@redhat.com>
	<5453BDCB.1060104@redhat.com>
	<0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>
	<5453C21D.5040203@redhat.com>
Message-ID: <CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>

Sorry for my late reply... I was on PTO (in fact I return tomorrow)

First of all... I understand all the reasoning behind the issues that makes
us avoid use maven central for our stuff, I'm also a seasoned developer
with good expirience on maven config - so touch my settings.xml isn't a
problem, or even change myself some POMs wouldn't be a problem too.

So what's the problem? Simplicity (or lack of it)! If Ticketmonster is our
`petclinic`, we should make it easy to build and deploy as spring's
petclinic is... git clone; mvn clean install and done!

Ticketmonster uses a default branch called "2.7.x-develop" (after cloning
and I had to double check if I did anything wrong... I questioned myself if
I cloned the right project; if i had changed branches accidently; and
finally if 2.7.x was really the latest version); then I tried to build, no
pom.xml on the root (fine, it was quick to find the real sources
directory); finally I run the build (tried the innocent `mvn clean
install`) - and got lots of error messages. You can arguee that I didn't
follow the tutorial... and you're right! But how many developers are also
skiping the tutorial and are trying to build the app directly? How many
people we're loosing on this process?

If we want to make our technology accessible to people, we should try to
make it simple as possible... we should try to remove all barriers, and
make our things as easy to consume as others are doing.

btw: I was trying to use ticketmonster to record a demo of our UberFire
based Web IDE: https://www.youtube.com/watch?v=UG4pqk2r70Q

[]s
___________________
Alexandre Porcelli
F: +55 11 98159-9725
http://about.me/porcelli

On Fri, Oct 31, 2014 at 3:08 PM, Rafael Benevides <benevides at redhat.com>
wrote:

> We stopped at which repos should be included.
>
> Them in the other email thread I proposed to have a list of approved repos
> and its id, them QSTools can be used to update those repo definitions.
>
>
> On 10/31/14 15:07, Max Rydahl Andersen wrote:
>
>> Anything holding us back for doing it for quick starts and ticketmonster?
>>
>> I feel we had this discussion in past but I only remember "just not done
>> yet" ...or was there something beyond that ?
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>>  On 31 Oct 2014, at 17:50, Rafael Benevides <benevides at redhat.com> wrote:
>>>
>>> This was only done for the archetypes
>>>
>>>  On 10/31/14 13:44, Max Rydahl Andersen wrote:
>>>> Didn't we do inject of these when Productization built them ?
>>>>
>>>> Or was this only done for the archetypes ?
>>>>
>>>>
>>>>
>>>> /max
>>>> http://about.me/maxandersen
>>>>
>>>>
>>>>  On 31 Oct 2014, at 14:36, Vineet Reynolds Pereira <vpereira at redhat.com>
>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>
>>>>>> From: "Max Rydahl Andersen" <max.andersen at redhat.com>
>>>>>> To: "Rafael Benevides" <benevides at redhat.com>
>>>>>> Cc: jbossdeveloper at lists.jboss.org, "Alexandre Porcelli" <
>>>>>> alexandre.porcelli at gmail.com>, "Tomas Repel"
>>>>>> <trepel at redhat.com>, "Nikoleta Ziakova" <nziakova at redhat.com>
>>>>>> Sent: Friday, October 31, 2014 6:53:43 PM
>>>>>> Subject: Re: [jbossdeveloper] <repository /> on quickstarts pom.xml
>>>>>>
>>>>>>  On 31 Oct 2014, at 13:58, Rafael Benevides wrote:
>>>>>>>
>>>>>>> I know which dependencies were causing the build to fail and where to
>>>>>>> find them, but it seems that Alexandre wanted to show users how to
>>>>>>> run
>>>>>>> a
>>>>>>> project as easy as clone, build and run.
>>>>>>>
>>>>>>> If I'm not wrong, this discussion started with similar issues in this
>>>>>>> Arun Gupta Twitter thread:
>>>>>>> https://twitter.com/arungupta/status/502854638832730112
>>>>>>>
>>>>>> so this is a different question.
>>>>>>
>>>>>> Question is if we should add the techpreview/all to
>>>>>> quickstarts/examples.
>>>>>>
>>>>>> Not about earlyaccess.
>>>>>>
>>>>>> And afaik we already did this for quickstarts with a clear warning,
>>>>>> right ?
>>>>>>
>>>>> AFAIK, they're not in the POM of the quickstarts. A settings.xml is
>>>>> supplied instead:
>>>>> https://github.com/jboss-developer/jboss-wfk-
>>>>> quickstarts/blob/2.6.0.Final/settings.xml
>>>>>
>>>>> But, that would deflect the original question on whether we should add
>>>>> it to POM.
>>>>> Honestly, I dont mind adding it, with the warning that for a
>>>>> real-world project, the repo should instead be in the settings.xml.
>>>>>
>>>>>  Thus if ticketmonster does not have that in there I would say it would
>>>>>> make sense to add it
>>>>>> with similar warning/text as the quickstarts.
>>>>>>
>>>>>> /max
>>>>>>
>>>>>>  As I also told Alexandre that we were having this discussion, I
>>>>>>> invited
>>>>>>> him to give his feedback on this Thread so he can provide more
>>>>>>> details.
>>>>>>>
>>>>>>> Alexandre,
>>>>>>>
>>>>>>> Do you mind to share your restrictions and perceptions about the
>>>>>>> build
>>>>>>> process ?
>>>>>>>
>>>>>>> On 10/31/14 06:47, Marek Novotny wrote:
>>>>>>>
>>>>>>>> What restrictions does he have ?
>>>>>>>>>>
>>>>>>>>>> And I guess the issue here is ticketmonster master needs the
>>>>>>>>>> earlyaccess bits ?
>>>>>>>>>>
>>>>>>>>>> I think ticketmonster master could add the earlyaccess to its pom
>>>>>>>>>> but
>>>>>>>>>> then just make sure once it is releaesed it gets removed which
>>>>>>>>>> should
>>>>>>>>>> be fine since then it should be using any earlyaccess bundles,
>>>>>>>>>> right ?
>>>>>>>>>>
>>>>>>>>> Not really, ticket-monster master branch doesn't exist. The closest
>>>>>>>> to
>>>>>>>> master is 2.6.0.Final -
>>>>>>>> https://github.com/jboss-developer/ticket-monster/tree/2.6.0.Final
>>>>>>>> -
>>>>>>>> which is the tight to WFK 2.6.0.GA and all GAVs should be
>>>>>>>> resolvable
>>>>>>>> fromhttp://maven.repository.redhat.com/techpreview/all/
>>>>>>>>
>>>>>>>> I think that Rafael knows that 2.7.x-develop is unstable and
>>>>>>>> includes
>>>>>>>> internal product GAVs which are not in all or earlyaccess.
>>>>>>>>
>>>>>>>> So if Alexandre uses 2.6.0.Final branch/tag he should get it to work
>>>>>>>> just with online redhat repository
>>>>>>>> http://maven.repository.redhat.com/techpreview/all/. If not please
>>>>>>>> advice him to send errors to Vineet or me.
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> jbossdeveloper mailing list
>>>>>>> jbossdeveloper at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>>>>
>>>>>> /max
>>>>>> http://about.me/maxandersen
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141111/022bd2c9/attachment-0001.html 

From manderse at redhat.com  Thu Nov 13 08:21:05 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 13 Nov 2014 14:21:05 +0100
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <54540075.6020403@redhat.com>
References: <54539501.8030609@redhat.com> <54540075.6020403@redhat.com>
Message-ID: <D443976B-5784-4474-A3E2-2D32BC3989E7@redhat.com>

On 31 Oct 2014, at 22:34, Rafael Benevides wrote:

> Max/Fred
>
> Can you please review https://mojo.redhat.com/docs/DOC-997344 and 
> confirm if those ids are ok. If not, do you mind to place the right 
> information at the document?

sorry for late response.

Looking at this list the only two repositories I consider valid in 
production quickstarts are:

redhat-techpreview-all-repository
http://maven.repository.redhat.com/techpreview/all/

redhat-earlyaccess-all-repository (for things not GA)
https://maven.repository.redhat.com/earlyaccess/all/


These are I'm surprised we are now letting in:

Jboss public repo is not something our productized nor project 
quickstarts should depend on is it ? Was there not a requirement for 
quickstarts
to *not* rely on this repo that is a big mashup of dependencies and 
instead only rely on central published artifacts ?
jboss-public-repository
https://repository.jboss.org/nexus/content/groups/public/

Fuse reposource repo I thought was only being used for old fuse releases 
? If that is no longer the case then that is not great since
it seem to have a lot of redundancy of artifacts.
fuse-public-repository
https://repo.fusesource.com/nexus/content/groups/public

This repo I do not understand what is for and should not be exposed 
anywhere IMO. Only relevant to put in testers own settings.xml is it not 
?
jboss-developer-staging-repository
http://jboss-developer.github.io/temp-maven-repo/

About the ID's correctness/alignment with our tools that is something 
Fred should be able to verify better than I.

/max

> Pete/Max,
>
> Do you know if Fuse maven repository still valid ?
>
>
> Thanks
>
> On 10/31/14 11:56, Rafael Benevides wrote:
>> Hi all,
>>
>> I was thinking about the implementation of the repository definition 
>> in pom.xml and I want to share my thoughts:
>>
>> - Create a QSTools CHECKER to mark the lack of <repository /> as a 
>> guideline violation if MavenCentralChecker is disabled.
>> - The violation message will instruct to use the new QSTools GOAL 
>> that will be created
>>
>> - Create another QSTools GOAL to setup the repositories.
>> - There will be a list of approved repositories and its IDs (redhat 
>> techpreview, earlyacess, jboss developer temporary, etc)
>> - QSTools will remove all previous repositories from pom.xml and 
>> prompt which repositories should be added.
>> - This will help Quickstarts and demos to be easily buildable from 
>> development and production branches and will also allow this list to 
>> be bulk updated to remove any previous development repository 
>> definition.
>>
>> Please,
>>
>> If you have any feedback on this, feel free to reply.
>>
>> -- 
>>
>> *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
>
> _______________________________________________
> 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  Thu Nov 13 08:31:44 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Thu, 13 Nov 2014 11:31:44 -0200
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <D443976B-5784-4474-A3E2-2D32BC3989E7@redhat.com>
References: <54539501.8030609@redhat.com> <54540075.6020403@redhat.com>
	<D443976B-5784-4474-A3E2-2D32BC3989E7@redhat.com>
Message-ID: <5464B2C0.5050104@redhat.com>

Those other repos (jboss-public, fuse-public, jboss-developer-staging) 
exists just to make it easy to add them for development branches. We use 
jboss-developer-staging a lot for staged BOMs.

I also added Fuse repo because 6.1.0 was released using it. Check it: 
https://github.com/jboss-fuse/quickstarts/releases - Should it be removed ?

One of the goals of *QSTools:repositories goal* (1.5.0.CR3) is to make 
it easy to setup repos by making only redhat-techpreview-all-repository  
and redhat-earlyaccess-all-repository available on stable branches.


I'll wait Fred to confirm repo IDs. Thanks


On 11/13/14 11:21, Max Rydahl Andersen wrote:
> On 31 Oct 2014, at 22:34, Rafael Benevides wrote:
>
>> Max/Fred
>>
>> Can you please review https://mojo.redhat.com/docs/DOC-997344 and 
>> confirm if those ids are ok. If not, do you mind to place the right 
>> information at the document?
>
> sorry for late response.
>
> Looking at this list the only two repositories I consider valid in 
> production quickstarts are:
>
> redhat-techpreview-all-repository
> http://maven.repository.redhat.com/techpreview/all/
>
> redhat-earlyaccess-all-repository (for things not GA)
> https://maven.repository.redhat.com/earlyaccess/all/
>
>
> These are I'm surprised we are now letting in:
>
> Jboss public repo is not something our productized nor project 
> quickstarts should depend on is it ? Was there not a requirement for 
> quickstarts
> to *not* rely on this repo that is a big mashup of dependencies and 
> instead only rely on central published artifacts ?
> jboss-public-repository
> https://repository.jboss.org/nexus/content/groups/public/
>
> Fuse reposource repo I thought was only being used for old fuse 
> releases ? If that is no longer the case then that is not great since
> it seem to have a lot of redundancy of artifacts.
> fuse-public-repository
> https://repo.fusesource.com/nexus/content/groups/public
>
> This repo I do not understand what is for and should not be exposed 
> anywhere IMO. Only relevant to put in testers own settings.xml is it 
> not ?
> jboss-developer-staging-repository
> http://jboss-developer.github.io/temp-maven-repo/
>
> About the ID's correctness/alignment with our tools that is something 
> Fred should be able to verify better than I.
>
> /max
>
>> Pete/Max,
>>
>> Do you know if Fuse maven repository still valid ?
>>
>>
>> Thanks
>>
>> On 10/31/14 11:56, Rafael Benevides wrote:
>>> Hi all,
>>>
>>> I was thinking about the implementation of the repository definition 
>>> in pom.xml and I want to share my thoughts:
>>>
>>> - Create a QSTools CHECKER to mark the lack of <repository /> as a 
>>> guideline violation if MavenCentralChecker is disabled.
>>> - The violation message will instruct to use the new QSTools GOAL 
>>> that will be created
>>>
>>> - Create another QSTools GOAL to setup the repositories.
>>> - There will be a list of approved repositories and its IDs (redhat 
>>> techpreview, earlyacess, jboss developer temporary, etc)
>>> - QSTools will remove all previous repositories from pom.xml and 
>>> prompt which repositories should be added.
>>> - This will help Quickstarts and demos to be easily buildable from 
>>> development and production branches and will also allow this list to 
>>> be bulk updated to remove any previous development repository 
>>> definition.
>>>
>>> Please,
>>>
>>> If you have any feedback on this, feel free to reply.
>>>
>>> -- 
>>>
>>> *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
>>
>> _______________________________________________
>> 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/20141113/93c247d6/attachment.html 

From fbricon at redhat.com  Thu Nov 13 10:33:33 2014
From: fbricon at redhat.com (Fred Bricon)
Date: Thu, 13 Nov 2014 10:33:33 -0500
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <D443976B-5784-4474-A3E2-2D32BC3989E7@redhat.com>
References: <54539501.8030609@redhat.com> <54540075.6020403@redhat.com>
	<D443976B-5784-4474-A3E2-2D32BC3989E7@redhat.com>
Message-ID: <1B582AEC-015A-44AA-8E4F-B2B0C116294E@redhat.com>

>From a JBT/JBDS standpoint, only redhat-techpreview-all-repository is used/recognized.

So if you decide to use other repo ids, we should be fine, but this need to be documented in a central place, so that everyone stays on the same page.

Fred

> Le 13 nov. 2014 ? 08:21, Max Rydahl Andersen <manderse at redhat.com> a ?crit :
> 
> On 31 Oct 2014, at 22:34, Rafael Benevides wrote:
> 
>> Max/Fred
>> 
>> Can you please review https://mojo.redhat.com/docs/DOC-997344 and 
>> confirm if those ids are ok. If not, do you mind to place the right 
>> information at the document?
> 
> sorry for late response.
> 
> Looking at this list the only two repositories I consider valid in 
> production quickstarts are:
> 
> redhat-techpreview-all-repository
> http://maven.repository.redhat.com/techpreview/all/
> 
> redhat-earlyaccess-all-repository (for things not GA)
> https://maven.repository.redhat.com/earlyaccess/all/
> 
> 
> These are I'm surprised we are now letting in:
> 
> Jboss public repo is not something our productized nor project 
> quickstarts should depend on is it ? Was there not a requirement for 
> quickstarts
> to *not* rely on this repo that is a big mashup of dependencies and 
> instead only rely on central published artifacts ?
> jboss-public-repository
> https://repository.jboss.org/nexus/content/groups/public/
> 
> Fuse reposource repo I thought was only being used for old fuse releases 
> ? If that is no longer the case then that is not great since
> it seem to have a lot of redundancy of artifacts.
> fuse-public-repository
> https://repo.fusesource.com/nexus/content/groups/public
> 
> This repo I do not understand what is for and should not be exposed 
> anywhere IMO. Only relevant to put in testers own settings.xml is it not 
> ?
> jboss-developer-staging-repository
> http://jboss-developer.github.io/temp-maven-repo/
> 
> About the ID's correctness/alignment with our tools that is something 
> Fred should be able to verify better than I.
> 
> /max
> 
>> Pete/Max,
>> 
>> Do you know if Fuse maven repository still valid ?
>> 
>> 
>> Thanks
>> 
>> On 10/31/14 11:56, Rafael Benevides wrote:
>>> Hi all,
>>> 
>>> I was thinking about the implementation of the repository definition 
>>> in pom.xml and I want to share my thoughts:
>>> 
>>> - Create a QSTools CHECKER to mark the lack of <repository /> as a 
>>> guideline violation if MavenCentralChecker is disabled.
>>> - The violation message will instruct to use the new QSTools GOAL 
>>> that will be created
>>> 
>>> - Create another QSTools GOAL to setup the repositories.
>>> - There will be a list of approved repositories and its IDs (redhat 
>>> techpreview, earlyacess, jboss developer temporary, etc)
>>> - QSTools will remove all previous repositories from pom.xml and 
>>> prompt which repositories should be added.
>>> - This will help Quickstarts and demos to be easily buildable from 
>>> development and production branches and will also allow this list to 
>>> be bulk updated to remove any previous development repository 
>>> definition.
>>> 
>>> Please,
>>> 
>>> If you have any feedback on this, feel free to reply.
>>> 
>>> -- 
>>> 
>>> *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
>> 
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
> 
> 
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper



From pmuir at redhat.com  Thu Nov 13 10:19:58 2014
From: pmuir at redhat.com (Pete Muir)
Date: Thu, 13 Nov 2014 15:19:58 +0000
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <D443976B-5784-4474-A3E2-2D32BC3989E7@redhat.com>
References: <54539501.8030609@redhat.com> <54540075.6020403@redhat.com>
	<D443976B-5784-4474-A3E2-2D32BC3989E7@redhat.com>
Message-ID: <DCA297DB-8746-40F7-94D9-290D02F50B1B@redhat.com>


> On 13 Nov 2014, at 13:21, Max Rydahl Andersen <manderse at redhat.com> wrote:
> 
> On 31 Oct 2014, at 22:34, Rafael Benevides wrote:
> 
>> Max/Fred
>> 
>> Can you please review https://mojo.redhat.com/docs/DOC-997344 <https://mojo.redhat.com/docs/DOC-997344> and confirm if those ids are ok. If not, do you mind to place the right information at the document?
> 
> sorry for late response.
> 
> Looking at this list the only two repositories I consider valid in production quickstarts

production quickstarts aren?t actually a thing :-p

> are:
> 
> redhat-techpreview-all-repository
> http://maven.repository.redhat.com/techpreview/all/ <http://maven.repository.redhat.com/techpreview/all/>
> 
> redhat-earlyaccess-all-repository (for things not GA)
> https://maven.repository.redhat.com/earlyaccess/all/ <https://maven.repository.redhat.com/earlyaccess/all/>

These ^^^, plus fusesource, are valid for non-earlyaccess quickstarts

> 
> 
> These are I'm surprised we are now letting in:
> 
> Jboss public repo is not something our productized nor project quickstarts should depend on is it ? Was there not a requirement for quickstarts
> to *not* rely on this repo that is a big mashup of dependencies and instead only rely on central published artifacts ?
> jboss-public-repository
> https://repository.jboss.org/nexus/content/groups/public/ <https://repository.jboss.org/nexus/content/groups/public/>

This ^^^ is valid only for earlyaccess quickstarts

> 
> Fuse reposource repo I thought was only being used for old fuse releases ? If that is no longer the case then that is not great since
> it seem to have a lot of redundancy of artifacts.
> fuse-public-repository
> https://repo.fusesource.com/nexus/content/groups/public <https://repo.fusesource.com/nexus/content/groups/public>

It?s still used for Fuse releases AFAIK.

> 
> This repo I do not understand what is for and should not be exposed anywhere IMO. Only relevant to put in testers own settings.xml is it not ?
> jboss-developer-staging-repository
> http://jboss-developer.github.io/temp-maven-repo/ <http://jboss-developer.github.io/temp-maven-repo/>

Agreed, this one should never appear in a POM.

> 
> About the ID's correctness/alignment with our tools that is something Fred should be able to verify better than I.
> 
> /max
> 
>> Pete/Max,
>> 
>> Do you know if Fuse maven repository still valid ?
>> 
>> 
>> Thanks
>> 
>> On 10/31/14 11:56, Rafael Benevides wrote:
>>> Hi all,
>>> 
>>> I was thinking about the implementation of the repository definition in pom.xml and I want to share my thoughts:
>>> 
>>> - Create a QSTools CHECKER to mark the lack of <repository /> as a guideline violation if MavenCentralChecker is disabled.
>>> - The violation message will instruct to use the new QSTools GOAL that will be created
>>> 
>>> - Create another QSTools GOAL to setup the repositories.
>>> - There will be a list of approved repositories and its IDs (redhat techpreview, earlyacess, jboss developer temporary, etc)
>>> - QSTools will remove all previous repositories from pom.xml and prompt which repositories should be added.
>>> - This will help Quickstarts and demos to be easily buildable from development and production branches and will also allow this list to be bulk updated to remove any previous development repository definition.
>>> 
>>> Please,
>>> 
>>> If you have any feedback on this, feel free to reply.
>>> 
>>> -- 
>>> 
>>> *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/> <http://www.redhat.com/ <http://www.redhat.com/>>
>>> 
>>> LinkedIn <http://www.linkedin.com/company/3258288 <http://www.linkedin.com/company/3258288>> Youtube <https://www.youtube.com/redhatlatam <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 <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 <https://lists.jboss.org/mailman/listinfo/jbossdeveloper>
> 
> 
> /max
> http://about.me/maxandersen <http://about.me/maxandersen>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141113/1aaa1a9b/attachment-0001.html 

From manderse at redhat.com  Fri Nov 14 05:51:25 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 14 Nov 2014 11:51:25 +0100
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <DCA297DB-8746-40F7-94D9-290D02F50B1B@redhat.com>
References: <54539501.8030609@redhat.com> <54540075.6020403@redhat.com>
	<D443976B-5784-4474-A3E2-2D32BC3989E7@redhat.com>
	<DCA297DB-8746-40F7-94D9-290D02F50B1B@redhat.com>
Message-ID: <5562D685-7586-4765-9094-1D1397B72D63@redhat.com>

>>>
>>> Can you please review https://mojo.redhat.com/docs/DOC-997344 
>>> <https://mojo.redhat.com/docs/DOC-997344> and confirm if those ids 
>>> are ok. If not, do you mind to place the right information at the 
>>> document?
>>
>> sorry for late response.
>>
>> Looking at this list the only two repositories I consider valid in 
>> production quickstarts
>
> production quickstarts aren?t actually a thing :-p

What word do we use for it then ? it's not community quickstarts since 
they depend on productized bits.

>> are:
>>
>> redhat-techpreview-all-repository
>> http://maven.repository.redhat.com/techpreview/all/ 
>> <http://maven.repository.redhat.com/techpreview/all/>
>>
>> redhat-earlyaccess-all-repository (for things not GA)
>> https://maven.repository.redhat.com/earlyaccess/all/ 
>> <https://maven.repository.redhat.com/earlyaccess/all/>
>
> These ^^^, plus fusesource, are valid for non-earlyaccess quickstarts

So the earlyaccess repo is valid for non-earlyaccess quickstarts ? seems 
counterintuitive ?

>> These are I'm surprised we are now letting in:
>>
>> Jboss public repo is not something our productized nor project 
>> quickstarts should depend on is it ? Was there not a requirement for 
>> quickstarts
>> to *not* rely on this repo that is a big mashup of dependencies and 
>> instead only rely on central published artifacts ?
>> jboss-public-repository
>> https://repository.jboss.org/nexus/content/groups/public/ 
>> <https://repository.jboss.org/nexus/content/groups/public/>
>
> This ^^^ is valid only for earlyaccess quickstarts

...so earlyaccess quickstarts is even earlier than what is in 
earlyaccess maven repo  ?

Just trying to do the mapping since this is what we call community 
quickstarts on jboss tools end and we keep it clearly separate from 
production related stuff
to avoid/reduce confusion.

>> Fuse reposource repo I thought was only being used for old fuse 
>> releases ? If that is no longer the case then that is not great since
>> it seem to have a lot of redundancy of artifacts.
>> fuse-public-repository
>> https://repo.fusesource.com/nexus/content/groups/public 
>> <https://repo.fusesource.com/nexus/content/groups/public>
>
> It?s still used for Fuse releases AFAIK.

mkay '/ - i'll try reach Aileen and here what is the plan for it and 
what is stopping them from getting into maven.repository.redhat.com.

>> This repo I do not understand what is for and should not be exposed 
>> anywhere IMO. Only relevant to put in testers own settings.xml is it 
>> not ?
>> jboss-developer-staging-repository
>> http://jboss-developer.github.io/temp-maven-repo/ 
>> <http://jboss-developer.github.io/temp-maven-repo/>
>
> Agreed, this one should never appear in a POM.

+1

/max

>
>>
>> About the ID's correctness/alignment with our tools that is something 
>> Fred should be able to verify better than I.
>>
>> /max
>>
>>> Pete/Max,
>>>
>>> Do you know if Fuse maven repository still valid ?
>>>
>>>
>>> Thanks
>>>
>>> On 10/31/14 11:56, Rafael Benevides wrote:
>>>> Hi all,
>>>>
>>>> I was thinking about the implementation of the repository 
>>>> definition in pom.xml and I want to share my thoughts:
>>>>
>>>> - Create a QSTools CHECKER to mark the lack of <repository /> as a 
>>>> guideline violation if MavenCentralChecker is disabled.
>>>> - The violation message will instruct to use the new QSTools GOAL 
>>>> that will be created
>>>>
>>>> - Create another QSTools GOAL to setup the repositories.
>>>> - There will be a list of approved repositories and its IDs (redhat 
>>>> techpreview, earlyacess, jboss developer temporary, etc)
>>>> - QSTools will remove all previous repositories from pom.xml and 
>>>> prompt which repositories should be added.
>>>> - This will help Quickstarts and demos to be easily buildable from 
>>>> development and production branches and will also allow this list 
>>>> to be bulk updated to remove any previous development repository 
>>>> definition.
>>>>
>>>> Please,
>>>>
>>>> If you have any feedback on this, feel free to reply.
>>>>
>>>> -- 
>>>>
>>>> *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/> 
>>>> <http://www.redhat.com/ <http://www.redhat.com/>>
>>>>
>>>> LinkedIn <http://www.linkedin.com/company/3258288 
>>>> <http://www.linkedin.com/company/3258288>> Youtube 
>>>> <https://www.youtube.com/redhatlatam 
>>>> <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 
>>>> <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 
>>> <https://lists.jboss.org/mailman/listinfo/jbossdeveloper>
>>
>>
>> /max
>> http://about.me/maxandersen <http://about.me/maxandersen>


/max
http://about.me/maxandersen

From benevides at redhat.com  Fri Nov 14 07:20:10 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 14 Nov 2014 10:20:10 -0200
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
 Quickstarts and Demos
In-Reply-To: <5562D685-7586-4765-9094-1D1397B72D63@redhat.com>
References: <54539501.8030609@redhat.com> <54540075.6020403@redhat.com>
	<D443976B-5784-4474-A3E2-2D32BC3989E7@redhat.com>
	<DCA297DB-8746-40F7-94D9-290D02F50B1B@redhat.com>
	<5562D685-7586-4765-9094-1D1397B72D63@redhat.com>
Message-ID: <5465F37A.1080405@redhat.com>

If I'm not wrong, We are trying to make it easy (by avoiding 
settings.xml file updates) to everyone from _final __users_ to 
_contributors_ or even for _developers_ or _tools_ who want to try it 
with a mvn clean compile just as happened with Arun, Porcelli, etc

For unreleased Quickstarts, the "stable" branch will need the 
settings.xml file update anyway because we use internal engineer 
repositories.  For "-develop" branch, If we don't have the 
jboss-developer-staging repo added to quickstarts, I feel that we will 
only achieve our goal partially (final users that uses G.A quickstarts).

Experienced developers who will try our Quickstarts for the first time 
and go directly to github, will need to read the documentation or query 
someone to figure out that they should add jboss-developer-staging repo 
to do a single mvn compile.

I think that there's no issue if we add jboss-developer-staging repo on 
a "-develop" branch as long as we keep only the right repos for "stable" 
branch. That's why QSTools:repositories goal was created for - This goal 
is capable of add/remove repos easily.
On 11/14/14 08:51, Max Rydahl Andersen wrote:
>>> This repo I do not understand what is for and should not be exposed 
>>> anywhere IMO. Only relevant to put in testers own settings.xml is it 
>>> not ?
>>> jboss-developer-staging-repository
>>> http://jboss-developer.github.io/temp-maven-repo/ 
>>> <http://jboss-developer.github.io/temp-maven-repo/>
>>
>> Agreed, this one should never appear in a POM.
>
> +1
>
> /max 

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

From pmuir at redhat.com  Fri Nov 14 07:38:04 2014
From: pmuir at redhat.com (Pete Muir)
Date: Fri, 14 Nov 2014 12:38:04 +0000
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <5562D685-7586-4765-9094-1D1397B72D63@redhat.com>
References: <54539501.8030609@redhat.com> <54540075.6020403@redhat.com>
	<D443976B-5784-4474-A3E2-2D32BC3989E7@redhat.com>
	<DCA297DB-8746-40F7-94D9-290D02F50B1B@redhat.com>
	<5562D685-7586-4765-9094-1D1397B72D63@redhat.com>
Message-ID: <F6D7FD17-4898-4047-8971-0AE026A6AA81@redhat.com>


> On 14 Nov 2014, at 10:51, Max Rydahl Andersen <manderse at redhat.com> wrote:
> 
>>>> 
>>>> Can you please review https://mojo.redhat.com/docs/DOC-997344 <https://mojo.redhat.com/docs/DOC-997344> and confirm if those ids are ok. If not, do you mind to place the right information at the document?
>>> 
>>> sorry for late response.
>>> 
>>> Looking at this list the only two repositories I consider valid in production quickstarts
>> 
>> production quickstarts aren?t actually a thing :-p
> 
> What word do we use for it then ? it's not community quickstarts since they depend on productized bits.

Product quickstarts.

> 
>>> are:
>>> 
>>> redhat-techpreview-all-repository
>>> http://maven.repository.redhat.com/techpreview/all/ <http://maven.repository.redhat.com/techpreview/all/>
>>> 
>>> redhat-earlyaccess-all-repository (for things not GA)
>>> https://maven.repository.redhat.com/earlyaccess/all/ <https://maven.repository.redhat.com/earlyaccess/all/>
>> 
>> These ^^^, plus fusesource, are valid for non-earlyaccess quickstarts
> 
> So the earlyaccess repo is valid for non-earlyaccess quickstarts ? seems counterintuitive ?

Yes. A quickstart may be in beta, or a product may be in beta. These things are orthogonal.

> 
>>> These are I'm surprised we are now letting in:
>>> 
>>> Jboss public repo is not something our productized nor project quickstarts should depend on is it ? Was there not a requirement for quickstarts
>>> to *not* rely on this repo that is a big mashup of dependencies and instead only rely on central published artifacts ?
>>> jboss-public-repository
>>> https://repository.jboss.org/nexus/content/groups/public/ <https://repository.jboss.org/nexus/content/groups/public/>
>> 
>> This ^^^ is valid only for earlyaccess quickstarts
> 
> ...so earlyaccess quickstarts is even earlier than what is in earlyaccess maven repo  ?
> 
> Just trying to do the mapping since this is what we call community quickstarts on jboss tools end and we keep it clearly separate from production related stuff
> to avoid/reduce confusion.

Correct. It?s much closer to what you call early access in JBDS - features that aren?t ready to go in to the product yet.

> 
>>> Fuse reposource repo I thought was only being used for old fuse releases ? If that is no longer the case then that is not great since
>>> it seem to have a lot of redundancy of artifacts.
>>> fuse-public-repository
>>> https://repo.fusesource.com/nexus/content/groups/public <https://repo.fusesource.com/nexus/content/groups/public>
>> 
>> It?s still used for Fuse releases AFAIK.
> 
> mkay '/ - i'll try reach Aileen and here what is the plan for it and what is stopping them from getting into maven.repository.redhat.com.
> 
>>> This repo I do not understand what is for and should not be exposed anywhere IMO. Only relevant to put in testers own settings.xml is it not ?
>>> jboss-developer-staging-repository
>>> http://jboss-developer.github.io/temp-maven-repo/ <http://jboss-developer.github.io/temp-maven-repo/>
>> 
>> Agreed, this one should never appear in a POM.
> 
> +1
> 
> /max
> 
>> 
>>> 
>>> About the ID's correctness/alignment with our tools that is something Fred should be able to verify better than I.
>>> 
>>> /max
>>> 
>>>> Pete/Max,
>>>> 
>>>> Do you know if Fuse maven repository still valid ?
>>>> 
>>>> 
>>>> Thanks
>>>> 
>>>> On 10/31/14 11:56, Rafael Benevides wrote:
>>>>> Hi all,
>>>>> 
>>>>> I was thinking about the implementation of the repository definition in pom.xml and I want to share my thoughts:
>>>>> 
>>>>> - Create a QSTools CHECKER to mark the lack of <repository /> as a guideline violation if MavenCentralChecker is disabled.
>>>>> - The violation message will instruct to use the new QSTools GOAL that will be created
>>>>> 
>>>>> - Create another QSTools GOAL to setup the repositories.
>>>>> - There will be a list of approved repositories and its IDs (redhat techpreview, earlyacess, jboss developer temporary, etc)
>>>>> - QSTools will remove all previous repositories from pom.xml and prompt which repositories should be added.
>>>>> - This will help Quickstarts and demos to be easily buildable from development and production branches and will also allow this list to be bulk updated to remove any previous development repository definition.
>>>>> 
>>>>> Please,
>>>>> 
>>>>> If you have any feedback on this, feel free to reply.
>>>>> 
>>>>> -- 
>>>>> 
>>>>> *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/> <http://www.redhat.com/ <http://www.redhat.com/>>
>>>>> 
>>>>> LinkedIn <http://www.linkedin.com/company/3258288 <http://www.linkedin.com/company/3258288>> Youtube <https://www.youtube.com/redhatlatam <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 <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 <https://lists.jboss.org/mailman/listinfo/jbossdeveloper>
>>> 
>>> 
>>> /max
>>> http://about.me/maxandersen <http://about.me/maxandersen>
> 
> 
> /max
> http://about.me/maxandersen



From pmuir at redhat.com  Mon Nov 17 06:00:57 2014
From: pmuir at redhat.com (Pete Muir)
Date: Mon, 17 Nov 2014 11:00:57 +0000
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>
References: <53FB3100.4020501@redhat.com>
	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>
	<246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>
	<5452ADAB.2060803@redhat.com>
	<4A802246-C724-491F-8A4A-9480142A1B6A@redhat.com>
	<54534CA6.9050303@redhat.com> <54538780.5070509@redhat.com>
	<B20848FF-2F53-4AF6-9C8D-3E8CF25A1D96@redhat.com>
	<1753895673.3004550.1414762450254.JavaMail.zimbra@redhat.com>
	<638CC3E7-0036-4EF4-9C91-9F9F82DD805B@redhat.com>
	<5453BDCB.1060104@redhat.com>
	<0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>
	<5453C21D.5040203@redhat.com>
	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>
Message-ID: <B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>

Agreed, and it was this logic that led to us deciding to introduce the repo into the POM.

> On 11 Nov 2014, at 14:37, Alexandre Porcelli <alexandre.porcelli at gmail.com> wrote:
> 
> Sorry for my late reply... I was on PTO (in fact I return tomorrow)
> 
> First of all... I understand all the reasoning behind the issues that makes us avoid use maven central for our stuff, I'm also a seasoned developer with good expirience on maven config - so touch my settings.xml isn't a problem, or even change myself some POMs wouldn't be a problem too.
> 
> So what's the problem? Simplicity (or lack of it)! If Ticketmonster is our `petclinic`, we should make it easy to build and deploy as spring's petclinic is... git clone; mvn clean install and done!
> 
> Ticketmonster uses a default branch called "2.7.x-develop" (after cloning and I had to double check if I did anything wrong... I questioned myself if I cloned the right project; if i had changed branches accidently; and finally if 2.7.x was really the latest version); then I tried to build, no pom.xml on the root (fine, it was quick to find the real sources directory); finally I run the build (tried the innocent `mvn clean install`) - and got lots of error messages. You can arguee that I didn't follow the tutorial... and you're right! But how many developers are also skiping the tutorial and are trying to build the app directly? How many people we're loosing on this process?
> 
> If we want to make our technology accessible to people, we should try to make it simple as possible... we should try to remove all barriers, and make our things as easy to consume as others are doing.
> 
> btw: I was trying to use ticketmonster to record a demo of our UberFire based Web IDE: https://www.youtube.com/watch?v=UG4pqk2r70Q <https://www.youtube.com/watch?v=UG4pqk2r70Q>
> 
> []s
> ___________________
> Alexandre Porcelli
> F: +55 11 98159-9725
> http://about.me/porcelli <http://about.me/porcelli>
> 
> On Fri, Oct 31, 2014 at 3:08 PM, Rafael Benevides <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
> We stopped at which repos should be included.
> 
> Them in the other email thread I proposed to have a list of approved repos and its id, them QSTools can be used to update those repo definitions.
> 
> 
> On 10/31/14 15:07, Max Rydahl Andersen wrote:
> Anything holding us back for doing it for quick starts and ticketmonster?
> 
> I feel we had this discussion in past but I only remember "just not done yet" ...or was there something beyond that ?
> 
> /max
> http://about.me/maxandersen <http://about.me/maxandersen>
> 
> 
> On 31 Oct 2014, at 17:50, Rafael Benevides <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
> 
> This was only done for the archetypes
> 
> On 10/31/14 13:44, Max Rydahl Andersen wrote:
> Didn't we do inject of these when Productization built them ?
> 
> Or was this only done for the archetypes ?
> 
> 
> 
> /max
> http://about.me/maxandersen <http://about.me/maxandersen>
> 
> 
> On 31 Oct 2014, at 14:36, Vineet Reynolds Pereira <vpereira at redhat.com <mailto:vpereira at redhat.com>> wrote:
> 
> 
> 
> ----- Original Message -----
> From: "Max Rydahl Andersen" <max.andersen at redhat.com <mailto:max.andersen at redhat.com>>
> To: "Rafael Benevides" <benevides at redhat.com <mailto:benevides at redhat.com>>
> Cc: jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>, "Alexandre Porcelli" <alexandre.porcelli at gmail.com <mailto:alexandre.porcelli at gmail.com>>, "Tomas Repel"
> <trepel at redhat.com <mailto:trepel at redhat.com>>, "Nikoleta Ziakova" <nziakova at redhat.com <mailto:nziakova at redhat.com>>
> Sent: Friday, October 31, 2014 6:53:43 PM
> Subject: Re: [jbossdeveloper] <repository /> on quickstarts pom.xml
> 
> On 31 Oct 2014, at 13:58, Rafael Benevides wrote:
> 
> I know which dependencies were causing the build to fail and where to
> find them, but it seems that Alexandre wanted to show users how to run
> a
> project as easy as clone, build and run.
> 
> If I'm not wrong, this discussion started with similar issues in this
> Arun Gupta Twitter thread:
> https://twitter.com/arungupta/status/502854638832730112 <https://twitter.com/arungupta/status/502854638832730112>
> so this is a different question.
> 
> Question is if we should add the techpreview/all to
> quickstarts/examples.
> 
> Not about earlyaccess.
> 
> And afaik we already did this for quickstarts with a clear warning,
> right ?
> AFAIK, they're not in the POM of the quickstarts. A settings.xml is supplied instead:
> https://github.com/jboss-developer/jboss-wfk-quickstarts/blob/2.6.0.Final/settings.xml <https://github.com/jboss-developer/jboss-wfk-quickstarts/blob/2.6.0.Final/settings.xml>
> 
> But, that would deflect the original question on whether we should add it to POM.
> Honestly, I dont mind adding it, with the warning that for a real-world project, the repo should instead be in the settings.xml.
> 
> Thus if ticketmonster does not have that in there I would say it would
> make sense to add it
> with similar warning/text as the quickstarts.
> 
> /max
> 
> As I also told Alexandre that we were having this discussion, I
> invited
> him to give his feedback on this Thread so he can provide more
> details.
> 
> Alexandre,
> 
> Do you mind to share your restrictions and perceptions about the build
> process ?
> 
> On 10/31/14 06:47, Marek Novotny wrote:
> What restrictions does he have ?
> 
> And I guess the issue here is ticketmonster master needs the
> earlyaccess bits ?
> 
> I think ticketmonster master could add the earlyaccess to its pom
> but
> then just make sure once it is releaesed it gets removed which
> should
> be fine since then it should be using any earlyaccess bundles,
> right ?
> Not really, ticket-monster master branch doesn't exist. The closest
> to
> master is 2.6.0.Final -
> https://github.com/jboss-developer/ticket-monster/tree/2.6.0.Final <https://github.com/jboss-developer/ticket-monster/tree/2.6.0.Final>  -
> which is the tight to WFK 2.6.0.GA <http://2.6.0.ga/> and all GAVs should be resolvable
> fromhttp://maven.repository.redhat.com/techpreview/all/ <http://maven.repository.redhat.com/techpreview/all/>
> 
> I think that Rafael knows that 2.7.x-develop is unstable and includes
> internal product GAVs which are not in all or earlyaccess.
> 
> So if Alexandre uses 2.6.0.Final branch/tag he should get it to work
> just with online redhat repository
> http://maven.repository.redhat.com/techpreview/all/ <http://maven.repository.redhat.com/techpreview/all/>. If not please
> advice him to send errors to Vineet or me.
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper <https://lists.jboss.org/mailman/listinfo/jbossdeveloper>
> /max
> http://about.me/maxandersen <http://about.me/maxandersen>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper <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 <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 <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/20141117/13c2e372/attachment-0001.html 

From paul.robinson at redhat.com  Wed Nov 19 13:23:00 2014
From: paul.robinson at redhat.com (Paul Robinson)
Date: Wed, 19 Nov 2014 18:23:00 +0000
Subject: [jbossdeveloper] Patchy availability Thurs and Fri
Message-ID: <9593B141-E0D1-472B-A93C-FCC8138BAF24@redhat.com>

All,

My availability will be patchy on Thursday and Friday. We are moving offices, plus I have some teaching and personal matters to attend to.

I?ll keep an eye on email, but response times could be higher.

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/20141119/bcb33378/attachment.html 

From sgilda at redhat.com  Mon Nov 24 15:15:01 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 24 Nov 2014 15:15:01 -0500
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>
References: <53FB3100.4020501@redhat.com>	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>	<246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>	<5452ADAB.2060803@redhat.com>	<4A802246-C724-491F-8A4A-9480142A1B6A@redhat.com>	<54534CA6.9050303@redhat.com>
	<54538780.5070509@redhat.com>	<B20848FF-2F53-4AF6-9C8D-3E8CF25A1D96@redhat.com>	<1753895673.3004550.1414762450254.JavaMail.zimbra@redhat.com>	<638CC3E7-0036-4EF4-9C91-9F9F82DD805B@redhat.com>	<5453BDCB.1060104@redhat.com>	<0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>	<5453C21D.5040203@redhat.com>	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>
	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>
Message-ID: <547391C5.60106@redhat.com>

What is the timeline for this? Am I supposed to do this for the JBoss 
EAP 6.4 quickstarts or for the EAP 7 release? I think it will have a 
pretty big QE impact. Plus, this change not only impacts the 
quickstarts, but the documentation.

On 11/17/2014 06:00 AM, Pete Muir wrote:
> Agreed, and it was this logic that led to us deciding to introduce the 
> repo into the POM.
>
>> On 11 Nov 2014, at 14:37, Alexandre Porcelli 
>> <alexandre.porcelli at gmail.com <mailto:alexandre.porcelli at gmail.com>> 
>> wrote:
>>
>> Sorry for my late reply... I was on PTO (in fact I return tomorrow)
>>
>> First of all... I understand all the reasoning behind the issues that 
>> makes us avoid use maven central for our stuff, I'm also a seasoned 
>> developer with good expirience on maven config - so touch my 
>> settings.xml isn't a problem, or even change myself some POMs 
>> wouldn't be a problem too.
>>
>> So what's the problem? Simplicity (or lack of it)! If Ticketmonster 
>> is our `petclinic`, we should make it easy to build and deploy as 
>> spring's petclinic is... git clone; mvn clean install and done!
>>
>> Ticketmonster uses a default branch called "2.7.x-develop" (after 
>> cloning and I had to double check if I did anything wrong... I 
>> questioned myself if I cloned the right project; if i had changed 
>> branches accidently; and finally if 2.7.x was really the latest 
>> version); then I tried to build, no pom.xml on the root (fine, it was 
>> quick to find the real sources directory); finally I run the build 
>> (tried the innocent `mvn clean install`) - and got lots of error 
>> messages. You can arguee that I didn't follow the tutorial... and 
>> you're right! But how many developers are also skiping the tutorial 
>> and are trying to build the app directly? How many people we're 
>> loosing on this process?
>>
>> If we want to make our technology accessible to people, we should try 
>> to make it simple as possible... we should try to remove all 
>> barriers, and make our things as easy to consume as others are doing.
>>
>> btw: I was trying to use ticketmonster to record a demo of our 
>> UberFire based Web IDE: https://www.youtube.com/watch?v=UG4pqk2r70Q
>>
>> []s
>> ___________________
>> Alexandre Porcelli
>> F: +55 11 98159-9725
>> http://about.me/porcelli
>>
>> On Fri, Oct 31, 2014 at 3:08 PM, Rafael Benevides 
>> <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>
>>     We stopped at which repos should be included.
>>
>>     Them in the other email thread I proposed to have a list of
>>     approved repos and its id, them QSTools can be used to update
>>     those repo definitions.
>>
>>
>>     On 10/31/14 15:07, Max Rydahl Andersen wrote:
>>
>>         Anything holding us back for doing it for quick starts and
>>         ticketmonster?
>>
>>         I feel we had this discussion in past but I only remember
>>         "just not done yet" ...or was there something beyond that ?
>>
>>         /max
>>         http://about.me/maxandersen
>>
>>
>>             On 31 Oct 2014, at 17:50, Rafael Benevides
>>             <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>
>>             This was only done for the archetypes
>>
>>                 On 10/31/14 13:44, Max Rydahl Andersen wrote:
>>                 Didn't we do inject of these when Productization
>>                 built them ?
>>
>>                 Or was this only done for the archetypes ?
>>
>>
>>
>>                 /max
>>                 http://about.me/maxandersen
>>
>>
>>                     On 31 Oct 2014, at 14:36, Vineet Reynolds Pereira
>>                     <vpereira at redhat.com
>>                     <mailto:vpereira at redhat.com>> wrote:
>>
>>
>>
>>                     ----- Original Message -----
>>
>>                         From: "Max Rydahl Andersen"
>>                         <max.andersen at redhat.com
>>                         <mailto:max.andersen at redhat.com>>
>>                         To: "Rafael Benevides" <benevides at redhat.com
>>                         <mailto:benevides at redhat.com>>
>>                         Cc: jbossdeveloper at lists.jboss.org
>>                         <mailto:jbossdeveloper at lists.jboss.org>,
>>                         "Alexandre Porcelli"
>>                         <alexandre.porcelli at gmail.com
>>                         <mailto:alexandre.porcelli at gmail.com>>,
>>                         "Tomas Repel"
>>                         <trepel at redhat.com
>>                         <mailto:trepel at redhat.com>>, "Nikoleta
>>                         Ziakova" <nziakova at redhat.com
>>                         <mailto:nziakova at redhat.com>>
>>                         Sent: Friday, October 31, 2014 6:53:43 PM
>>                         Subject: Re: [jbossdeveloper] <repository />
>>                         on quickstarts pom.xml
>>
>>                             On 31 Oct 2014, at 13:58, Rafael
>>                             Benevides wrote:
>>
>>                             I know which dependencies were causing
>>                             the build to fail and where to
>>                             find them, but it seems that Alexandre
>>                             wanted to show users how to run
>>                             a
>>                             project as easy as clone, build and run.
>>
>>                             If I'm not wrong, this discussion started
>>                             with similar issues in this
>>                             Arun Gupta Twitter thread:
>>                             https://twitter.com/arungupta/status/502854638832730112
>>
>>                         so this is a different question.
>>
>>                         Question is if we should add the
>>                         techpreview/all to
>>                         quickstarts/examples.
>>
>>                         Not about earlyaccess.
>>
>>                         And afaik we already did this for quickstarts
>>                         with a clear warning,
>>                         right ?
>>
>>                     AFAIK, they're not in the POM of the quickstarts.
>>                     A settings.xml is supplied instead:
>>                     https://github.com/jboss-developer/jboss-wfk-quickstarts/blob/2.6.0.Final/settings.xml
>>
>>                     But, that would deflect the original question on
>>                     whether we should add it to POM.
>>                     Honestly, I dont mind adding it, with the warning
>>                     that for a real-world project, the repo should
>>                     instead be in the settings.xml.
>>
>>                         Thus if ticketmonster does not have that in
>>                         there I would say it would
>>                         make sense to add it
>>                         with similar warning/text as the quickstarts.
>>
>>                         /max
>>
>>                             As I also told Alexandre that we were
>>                             having this discussion, I
>>                             invited
>>                             him to give his feedback on this Thread
>>                             so he can provide more
>>                             details.
>>
>>                             Alexandre,
>>
>>                             Do you mind to share your restrictions
>>                             and perceptions about the build
>>                             process ?
>>
>>                             On 10/31/14 06:47, Marek Novotny wrote:
>>
>>                                         What restrictions does he have ?
>>
>>                                         And I guess the issue here is
>>                                         ticketmonster master needs the
>>                                         earlyaccess bits ?
>>
>>                                         I think ticketmonster master
>>                                         could add the earlyaccess to
>>                                         its pom
>>                                         but
>>                                         then just make sure once it
>>                                         is releaesed it gets removed
>>                                         which
>>                                         should
>>                                         be fine since then it should
>>                                         be using any earlyaccess bundles,
>>                                         right ?
>>
>>                                 Not really, ticket-monster master
>>                                 branch doesn't exist. The closest
>>                                 to
>>                                 master is 2.6.0.Final -
>>                                 https://github.com/jboss-developer/ticket-monster/tree/2.6.0.Final
>>                                 -
>>                                 which is the tight to WFK 2.6.0.GA
>>                                 <http://2.6.0.ga/> and all GAVs
>>                                 should be resolvable
>>                                 fromhttp://maven.repository.redhat.com/techpreview/all/
>>                                 <http://maven.repository.redhat.com/techpreview/all/>
>>
>>                                 I think that Rafael knows that
>>                                 2.7.x-develop is unstable and includes
>>                                 internal product GAVs which are not
>>                                 in all or earlyaccess.
>>
>>                                 So if Alexandre uses 2.6.0.Final
>>                                 branch/tag he should get it to work
>>                                 just with online redhat repository
>>                                 http://maven.repository.redhat.com/techpreview/all/.
>>                                 If not please
>>                                 advice him to send errors to Vineet
>>                                 or me.
>>
>>                             _______________________________________________
>>                             jbossdeveloper mailing list
>>                             jbossdeveloper at lists.jboss.org
>>                             <mailto:jbossdeveloper at lists.jboss.org>
>>                             https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>
>>                         /max
>>                         http://about.me/maxandersen
>>                         _______________________________________________
>>                         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
>>
>>                 _______________________________________________
>>                 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
>
>
>
> _______________________________________________
> 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/20141124/3ff3a613/attachment-0001.html 

From pmuir at redhat.com  Tue Nov 25 05:21:48 2014
From: pmuir at redhat.com (Pete Muir)
Date: Tue, 25 Nov 2014 10:21:48 +0000
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <547391C5.60106@redhat.com>
References: <53FB3100.4020501@redhat.com>
	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>
	<246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>
	<5452ADAB.2060803@redhat.com>
	<4A802246-C724-491F-8A4A-9480142A1B6A@redhat.com>
	<54534CA6.9050303@redhat.com> <54538780.5070509@redhat.com>
	<B20848FF-2F53-4AF6-9C8D-3E8CF25A1D96@redhat.com>
	<1753895673.3004550.1414762450254.JavaMail.zimbra@redhat.com>
	<638CC3E7-0036-4EF4-9C91-9F9F82DD805B@redhat.com>
	<5453BDCB.1060104@redhat.com>
	<0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>
	<5453C21D.5040203@redhat.com>
	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>
	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>
	<547391C5.60106@redhat.com>
Message-ID: <3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>

Ideally sooner rather than later, but I think it?s too late for EAP 6.4

> On 24 Nov 2014, at 20:15, Sande Gilda <sgilda at redhat.com> wrote:
> 
> What is the timeline for this? Am I supposed to do this for the JBoss EAP 6.4 quickstarts or for the EAP 7 release? I think it will have a pretty big QE impact. Plus, this change not only impacts the quickstarts, but the documentation.
> 
> On 11/17/2014 06:00 AM, Pete Muir wrote:
>> Agreed, and it was this logic that led to us deciding to introduce the repo into the POM.
>> 
>>> On 11 Nov 2014, at 14:37, Alexandre Porcelli <alexandre.porcelli at gmail.com <mailto:alexandre.porcelli at gmail.com>> wrote:
>>> 
>>> Sorry for my late reply... I was on PTO (in fact I return tomorrow)
>>> 
>>> First of all... I understand all the reasoning behind the issues that makes us avoid use maven central for our stuff, I'm also a seasoned developer with good expirience on maven config - so touch my settings.xml isn't a problem, or even change myself some POMs wouldn't be a problem too.
>>> 
>>> So what's the problem? Simplicity (or lack of it)! If Ticketmonster is our `petclinic`, we should make it easy to build and deploy as spring's petclinic is... git clone; mvn clean install and done!
>>> 
>>> Ticketmonster uses a default branch called "2.7.x-develop" (after cloning and I had to double check if I did anything wrong... I questioned myself if I cloned the right project; if i had changed branches accidently; and finally if 2.7.x was really the latest version); then I tried to build, no pom.xml on the root (fine, it was quick to find the real sources directory); finally I run the build (tried the innocent `mvn clean install`) - and got lots of error messages. You can arguee that I didn't follow the tutorial... and you're right! But how many developers are also skiping the tutorial and are trying to build the app directly? How many people we're loosing on this process?
>>> 
>>> If we want to make our technology accessible to people, we should try to make it simple as possible... we should try to remove all barriers, and make our things as easy to consume as others are doing.
>>> 
>>> btw: I was trying to use ticketmonster to record a demo of our UberFire based Web IDE: https://www.youtube.com/watch?v=UG4pqk2r70Q <https://www.youtube.com/watch?v=UG4pqk2r70Q>
>>> 
>>> []s
>>> ___________________
>>> Alexandre Porcelli
>>> F: +55 11 98159-9725
>>> http://about.me/porcelli <http://about.me/porcelli>
>>> 
>>> On Fri, Oct 31, 2014 at 3:08 PM, Rafael Benevides <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>> We stopped at which repos should be included.
>>> 
>>> Them in the other email thread I proposed to have a list of approved repos and its id, them QSTools can be used to update those repo definitions.
>>> 
>>> 
>>> On 10/31/14 15:07, Max Rydahl Andersen wrote:
>>> Anything holding us back for doing it for quick starts and ticketmonster?
>>> 
>>> I feel we had this discussion in past but I only remember "just not done yet" ...or was there something beyond that ?
>>> 
>>> /max
>>> http://about.me/maxandersen <http://about.me/maxandersen>
>>> 
>>> 
>>> On 31 Oct 2014, at 17:50, Rafael Benevides <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>> 
>>> This was only done for the archetypes
>>> 
>>> On 10/31/14 13:44, Max Rydahl Andersen wrote:
>>> Didn't we do inject of these when Productization built them ?
>>> 
>>> Or was this only done for the archetypes ?
>>> 
>>> 
>>> 
>>> /max
>>> http://about.me/maxandersen <http://about.me/maxandersen>
>>> 
>>> 
>>> On 31 Oct 2014, at 14:36, Vineet Reynolds Pereira <vpereira at redhat.com <mailto:vpereira at redhat.com>> wrote:
>>> 
>>> 
>>> 
>>> ----- Original Message -----
>>> From: "Max Rydahl Andersen" <max.andersen at redhat.com <mailto:max.andersen at redhat.com>>
>>> To: "Rafael Benevides" <benevides at redhat.com <mailto:benevides at redhat.com>>
>>> Cc: jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>, "Alexandre Porcelli" <alexandre.porcelli at gmail.com <mailto:alexandre.porcelli at gmail.com>>, "Tomas Repel"
>>> <trepel at redhat.com <mailto:trepel at redhat.com>>, "Nikoleta Ziakova" <nziakova at redhat.com <mailto:nziakova at redhat.com>>
>>> Sent: Friday, October 31, 2014 6:53:43 PM
>>> Subject: Re: [jbossdeveloper] <repository /> on quickstarts pom.xml
>>> 
>>> On 31 Oct 2014, at 13:58, Rafael Benevides wrote:
>>> 
>>> I know which dependencies were causing the build to fail and where to
>>> find them, but it seems that Alexandre wanted to show users how to run
>>> a
>>> project as easy as clone, build and run.
>>> 
>>> If I'm not wrong, this discussion started with similar issues in this
>>> Arun Gupta Twitter thread:
>>> https://twitter.com/arungupta/status/502854638832730112 <https://twitter.com/arungupta/status/502854638832730112>
>>> so this is a different question.
>>> 
>>> Question is if we should add the techpreview/all to
>>> quickstarts/examples.
>>> 
>>> Not about earlyaccess.
>>> 
>>> And afaik we already did this for quickstarts with a clear warning,
>>> right ?
>>> AFAIK, they're not in the POM of the quickstarts. A settings.xml is supplied instead:
>>> https://github.com/jboss-developer/jboss-wfk-quickstarts/blob/2.6.0.Final/settings.xml <https://github.com/jboss-developer/jboss-wfk-quickstarts/blob/2.6.0.Final/settings.xml>
>>> 
>>> But, that would deflect the original question on whether we should add it to POM.
>>> Honestly, I dont mind adding it, with the warning that for a real-world project, the repo should instead be in the settings.xml.
>>> 
>>> Thus if ticketmonster does not have that in there I would say it would
>>> make sense to add it
>>> with similar warning/text as the quickstarts.
>>> 
>>> /max
>>> 
>>> As I also told Alexandre that we were having this discussion, I
>>> invited
>>> him to give his feedback on this Thread so he can provide more
>>> details.
>>> 
>>> Alexandre,
>>> 
>>> Do you mind to share your restrictions and perceptions about the build
>>> process ?
>>> 
>>> On 10/31/14 06:47, Marek Novotny wrote:
>>> What restrictions does he have ?
>>> 
>>> And I guess the issue here is ticketmonster master needs the
>>> earlyaccess bits ?
>>> 
>>> I think ticketmonster master could add the earlyaccess to its pom
>>> but
>>> then just make sure once it is releaesed it gets removed which
>>> should
>>> be fine since then it should be using any earlyaccess bundles,
>>> right ?
>>> Not really, ticket-monster master branch doesn't exist. The closest
>>> to
>>> master is 2.6.0.Final -
>>> https://github.com/jboss-developer/ticket-monster/tree/2.6.0.Final <https://github.com/jboss-developer/ticket-monster/tree/2.6.0.Final>  -
>>> which is the tight to WFK 2.6.0.GA <http://2.6.0.ga/> and all GAVs should be resolvable
>>> fromhttp://maven.repository.redhat.com/techpreview/all/ <http://maven.repository.redhat.com/techpreview/all/>
>>> 
>>> I think that Rafael knows that 2.7.x-develop is unstable and includes
>>> internal product GAVs which are not in all or earlyaccess.
>>> 
>>> So if Alexandre uses 2.6.0.Final branch/tag he should get it to work
>>> just with online redhat repository
>>> http://maven.repository.redhat.com/techpreview/all/ <http://maven.repository.redhat.com/techpreview/all/>. If not please
>>> advice him to send errors to Vineet or me.
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper <https://lists.jboss.org/mailman/listinfo/jbossdeveloper>
>>> /max
>>> http://about.me/maxandersen <http://about.me/maxandersen>
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper <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 <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 <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 <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 <https://lists.jboss.org/mailman/listinfo/jbossdeveloper>

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

From mnovotny at redhat.com  Tue Nov 25 06:32:44 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Tue, 25 Nov 2014 12:32:44 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>
References: <53FB3100.4020501@redhat.com>	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>	<246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>	<5452ADAB.2060803@redhat.com>	<4A802246-C724-491F-8A4A-9480142A1B6A@redhat.com>	<54534CA6.9050303@redhat.com>
	<54538780.5070509@redhat.com>	<B20848FF-2F53-4AF6-9C8D-3E8CF25A1D96@redhat.com>	<1753895673.3004550.1414762450254.JavaMail.zimbra@redhat.com>	<638CC3E7-0036-4EF4-9C91-9F9F82DD805B@redhat.com>	<5453BDCB.1060104@redhat.com>	<0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>	<5453C21D.5040203@redhat.com>	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>	<547391C5.60106@redhat.com>
	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>
Message-ID: <547468DC.3090906@redhat.com>

WFK quickstarts already has injected the product repository, so WFK
2.7.0 will be released with it

On 25.11.2014 11:21, Pete Muir wrote:
> Ideally sooner rather than later, but I think it?s too late for EAP 6.4
>
>> On 24 Nov 2014, at 20:15, Sande Gilda <sgilda at redhat.com
>> <mailto:sgilda at redhat.com>> wrote:
>>
>> What is the timeline for this? Am I supposed to do this for the JBoss
>> EAP 6.4 quickstarts or for the EAP 7 release? I think it will have a
>> pretty big QE impact. Plus, this change not only impacts the
>> quickstarts, but the documentation.
>>

-- 
Marek Novotny
--
WFK and Seam Product Lead

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

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

From benevides at redhat.com  Tue Nov 25 14:15:27 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 25 Nov 2014 17:15:27 -0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <547468DC.3090906@redhat.com>
References: <53FB3100.4020501@redhat.com>	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>	<246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>	<5452ADAB.2060803@redhat.com>	<4A802246-C724-491F-8A4A-9480142A1B6A@redhat.com>	<54534CA6.9050303@redhat.com>	<54538780.5070509@redhat.com>	<B20848FF-2F53-4AF6-9C8D-3E8CF25A1D96@redhat.com>	<1753895673.3004550.1414762450254.JavaMail.zimbra@redhat.com>	<638CC3E7-0036-4EF4-9C91-9F9F82DD805B@redhat.com>	<5453BDCB.1060104@redhat.com>	<0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>	<5453C21D.5040203@redhat.com>	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>	<547391C5.60106@redhat.com>	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>
	<547468DC.3090906@redhat.com>
Message-ID: <5474D54F.6080204@redhat.com>

That's awesome!

What about other products Quickstarts? Ideally all Quickstarts owners 
should sign jbossdeveloper list to be aware of JBoss Developer Materials 
Guidelines, but I'm not sure if all of them are signed as users.

I added the following message to latest QSTools version (1.5.0.CR3) 
report: " Keep in touch with latest JBoss Developer guidelines 
discussion at the following mailinglist: jbossdeveloper at lists.jboss.org"

I'm copying everybody to ask them to sign jbossdeveloper at lists.jboss.org 
( https://lists.jboss.org/mailman/listinfo/jbossdeveloper ) if they 
didn't sign already.

Besides that, I'll create a MOJO document to keep a contact list of all 
Quickstarts "owners" by product.


On 11/25/14 09:32, Marek Novotny wrote:
> WFK quickstarts already has injected the product repository, so WFK 
> 2.7.0 will be released with it
>
> On 25.11.2014 11:21, Pete Muir wrote:
>> Ideally sooner rather than later, but I think it?s too late for EAP 6.4
>>
>>> On 24 Nov 2014, at 20:15, Sande Gilda <sgilda at redhat.com 
>>> <mailto:sgilda at redhat.com>> wrote:
>>>
>>> What is the timeline for this? Am I supposed to do this for the 
>>> JBoss EAP 6.4 quickstarts or for the EAP 7 release? I think it will 
>>> have a pretty big QE impact. Plus, this change not only impacts the 
>>> quickstarts, but the documentation.
>>>
>
> -- 
> 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

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

From rsearls at redhat.com  Tue Nov 25 19:21:57 2014
From: rsearls at redhat.com (Rebecca Searls)
Date: Tue, 25 Nov 2014 19:21:57 -0500 (EST)
Subject: [jbossdeveloper] where is
 org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
In-Reply-To: <662938302.18188857.1416961159283.JavaMail.zimbra@redhat.com>
References: <662938302.18188857.1416961159283.JavaMail.zimbra@redhat.com>
Message-ID: <1819535387.18189290.1416961317394.JavaMail.zimbra@redhat.com>



I'm adding quickstarts to https://github.com/jboss-developer/jboss-eap-quickstarts  6.4.x-develop
None of the quickstarts are buildable because org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
is not found.  

    [ERROR]     Non-resolvable import POM: Failure to find org.jboss.bom.eap:jboss-javaee-6.0-with-tools:pom:6.2.0-build-7 in    
    http://maven.repository.redhat.com/earlyaccess/all/ was cached in the local repository, resolution will not be reattempted until the
    update interval of jboss-earlyaccess-repository has elapsed or updates are forced @ line 74, column 25 -> [Help 2]

I am using the cmd

      mvn clean install jboss-as:deploy -s $QUICKSTART_HOME/settings.xml

What is the repo that should be referenced?

From mnovotny at redhat.com  Wed Nov 26 02:41:51 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Wed, 26 Nov 2014 08:41:51 +0100
Subject: [jbossdeveloper] where is
	org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
In-Reply-To: <1819535387.18189290.1416961317394.JavaMail.zimbra@redhat.com>
References: <662938302.18188857.1416961159283.JavaMail.zimbra@redhat.com>
	<1819535387.18189290.1416961317394.JavaMail.zimbra@redhat.com>
Message-ID: <5475843F.5000909@redhat.com>

Not sure you use updated BOM versions, but that *-build-# are probably
in temporary Maven repo on github.

Try to use
https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.4.x-develop/contributor-settings.xml
in maven build command

On 26.11.2014 01:21, Rebecca Searls wrote:
>
> I'm adding quickstarts to https://github.com/jboss-developer/jboss-eap-quickstarts  6.4.x-develop
> None of the quickstarts are buildable because org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
> is not found.  
>
>     [ERROR]     Non-resolvable import POM: Failure to find org.jboss.bom.eap:jboss-javaee-6.0-with-tools:pom:6.2.0-build-7 in    
>     http://maven.repository.redhat.com/earlyaccess/all/ was cached in the local repository, resolution will not be reattempted until the
>     update interval of jboss-earlyaccess-repository has elapsed or updates are forced @ line 74, column 25 -> [Help 2]
>
> I am using the cmd
>
>       mvn clean install jboss-as:deploy -s $QUICKSTART_HOME/settings.xml
>
> What is the repo that should be referenced?
> _______________________________________________
> 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 sgilda at redhat.com  Wed Nov 26 07:40:25 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 26 Nov 2014 07:40:25 -0500
Subject: [jbossdeveloper] where is
	org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
In-Reply-To: <5475843F.5000909@redhat.com>
References: <662938302.18188857.1416961159283.JavaMail.zimbra@redhat.com>	<1819535387.18189290.1416961317394.JavaMail.zimbra@redhat.com>
	<5475843F.5000909@redhat.com>
Message-ID: <5475CA39.7070105@redhat.com>

Marek is right. The settings.xml file located in the root of the 
quickstart directory should work.

The full instructions are located here: 
https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md

Instructions for contributors is located here: 
https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONTRIBUTING.md

Rebecca, please ping me. I'm happy to help.

On 11/26/2014 02:41 AM, Marek Novotny wrote:
> Not sure you use updated BOM versions, but that *-build-# are probably
> in temporary Maven repo on github.
>
> Try to use
> https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.4.x-develop/contributor-settings.xml
> in maven build command
>
> On 26.11.2014 01:21, Rebecca Searls wrote:
>> I'm adding quickstarts to https://github.com/jboss-developer/jboss-eap-quickstarts  6.4.x-develop
>> None of the quickstarts are buildable because org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
>> is not found.
>>
>>      [ERROR]     Non-resolvable import POM: Failure to find org.jboss.bom.eap:jboss-javaee-6.0-with-tools:pom:6.2.0-build-7 in
>>      http://maven.repository.redhat.com/earlyaccess/all/ was cached in the local repository, resolution will not be reattempted until the
>>      update interval of jboss-earlyaccess-repository has elapsed or updates are forced @ line 74, column 25 -> [Help 2]
>>
>> I am using the cmd
>>
>>        mvn clean install jboss-as:deploy -s $QUICKSTART_HOME/settings.xml
>>
>> What is the repo that should be referenced?
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>


From rsearls at redhat.com  Tue Nov 25 19:19:19 2014
From: rsearls at redhat.com (Rebecca Searls)
Date: Tue, 25 Nov 2014 19:19:19 -0500 (EST)
Subject: [jbossdeveloper] where is
 org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
In-Reply-To: <770108376.18186444.1416960692847.JavaMail.zimbra@redhat.com>
Message-ID: <662938302.18188857.1416961159283.JavaMail.zimbra@redhat.com>


I'm adding quickstarts to https://github.com/jboss-developer/jboss-eap-quickstarts  6.4.x-develop
None of the quickstarts are buildable because org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
is not found.  

    [ERROR]     Non-resolvable import POM: Failure to find org.jboss.bom.eap:jboss-javaee-6.0-with-tools:pom:6.2.0-build-7 in    
    http://maven.repository.redhat.com/earlyaccess/all/ was cached in the local repository, resolution will not be reattempted until the
    update interval of jboss-earlyaccess-repository has elapsed or updates are forced @ line 74, column 25 -> [Help 2]

I am using the cmd

      mvn clean install jboss-as:deploy -s $QUICKSTART_HOME/settings.xml

What is the repo that should be referenced?

From benevides at redhat.com  Wed Nov 26 08:27:45 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Wed, 26 Nov 2014 11:27:45 -0200
Subject: [jbossdeveloper] where is
	org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
In-Reply-To: <5475CA39.7070105@redhat.com>
References: <662938302.18188857.1416961159283.JavaMail.zimbra@redhat.com>	<1819535387.18189290.1416961317394.JavaMail.zimbra@redhat.com>	<5475843F.5000909@redhat.com>
	<5475CA39.7070105@redhat.com>
Message-ID: <5475D551.2000308@redhat.com>

Shouldn't these quickstarts use the repository definition inside pom.xml 
to avoid this kind of issue ?


On 11/26/14 10:40, Sande Gilda wrote:
> Marek is right. The settings.xml file located in the root of the
> quickstart directory should work.
>
> The full instructions are located here:
> https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md
>
> Instructions for contributors is located here:
> https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONTRIBUTING.md
>
> Rebecca, please ping me. I'm happy to help.
>
> On 11/26/2014 02:41 AM, Marek Novotny wrote:
>> Not sure you use updated BOM versions, but that *-build-# are probably
>> in temporary Maven repo on github.
>>
>> Try to use
>> https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.4.x-develop/contributor-settings.xml
>> in maven build command
>>
>> On 26.11.2014 01:21, Rebecca Searls wrote:
>>> I'm adding quickstarts to https://github.com/jboss-developer/jboss-eap-quickstarts  6.4.x-develop
>>> None of the quickstarts are buildable because org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
>>> is not found.
>>>
>>>       [ERROR]     Non-resolvable import POM: Failure to find org.jboss.bom.eap:jboss-javaee-6.0-with-tools:pom:6.2.0-build-7 in
>>>       http://maven.repository.redhat.com/earlyaccess/all/ was cached in the local repository, resolution will not be reattempted until the
>>>       update interval of jboss-earlyaccess-repository has elapsed or updates are forced @ line 74, column 25 -> [Help 2]
>>>
>>> I am using the cmd
>>>
>>>         mvn clean install jboss-as:deploy -s $QUICKSTART_HOME/settings.xml
>>>
>>> What is the repo that should be referenced?
>>> _______________________________________________
>>> 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


From sgilda at redhat.com  Wed Nov 26 08:36:56 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 26 Nov 2014 08:36:56 -0500
Subject: [jbossdeveloper] where is
	org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
In-Reply-To: <5475D551.2000308@redhat.com>
References: <662938302.18188857.1416961159283.JavaMail.zimbra@redhat.com>	<1819535387.18189290.1416961317394.JavaMail.zimbra@redhat.com>	<5475843F.5000909@redhat.com>
	<5475CA39.7070105@redhat.com> <5475D551.2000308@redhat.com>
Message-ID: <5475D778.60703@redhat.com>

Yes. However, we're debating whether it's too late in the release cycle 
for JBoss EAP 6.4 to add them.

On 11/26/2014 08:27 AM, Rafael Benevides wrote:
> Shouldn't these quickstarts use the repository definition inside 
> pom.xml to avoid this kind of issue ?
>
>
> On 11/26/14 10:40, Sande Gilda wrote:
>> Marek is right. The settings.xml file located in the root of the
>> quickstart directory should work.
>>
>> The full instructions are located here:
>> https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md 
>>
>>
>> Instructions for contributors is located here:
>> https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONTRIBUTING.md 
>>
>>
>> Rebecca, please ping me. I'm happy to help.
>>
>> On 11/26/2014 02:41 AM, Marek Novotny wrote:
>>> Not sure you use updated BOM versions, but that *-build-# are probably
>>> in temporary Maven repo on github.
>>>
>>> Try to use
>>> https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.4.x-develop/contributor-settings.xml 
>>>
>>> in maven build command
>>>
>>> On 26.11.2014 01:21, Rebecca Searls wrote:
>>>> I'm adding quickstarts to 
>>>> https://github.com/jboss-developer/jboss-eap-quickstarts 6.4.x-develop
>>>> None of the quickstarts are buildable because 
>>>> org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
>>>> is not found.
>>>>
>>>>       [ERROR]     Non-resolvable import POM: Failure to find 
>>>> org.jboss.bom.eap:jboss-javaee-6.0-with-tools:pom:6.2.0-build-7 in
>>>>       http://maven.repository.redhat.com/earlyaccess/all/ was 
>>>> cached in the local repository, resolution will not be reattempted 
>>>> until the
>>>>       update interval of jboss-earlyaccess-repository has elapsed 
>>>> or updates are forced @ line 74, column 25 -> [Help 2]
>>>>
>>>> I am using the cmd
>>>>
>>>>         mvn clean install jboss-as:deploy -s 
>>>> $QUICKSTART_HOME/settings.xml
>>>>
>>>> What is the repo that should be referenced?
>>>> _______________________________________________
>>>> 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
>


From benevides at redhat.com  Wed Nov 26 08:40:33 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Wed, 26 Nov 2014 11:40:33 -0200
Subject: [jbossdeveloper] where is
	org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
In-Reply-To: <5475D778.60703@redhat.com>
References: <662938302.18188857.1416961159283.JavaMail.zimbra@redhat.com>	<1819535387.18189290.1416961317394.JavaMail.zimbra@redhat.com>	<5475843F.5000909@redhat.com>
	<5475CA39.7070105@redhat.com> <5475D551.2000308@redhat.com>
	<5475D778.60703@redhat.com>
Message-ID: <5475D851.30608@redhat.com>

Thanks for remembering that. I'm already looking forward to have it for 
EAP 6.5 :)

On 11/26/14 11:36, Sande Gilda wrote:
> Yes. However, we're debating whether it's too late in the release 
> cycle for JBoss EAP 6.4 to add them.
>
> On 11/26/2014 08:27 AM, Rafael Benevides wrote:
>> Shouldn't these quickstarts use the repository definition inside 
>> pom.xml to avoid this kind of issue ?
>>
>>
>> On 11/26/14 10:40, Sande Gilda wrote:
>>> Marek is right. The settings.xml file located in the root of the
>>> quickstart directory should work.
>>>
>>> The full instructions are located here:
>>> https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md 
>>>
>>>
>>> Instructions for contributors is located here:
>>> https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONTRIBUTING.md 
>>>
>>>
>>> Rebecca, please ping me. I'm happy to help.
>>>
>>> On 11/26/2014 02:41 AM, Marek Novotny wrote:
>>>> Not sure you use updated BOM versions, but that *-build-# are probably
>>>> in temporary Maven repo on github.
>>>>
>>>> Try to use
>>>> https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.4.x-develop/contributor-settings.xml 
>>>>
>>>> in maven build command
>>>>
>>>> On 26.11.2014 01:21, Rebecca Searls wrote:
>>>>> I'm adding quickstarts to 
>>>>> https://github.com/jboss-developer/jboss-eap-quickstarts 
>>>>> 6.4.x-develop
>>>>> None of the quickstarts are buildable because 
>>>>> org.jboss.bom.eap:jboss-javaee-6.0-with-tools:6.2.0-build-7
>>>>> is not found.
>>>>>
>>>>>       [ERROR]     Non-resolvable import POM: Failure to find 
>>>>> org.jboss.bom.eap:jboss-javaee-6.0-with-tools:pom:6.2.0-build-7 in
>>>>>       http://maven.repository.redhat.com/earlyaccess/all/ was 
>>>>> cached in the local repository, resolution will not be reattempted 
>>>>> until the
>>>>>       update interval of jboss-earlyaccess-repository has elapsed 
>>>>> or updates are forced @ line 74, column 25 -> [Help 2]
>>>>>
>>>>> I am using the cmd
>>>>>
>>>>>         mvn clean install jboss-as:deploy -s 
>>>>> $QUICKSTART_HOME/settings.xml
>>>>>
>>>>> What is the repo that should be referenced?
>>>>> _______________________________________________
>>>>> 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
>>
>


From vpereira at redhat.com  Thu Nov 27 05:06:00 2014
From: vpereira at redhat.com (Vineet Reynolds Pereira)
Date: Thu, 27 Nov 2014 05:06:00 -0500 (EST)
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>
References: <53FB3100.4020501@redhat.com> <5453BDCB.1060104@redhat.com>
	<0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>
	<5453C21D.5040203@redhat.com>
	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>
	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>
	<547391C5.60106@redhat.com>
	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>
Message-ID: <151036514.11189408.1417082760553.JavaMail.zimbra@redhat.com>


I have a follow-up question - should we also change the default branch to x.y.Final instead of x.y-develop ?
This naturally follows from our need to not have users perform any special configuration to get started.
End-users who clone the repo do not have to figure out how to get the SNAPSHOT artifacts.


----- Original Message -----
> From: "Pete Muir" <pmuir at redhat.com>
> To: "Sande Gilda" <sgilda at redhat.com>
> Cc: "Max Rydahl Andersen" <max.andersen at redhat.com>, jbossdeveloper at lists.jboss.org, "Alexandre Porcelli"
> <alexandre.porcelli at gmail.com>, "Tomas Repel" <trepel at redhat.com>, "Nikoleta Ziakova" <nziakova at redhat.com>
> Sent: Tuesday, November 25, 2014 3:51:48 PM
> Subject: Re: [jbossdeveloper] <repository /> on quickstarts pom.xml
> 
> Ideally sooner rather than later, but I think it?s too late for EAP 6.4
> 
> 
> 
> 
> On 24 Nov 2014, at 20:15, Sande Gilda < sgilda at redhat.com > wrote:
> 
> What is the timeline for this? Am I supposed to do this for the JBoss EAP 6.4
> quickstarts or for the EAP 7 release? I think it will have a pretty big QE
> impact. Plus, this change not only impacts the quickstarts, but the
> documentation.
> 
> On 11/17/2014 06:00 AM, Pete Muir wrote:
> 
> 
> Agreed, and it was this logic that led to us deciding to introduce the repo
> into the POM.
> 
> 
> 
> 
> On 11 Nov 2014, at 14:37, Alexandre Porcelli < alexandre.porcelli at gmail.com >
> wrote:
> 
> Sorry for my late reply... I was on PTO (in fact I return tomorrow)
> 
> First of all... I understand all the reasoning behind the issues that makes
> us avoid use maven central for our stuff, I'm also a seasoned developer with
> good expirience on maven config - so touch my settings.xml isn't a problem,
> or even change myself some POMs wouldn't be a problem too.
> 
> So what's the problem? Simplicity (or lack of it)! If Ticketmonster is our
> `petclinic`, we should make it easy to build and deploy as spring's
> petclinic is... git clone; mvn clean install and done!
> 
> Ticketmonster uses a default branch called "2.7.x-develop" (after cloning and
> I had to double check if I did anything wrong... I questioned myself if I
> cloned the right project; if i had changed branches accidently; and finally
> if 2.7.x was really the latest version); then I tried to build, no pom.xml
> on the root (fine, it was quick to find the real sources directory); finally
> I run the build (tried the innocent `mvn clean install`) - and got lots of
> error messages. You can arguee that I didn't follow the tutorial... and
> you're right! But how many developers are also skiping the tutorial and are
> trying to build the app directly? How many people we're loosing on this
> process?
> 
> If we want to make our technology accessible to people, we should try to make
> it simple as possible... we should try to remove all barriers, and make our
> things as easy to consume as others are doing.
> 
> btw: I was trying to use ticketmonster to record a demo of our UberFire based
> Web IDE: https://www.youtube.com/watch?v=UG4pqk2r70Q
> 
> []s
> ___________________
> Alexandre Porcelli
> F: +55 11 98159-9725
> http://about.me/porcelli
> 
> On Fri, Oct 31, 2014 at 3:08 PM, Rafael Benevides < benevides at redhat.com >
> wrote:
> 
> 
> We stopped at which repos should be included.
> 
> Them in the other email thread I proposed to have a list of approved repos
> and its id, them QSTools can be used to update those repo definitions.
> 
> 
> On 10/31/14 15:07, Max Rydahl Andersen wrote:
> 
> 
> Anything holding us back for doing it for quick starts and ticketmonster?
> 
> I feel we had this discussion in past but I only remember "just not done yet"
> ...or was there something beyond that ?
> 
> /max
> http://about.me/maxandersen
> 
> 
> 
> 
> On 31 Oct 2014, at 17:50, Rafael Benevides < benevides at redhat.com > wrote:
> 
> This was only done for the archetypes
> 
> 
> 
> On 10/31/14 13:44, Max Rydahl Andersen wrote:
> Didn't we do inject of these when Productization built them ?
> 
> Or was this only done for the archetypes ?
> 
> 
> 
> /max
> http://about.me/maxandersen
> 
> 
> 
> 
> On 31 Oct 2014, at 14:36, Vineet Reynolds Pereira < vpereira at redhat.com >
> wrote:
> 
> 
> 
> ----- Original Message -----
> 
> 
> From: "Max Rydahl Andersen" < max.andersen at redhat.com >
> To: "Rafael Benevides" < benevides at redhat.com >
> Cc: jbossdeveloper at lists.jboss.org , "Alexandre Porcelli" <
> alexandre.porcelli at gmail.com >, "Tomas Repel"
> < trepel at redhat.com >, "Nikoleta Ziakova" < nziakova at redhat.com >
> Sent: Friday, October 31, 2014 6:53:43 PM
> Subject: Re: [jbossdeveloper] <repository /> on quickstarts pom.xml
> 
> 
> 
> On 31 Oct 2014, at 13:58, Rafael Benevides wrote:
> 
> I know which dependencies were causing the build to fail and where to
> find them, but it seems that Alexandre wanted to show users how to run
> a
> project as easy as clone, build and run.
> 
> If I'm not wrong, this discussion started with similar issues in this
> Arun Gupta Twitter thread:
> https://twitter.com/arungupta/status/502854638832730112
> so this is a different question.
> 
> Question is if we should add the techpreview/all to
> quickstarts/examples.
> 
> Not about earlyaccess.
> 
> And afaik we already did this for quickstarts with a clear warning,
> right ?
> AFAIK, they're not in the POM of the quickstarts. A settings.xml is supplied
> instead:
> https://github.com/jboss-developer/jboss-wfk-quickstarts/blob/2.6.0.Final/settings.xml
> 
> But, that would deflect the original question on whether we should add it to
> POM.
> Honestly, I dont mind adding it, with the warning that for a real-world
> project, the repo should instead be in the settings.xml.
> 
> 
> 
> Thus if ticketmonster does not have that in there I would say it would
> make sense to add it
> with similar warning/text as the quickstarts.
> 
> /max
> 
> 
> 
> As I also told Alexandre that we were having this discussion, I
> invited
> him to give his feedback on this Thread so he can provide more
> details.
> 
> Alexandre,
> 
> Do you mind to share your restrictions and perceptions about the build
> process ?
> 
> On 10/31/14 06:47, Marek Novotny wrote:
> 
> 
> 
> 
> 
> 
> What restrictions does he have ?
> 
> And I guess the issue here is ticketmonster master needs the
> earlyaccess bits ?
> 
> I think ticketmonster master could add the earlyaccess to its pom
> but
> then just make sure once it is releaesed it gets removed which
> should
> be fine since then it should be using any earlyaccess bundles,
> right ?
> Not really, ticket-monster master branch doesn't exist. The closest
> to
> master is 2.6.0.Final -
> https://github.com/jboss-developer/ticket-monster/tree/2.6.0.Final -
> which is the tight to WFK 2.6.0.GA and all GAVs should be resolvable
> fromhttp:// maven.repository.redhat.com/techpreview/all/
> 
> I think that Rafael knows that 2.7.x-develop is unstable and includes
> internal product GAVs which are not in all or earlyaccess.
> 
> So if Alexandre uses 2.6.0.Final branch/tag he should get it to work
> just with online redhat repository
> http://maven.repository.redhat.com/techpreview/all/ . If not please
> advice him to send errors to Vineet or me.
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
> /max
> http://about.me/maxandersen
> _______________________________________________
> 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
> 
> 
> 
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


From benevides at redhat.com  Thu Nov 27 06:49:02 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Thu, 27 Nov 2014 09:49:02 -0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <151036514.11189408.1417082760553.JavaMail.zimbra@redhat.com>
References: <53FB3100.4020501@redhat.com>
	<5453BDCB.1060104@redhat.com>	<0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>	<5453C21D.5040203@redhat.com>	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>	<547391C5.60106@redhat.com>	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>
	<151036514.11189408.1417082760553.JavaMail.zimbra@redhat.com>
Message-ID: <54770FAE.9060007@redhat.com>

That's an excellent proposal since we are thinking on users that goes 
directly to github.

Anyway we shouldn't use SNAPSHOTs artifacts on -devel branch. Every 
"staging" release should be placed at 
http://jboss-developer.github.io/temp-maven-repo/ using the "-build-x" 
suffix. That's one of the reasons that I placed that repo as an approved 
one on QSTools, so we can add it on "-develop" branch. But unfortunately 
it seems that nobody is using it anymore since it's not being updated 
since July.

Besides that proposal, We also should ask to have the x.y.Final tag for 
each release.



On 11/27/14 08:06, Vineet Reynolds Pereira wrote:
> I have a follow-up question - should we also change the default branch to x.y.Final instead of x.y-develop ?
> This naturally follows from our need to not have users perform any special configuration to get started.
> End-users who clone the repo do not have to figure out how to get the SNAPSHOT artifacts.
>
>
> ----- Original Message -----
>> From: "Pete Muir" <pmuir at redhat.com>
>> To: "Sande Gilda" <sgilda at redhat.com>
>> Cc: "Max Rydahl Andersen" <max.andersen at redhat.com>, jbossdeveloper at lists.jboss.org, "Alexandre Porcelli"
>> <alexandre.porcelli at gmail.com>, "Tomas Repel" <trepel at redhat.com>, "Nikoleta Ziakova" <nziakova at redhat.com>
>> Sent: Tuesday, November 25, 2014 3:51:48 PM
>> Subject: Re: [jbossdeveloper] <repository /> on quickstarts pom.xml
>>
>> Ideally sooner rather than later, but I think it?s too late for EAP 6.4
>>
>>
>>
>>
>> On 24 Nov 2014, at 20:15, Sande Gilda < sgilda at redhat.com > wrote:
>>
>> What is the timeline for this? Am I supposed to do this for the JBoss EAP 6.4
>> quickstarts or for the EAP 7 release? I think it will have a pretty big QE
>> impact. Plus, this change not only impacts the quickstarts, but the
>> documentation.
>>
>> On 11/17/2014 06:00 AM, Pete Muir wrote:
>>
>>
>> Agreed, and it was this logic that led to us deciding to introduce the repo
>> into the POM.
>>
>>
>>
>>
>> On 11 Nov 2014, at 14:37, Alexandre Porcelli < alexandre.porcelli at gmail.com >
>> wrote:
>>
>> Sorry for my late reply... I was on PTO (in fact I return tomorrow)
>>
>> First of all... I understand all the reasoning behind the issues that makes
>> us avoid use maven central for our stuff, I'm also a seasoned developer with
>> good expirience on maven config - so touch my settings.xml isn't a problem,
>> or even change myself some POMs wouldn't be a problem too.
>>
>> So what's the problem? Simplicity (or lack of it)! If Ticketmonster is our
>> `petclinic`, we should make it easy to build and deploy as spring's
>> petclinic is... git clone; mvn clean install and done!
>>
>> Ticketmonster uses a default branch called "2.7.x-develop" (after cloning and
>> I had to double check if I did anything wrong... I questioned myself if I
>> cloned the right project; if i had changed branches accidently; and finally
>> if 2.7.x was really the latest version); then I tried to build, no pom.xml
>> on the root (fine, it was quick to find the real sources directory); finally
>> I run the build (tried the innocent `mvn clean install`) - and got lots of
>> error messages. You can arguee that I didn't follow the tutorial... and
>> you're right! But how many developers are also skiping the tutorial and are
>> trying to build the app directly? How many people we're loosing on this
>> process?
>>
>> If we want to make our technology accessible to people, we should try to make
>> it simple as possible... we should try to remove all barriers, and make our
>> things as easy to consume as others are doing.
>>
>> btw: I was trying to use ticketmonster to record a demo of our UberFire based
>> Web IDE: https://www.youtube.com/watch?v=UG4pqk2r70Q
>>
>> []s
>> ___________________
>> Alexandre Porcelli
>> F: +55 11 98159-9725
>> http://about.me/porcelli
>>
>> On Fri, Oct 31, 2014 at 3:08 PM, Rafael Benevides < benevides at redhat.com >
>> wrote:
>>
>>
>> We stopped at which repos should be included.
>>
>> Them in the other email thread I proposed to have a list of approved repos
>> and its id, them QSTools can be used to update those repo definitions.
>>
>>
>> On 10/31/14 15:07, Max Rydahl Andersen wrote:
>>
>>
>> Anything holding us back for doing it for quick starts and ticketmonster?
>>
>> I feel we had this discussion in past but I only remember "just not done yet"
>> ...or was there something beyond that ?
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>>
>>
>> On 31 Oct 2014, at 17:50, Rafael Benevides < benevides at redhat.com > wrote:
>>
>> This was only done for the archetypes
>>
>>
>>
>> On 10/31/14 13:44, Max Rydahl Andersen wrote:
>> Didn't we do inject of these when Productization built them ?
>>
>> Or was this only done for the archetypes ?
>>
>>
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>>
>>
>> On 31 Oct 2014, at 14:36, Vineet Reynolds Pereira < vpereira at redhat.com >
>> wrote:
>>
>>
>>
>> ----- Original Message -----
>>
>>
>> From: "Max Rydahl Andersen" < max.andersen at redhat.com >
>> To: "Rafael Benevides" < benevides at redhat.com >
>> Cc: jbossdeveloper at lists.jboss.org , "Alexandre Porcelli" <
>> alexandre.porcelli at gmail.com >, "Tomas Repel"
>> < trepel at redhat.com >, "Nikoleta Ziakova" < nziakova at redhat.com >
>> Sent: Friday, October 31, 2014 6:53:43 PM
>> Subject: Re: [jbossdeveloper] <repository /> on quickstarts pom.xml
>>
>>
>>
>> On 31 Oct 2014, at 13:58, Rafael Benevides wrote:
>>
>> I know which dependencies were causing the build to fail and where to
>> find them, but it seems that Alexandre wanted to show users how to run
>> a
>> project as easy as clone, build and run.
>>
>> If I'm not wrong, this discussion started with similar issues in this
>> Arun Gupta Twitter thread:
>> https://twitter.com/arungupta/status/502854638832730112
>> so this is a different question.
>>
>> Question is if we should add the techpreview/all to
>> quickstarts/examples.
>>
>> Not about earlyaccess.
>>
>> And afaik we already did this for quickstarts with a clear warning,
>> right ?
>> AFAIK, they're not in the POM of the quickstarts. A settings.xml is supplied
>> instead:
>> https://github.com/jboss-developer/jboss-wfk-quickstarts/blob/2.6.0.Final/settings.xml
>>
>> But, that would deflect the original question on whether we should add it to
>> POM.
>> Honestly, I dont mind adding it, with the warning that for a real-world
>> project, the repo should instead be in the settings.xml.
>>
>>
>>
>> Thus if ticketmonster does not have that in there I would say it would
>> make sense to add it
>> with similar warning/text as the quickstarts.
>>
>> /max
>>
>>
>>
>> As I also told Alexandre that we were having this discussion, I
>> invited
>> him to give his feedback on this Thread so he can provide more
>> details.
>>
>> Alexandre,
>>
>> Do you mind to share your restrictions and perceptions about the build
>> process ?
>>
>> On 10/31/14 06:47, Marek Novotny wrote:
>>
>>
>>
>>
>>
>>
>> What restrictions does he have ?
>>
>> And I guess the issue here is ticketmonster master needs the
>> earlyaccess bits ?
>>
>> I think ticketmonster master could add the earlyaccess to its pom
>> but
>> then just make sure once it is releaesed it gets removed which
>> should
>> be fine since then it should be using any earlyaccess bundles,
>> right ?
>> Not really, ticket-monster master branch doesn't exist. The closest
>> to
>> master is 2.6.0.Final -
>> https://github.com/jboss-developer/ticket-monster/tree/2.6.0.Final -
>> which is the tight to WFK 2.6.0.GA and all GAVs should be resolvable
>> fromhttp:// maven.repository.redhat.com/techpreview/all/
>>
>> I think that Rafael knows that 2.7.x-develop is unstable and includes
>> internal product GAVs which are not in all or earlyaccess.
>>
>> So if Alexandre uses 2.6.0.Final branch/tag he should get it to work
>> just with online redhat repository
>> http://maven.repository.redhat.com/techpreview/all/ . If not please
>> advice him to send errors to Vineet or me.
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>> /max
>> http://about.me/maxandersen
>> _______________________________________________
>> 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
>>
>>
>>
>> _______________________________________________
>> 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


From jcoleman at redhat.com  Thu Nov 27 06:50:29 2014
From: jcoleman at redhat.com (Julian Coleman)
Date: Thu, 27 Nov 2014 11:50:29 +0000
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <5474D54F.6080204@redhat.com>
References: <638CC3E7-0036-4EF4-9C91-9F9F82DD805B@redhat.com>
	<5453BDCB.1060104@redhat.com>
	<0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>
	<5453C21D.5040203@redhat.com>
	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>
	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>
	<547391C5.60106@redhat.com>
	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>
	<547468DC.3090906@redhat.com> <5474D54F.6080204@redhat.com>
Message-ID: <20141127115029.GG2643@cyfynwy.redhat.com>

Hi,

Just trying to summarise this thread (and I have questions).

The developer materials will have repositories sections in their POM files
that will point to released maven artifacts in the Red Hat public repository.
We won't alter them with the (Wolf-compatible) tooling that strips out any
repository section from POM files.

How will the tests be done?  Artifacts are not added to the repository until
the release is signed off.  Will we start using the staging repository?  Will
the product branches have the staging repository added to the POM files (as
well as, or instead of, the release repository)?

Thanks,

J

-- 
Red Hat
Newcastle upon Tyne

From benevides at redhat.com  Thu Nov 27 06:58:41 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Thu, 27 Nov 2014 09:58:41 -0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <20141127115029.GG2643@cyfynwy.redhat.com>
References: <638CC3E7-0036-4EF4-9C91-9F9F82DD805B@redhat.com>	<5453BDCB.1060104@redhat.com>	<0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>	<5453C21D.5040203@redhat.com>	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>	<547391C5.60106@redhat.com>	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>	<547468DC.3090906@redhat.com>
	<5474D54F.6080204@redhat.com>
	<20141127115029.GG2643@cyfynwy.redhat.com>
Message-ID: <547711F1.2040809@redhat.com>


On 11/27/14 09:50, Julian Coleman wrote:
> Hi,
>
> Just trying to summarise this thread (and I have questions).
>
> The developer materials will have repositories sections in their POM files
> that will point to released maven artifacts in the Red Hat public repository.
Yes
> We won't alter them with the (Wolf-compatible) tooling that strips out any
> repository section from POM files.
>
> How will the tests be done?
> Artifacts are not added to the repository until
> the release is signed off.  Will we start using the staging repository?
I think that the staging repo is the answer here for testing purposes.

>   Will
> the product branches have the staging repository added to the POM files (as
> well as, or instead of, the release repository)?
I think so, otherwise we won't achieve our objectives to have buildable 
sources at github.
>
> Thanks,
>
> J
>


From jcoleman at redhat.com  Thu Nov 27 07:04:23 2014
From: jcoleman at redhat.com (Julian Coleman)
Date: Thu, 27 Nov 2014 12:04:23 +0000
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <547711F1.2040809@redhat.com>
References: <0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>
	<5453C21D.5040203@redhat.com>
	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>
	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>
	<547391C5.60106@redhat.com>
	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>
	<547468DC.3090906@redhat.com> <5474D54F.6080204@redhat.com>
	<20141127115029.GG2643@cyfynwy.redhat.com>
	<547711F1.2040809@redhat.com>
Message-ID: <20141127120423.GJ2643@cyfynwy.redhat.com>

Hi,

> I think that the staging repo is the answer here for testing purposes.

I think that this makes sense too.  However, I'm not sure how we will test
the final version, as that will need a reference to the public repository
and be tested before the public repository contains the artifacts.

> I think so, otherwise we won't achieve our objectives to have buildable
> sources at github.

Will it matter if we reference an internal repository in the sources?
(It won't be possible to build them trivially from outside the Red Hat
network.)

Thanks,

J

-- 
Red Hat
Newcastle upon Tyne

From benevides at redhat.com  Thu Nov 27 07:15:17 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Thu, 27 Nov 2014 10:15:17 -0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <20141127120423.GJ2643@cyfynwy.redhat.com>
References: <0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>	<5453C21D.5040203@redhat.com>	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>	<547391C5.60106@redhat.com>	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>	<547468DC.3090906@redhat.com>
	<5474D54F.6080204@redhat.com>	<20141127115029.GG2643@cyfynwy.redhat.com>	<547711F1.2040809@redhat.com>
	<20141127120423.GJ2643@cyfynwy.redhat.com>
Message-ID: <547715D5.9090109@redhat.com>


On 11/27/14 10:04, Julian Coleman wrote:
> Hi,
>
>> I think that the staging repo is the answer here for testing purposes.
> I think that this makes sense too.  However, I'm not sure how we will test
> the final version, as that will need a reference to the public repository
> and be tested before the public repository contains the artifacts.
We use a different process that we have the final versions released 
previously having the "-build-x" suffix at the version and place those 
versions at http://jboss-developer.github.io/temp-maven-repo/ repo 
(which is our "staging" repo until we have a nexus server setup). But I 
know that this process is particular and couldn't fit for every project. 
Do you see any restrictions to test the final version using the internal 
repo and having that repo defined in settings.xml ?
>
>> I think so, otherwise we won't achieve our objectives to have buildable
>> sources at github.
> Will it matter if we reference an internal repository in the sources?
> (It won't be possible to build them trivially from outside the Red Hat
> network.)
In that case, that's why we used 
http://jboss-developer.github.io/temp-maven-repo/ as a staging maven repo.
> Thanks,
>
> J
>


From jcoleman at redhat.com  Thu Nov 27 07:17:36 2014
From: jcoleman at redhat.com (Julian Coleman)
Date: Thu, 27 Nov 2014 12:17:36 +0000
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <547715D5.9090109@redhat.com>
References: <CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>
	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>
	<547391C5.60106@redhat.com>
	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>
	<547468DC.3090906@redhat.com> <5474D54F.6080204@redhat.com>
	<20141127115029.GG2643@cyfynwy.redhat.com>
	<547711F1.2040809@redhat.com>
	<20141127120423.GJ2643@cyfynwy.redhat.com>
	<547715D5.9090109@redhat.com>
Message-ID: <20141127121736.GN2643@cyfynwy.redhat.com>

Hi,

> We use a different process that we have the final versions released
> previously having the "-build-x" suffix at the version and place those
> versions at http://jboss-developer.github.io/temp-maven-repo/ repo (which is
> our "staging" repo until we have a nexus server setup). But I know that this
> process is particular and couldn't fit for every project. Do you see any
> restrictions to test the final version using the internal repo and having
> that repo defined in settings.xml ?

Yes - the product internal builds artifacts are not currently uploaded to:

  http://jboss-developer.github.io/temp-maven-repo/

It's probably sensible to have product internal releases available more
publically, but I don't think that we're there yet.

Thanks,

J

-- 
Red Hat
Newcastle upon Tyne

From mnovotny at redhat.com  Thu Nov 27 07:19:42 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Thu, 27 Nov 2014 13:19:42 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <547715D5.9090109@redhat.com>
References: <0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>	<5453C21D.5040203@redhat.com>	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>	<547391C5.60106@redhat.com>	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>	<547468DC.3090906@redhat.com>	<5474D54F.6080204@redhat.com>	<20141127115029.GG2643@cyfynwy.redhat.com>	<547711F1.2040809@redhat.com>	<20141127120423.GJ2643@cyfynwy.redhat.com>
	<547715D5.9090109@redhat.com>
Message-ID: <547716DE.90902@redhat.com>

Julian, I would suggest to use maven cli "-s" with settings to your
staging repository. Do not inject that into quickstarts, repositories
are injected ONLY for public end users. We are advanced users so we
should use CLI with a specified settings.xml.

We should not publish any product artefact into
http://jboss-developer.github.io/temp-maven-repo/

I would consider that repository only for upstream BOMs publicly available.


On 27.11.2014 13:15, Rafael Benevides wrote:
> On 11/27/14 10:04, Julian Coleman wrote:
>> Hi,
>>
>>> I think that the staging repo is the answer here for testing purposes.
>> I think that this makes sense too.  However, I'm not sure how we will test
>> the final version, as that will need a reference to the public repository
>> and be tested before the public repository contains the artifacts.
> We use a different process that we have the final versions released 
> previously having the "-build-x" suffix at the version and place those 
> versions at http://jboss-developer.github.io/temp-maven-repo/ repo 
> (which is our "staging" repo until we have a nexus server setup). But I 
> know that this process is particular and couldn't fit for every project. 
> Do you see any restrictions to test the final version using the internal 
> repo and having that repo defined in settings.xml ?
>>> I think so, otherwise we won't achieve our objectives to have buildable
>>> sources at github.
>> Will it matter if we reference an internal repository in the sources?
>> (It won't be possible to build them trivially from outside the Red Hat
>> network.)
> In that case, that's why we used 
> http://jboss-developer.github.io/temp-maven-repo/ as a staging maven repo.
>> Thanks,
>>
>> J
>>
> _______________________________________________
> 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  Thu Nov 27 07:21:39 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Thu, 27 Nov 2014 13:21:39 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <54770FAE.9060007@redhat.com>
References: <53FB3100.4020501@redhat.com>	<5453BDCB.1060104@redhat.com>	<0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>	<5453C21D.5040203@redhat.com>	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>	<547391C5.60106@redhat.com>	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>	<151036514.11189408.1417082760553.JavaMail.zimbra@redhat.com>
	<54770FAE.9060007@redhat.com>
Message-ID: <54771753.2060703@redhat.com>

you can't use any internal released artefact in 

http://jboss-developer.github.io/temp-maven-repo/ with the "-build-x"


On 27.11.2014 12:49, Rafael Benevides wrote:
> That's an excellent proposal since we are thinking on users that goes 
> directly to github.
>
> Anyway we shouldn't use SNAPSHOTs artifacts on -devel branch. Every 
> "staging" release should be placed at 
> http://jboss-developer.github.io/temp-maven-repo/ using the "-build-x" 
> suffix. That's one of the reasons that I placed that repo as an approved 
> one on QSTools, so we can add it on "-develop" branch. But unfortunately 
> it seems that nobody is using it anymore since it's not being updated 
> since July.
>
> Besides that proposal, We also should ask to have the x.y.Final tag for 
> each release.
>
>
>
> On 11/27/14 08:06, Vineet Reynolds Pereira wrote:
>> I have a follow-up question - should we also change the default branch to x.y.Final instead of x.y-develop ?
>> This naturally follows from our need to not have users perform any special configuration to get started.
>> End-users who clone the repo do not have to figure out how to get the SNAPSHOT artifacts.
>>
>>
>> --


-- 
Marek Novotny
--
WFK and Seam Product Lead

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


From sgilda at redhat.com  Thu Nov 27 08:25:34 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 27 Nov 2014 08:25:34 -0500
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <547715D5.9090109@redhat.com>
References: <0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>	<5453C21D.5040203@redhat.com>	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>	<547391C5.60106@redhat.com>	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>	<547468DC.3090906@redhat.com>	<5474D54F.6080204@redhat.com>	<20141127115029.GG2643@cyfynwy.redhat.com>	<547711F1.2040809@redhat.com>	<20141127120423.GJ2643@cyfynwy.redhat.com>
	<547715D5.9090109@redhat.com>
Message-ID: <5477264E.1040306@redhat.com>

I am a little confused by this discussion.

Are we saying we will add the staging repo [1] to the development branch 
POM files only and we then have to strip them from the product branch 
POM files? I think it is going to be hard to maintain different POM file 
contents in different branches.

[1] http://jboss-developer.github.io/temp-maven-repo

On 11/27/2014 07:15 AM, Rafael Benevides wrote:
> On 11/27/14 10:04, Julian Coleman wrote:
>> Hi,
>>
>>> I think that the staging repo is the answer here for testing purposes.
>> I think that this makes sense too.  However, I'm not sure how we will test
>> the final version, as that will need a reference to the public repository
>> and be tested before the public repository contains the artifacts.
> We use a different process that we have the final versions released
> previously having the "-build-x" suffix at the version and place those
> versions at http://jboss-developer.github.io/temp-maven-repo/ repo
> (which is our "staging" repo until we have a nexus server setup). But I
> know that this process is particular and couldn't fit for every project.
> Do you see any restrictions to test the final version using the internal
> repo and having that repo defined in settings.xml ?
>>> I think so, otherwise we won't achieve our objectives to have buildable
>>> sources at github.
>> Will it matter if we reference an internal repository in the sources?
>> (It won't be possible to build them trivially from outside the Red Hat
>> network.)
> In that case, that's why we used
> http://jboss-developer.github.io/temp-maven-repo/ as a staging maven repo.
>> Thanks,
>>
>> J
>>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


From benevides at redhat.com  Thu Nov 27 08:31:29 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Thu, 27 Nov 2014 11:31:29 -0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <5477264E.1040306@redhat.com>
References: <0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>	<5453C21D.5040203@redhat.com>	<CA+NJsVjcAYoXKQ5Y-s1X3MrA0Abrm45RchcVvcSEiSdL359V=A@mail.gmail.com>	<B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>	<547391C5.60106@redhat.com>	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>	<547468DC.3090906@redhat.com>	<5474D54F.6080204@redhat.com>	<20141127115029.GG2643@cyfynwy.redhat.com>	<547711F1.2040809@redhat.com>	<20141127120423.GJ2643@cyfynwy.redhat.com>
	<547715D5.9090109@redhat.com> <5477264E.1040306@redhat.com>
Message-ID: <547727B1.8020802@redhat.com>

It seems that staging repo is not being used anymore. I asked on another 
thread (you were copied) to review this process.

After the process is reviewed and clarified, we should update "JBoss 
Developer Materials Repository Management and Releases" MOJO [1] with 
those clarification points.

Anyway, adding and removing repos from pom.xml files is easy as running: 
mvn -U org.jboss.maven.plugins:qstools:repositories

[1] https://mojo.redhat.com/docs/DOC-928619

On 11/27/14 11:25, Sande Gilda wrote:
> I am a little confused by this discussion.
>
> Are we saying we will add the staging repo [1] to the development 
> branch POM files only and we then have to strip them from the product 
> branch POM files? I think it is going to be hard to maintain different 
> POM file contents in different branches.
>
> [1] http://jboss-developer.github.io/temp-maven-repo
>
> On 11/27/2014 07:15 AM, Rafael Benevides wrote:
>> On 11/27/14 10:04, Julian Coleman wrote:
>>> Hi,
>>>
>>>> I think that the staging repo is the answer here for testing purposes.
>>> I think that this makes sense too.  However, I'm not sure how we 
>>> will test
>>> the final version, as that will need a reference to the public 
>>> repository
>>> and be tested before the public repository contains the artifacts.
>> We use a different process that we have the final versions released
>> previously having the "-build-x" suffix at the version and place those
>> versions at http://jboss-developer.github.io/temp-maven-repo/ repo
>> (which is our "staging" repo until we have a nexus server setup). But I
>> know that this process is particular and couldn't fit for every project.
>> Do you see any restrictions to test the final version using the internal
>> repo and having that repo defined in settings.xml ?
>>>> I think so, otherwise we won't achieve our objectives to have 
>>>> buildable
>>>> sources at github.
>>> Will it matter if we reference an internal repository in the sources?
>>> (It won't be possible to build them trivially from outside the Red Hat
>>> network.)
>> In that case, that's why we used
>> http://jboss-developer.github.io/temp-maven-repo/ as a staging maven 
>> repo.
>>> Thanks,
>>>
>>> J
>>>
>> _______________________________________________
>> 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/20141127/48ccf40b/attachment-0001.html 

From jcoleman at redhat.com  Thu Nov 27 10:47:12 2014
From: jcoleman at redhat.com (Julian Coleman)
Date: Thu, 27 Nov 2014 15:47:12 +0000
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <547716DE.90902@redhat.com>
References: <B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>
	<547391C5.60106@redhat.com>
	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>
	<547468DC.3090906@redhat.com> <5474D54F.6080204@redhat.com>
	<20141127115029.GG2643@cyfynwy.redhat.com>
	<547711F1.2040809@redhat.com>
	<20141127120423.GJ2643@cyfynwy.redhat.com>
	<547715D5.9090109@redhat.com> <547716DE.90902@redhat.com>
Message-ID: <20141127154712.GS2643@cyfynwy.redhat.com>

Hi,

> Julian, I would suggest to use maven cli "-s" with settings to your
> staging repository. Do not inject that into quickstarts, repositories
> are injected ONLY for public end users. We are advanced users so we
> should use CLI with a specified settings.xml.

I was thinking more of how will the QE teams verify that things will work as
expected?  If the customers will run the quickstarts without specifying a
settings.xml file on the maven command line (or in JBoss Tools), then that
should be what is tested.  If the infrastructure at the time of testing isn't
the same as when the release is done, then how will QE verify (or automate
tests to verify) that the quickstarts are correct?

Thanks,

J

-- 
Red Hat
Newcastle upon Tyne

From mnovotny at redhat.com  Thu Nov 27 10:54:44 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Thu, 27 Nov 2014 16:54:44 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <20141127154712.GS2643@cyfynwy.redhat.com>
References: <B8115976-7FD1-468D-876B-590F91D66EAA@redhat.com>	<547391C5.60106@redhat.com>	<3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>	<547468DC.3090906@redhat.com>
	<5474D54F.6080204@redhat.com>	<20141127115029.GG2643@cyfynwy.redhat.com>	<547711F1.2040809@redhat.com>	<20141127120423.GJ2643@cyfynwy.redhat.com>	<547715D5.9090109@redhat.com>
	<547716DE.90902@redhat.com>
	<20141127154712.GS2643@cyfynwy.redhat.com>
Message-ID: <54774944.8000002@redhat.com>

On 27.11.2014 16:47, Julian Coleman wrote:
> Hi,
>
>> Julian, I would suggest to use maven cli "-s" with settings to your
>> staging repository. Do not inject that into quickstarts, repositories
>> are injected ONLY for public end users. We are advanced users so we
>> should use CLI with a specified settings.xml.
> I was thinking more of how will the QE teams verify that things will work as
> expected?  If the customers will run the quickstarts without specifying a
> settings.xml file on the maven command line (or in JBoss Tools), then that
> should be what is tested.  If the infrastructure at the time of testing isn't
> the same as when the release is done, then how will QE verify (or automate
> tests to verify) that the quickstarts are correct?
>
> Thanks,
>
> J
>
QE should verify the QS with Maven zipped repository files until we have
the staging and online Maven repository server by Nexus (yes, that is
coming - see Wolf project)

As we know that zip files are extracted in our current Tech preview
repository and later in staging and online supported repos. QE should
verify just that all GAVs from zip files are in online repository with
comparison to zipped Maven repository - that I think Karel Piwko and
John Casey produced some verification tool.

-- 
Marek Novotny
--
WFK and Seam Product Lead

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


From jcoleman at redhat.com  Thu Nov 27 11:22:04 2014
From: jcoleman at redhat.com (Julian Coleman)
Date: Thu, 27 Nov 2014 16:22:04 +0000
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <54774944.8000002@redhat.com>
References: <3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com>
	<547468DC.3090906@redhat.com> <5474D54F.6080204@redhat.com>
	<20141127115029.GG2643@cyfynwy.redhat.com>
	<547711F1.2040809@redhat.com>
	<20141127120423.GJ2643@cyfynwy.redhat.com>
	<547715D5.9090109@redhat.com> <547716DE.90902@redhat.com>
	<20141127154712.GS2643@cyfynwy.redhat.com>
	<54774944.8000002@redhat.com>
Message-ID: <20141127162204.GU2643@cyfynwy.redhat.com>

Hi,

> QE should verify the QS with Maven zipped repository files until we have
> the staging and online Maven repository server by Nexus (yes, that is
> coming - see Wolf project)

OK.

Thanks!

J

-- 
Red Hat
Newcastle upon Tyne