From benevides at redhat.com  Thu Oct 30 17:29:15 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Thu, 30 Oct 2014 19:29:15 -0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>
References: <53FB3100.4020501@redhat.com>
	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>
	<53FCC4E6.2060603@redhat.com> <53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
	<540EEA6D.9060108@redhat.com>
	<34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>
	<540EED2F.9080407@redhat.com>
	<5280B001-83D7-491D-AB9E-EAB7258D7E3C@redhat.com>
	<540F0995.9030201@redhat.com>
	<0A6DCC3F-CE9F-45F8-B474-9EE865F382A4! @redhat.com>
	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>
	<246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>
Message-ID: <5452ADAB.2060803@redhat.com>


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

Max,

What was the result of this subject in wolf call ?

Today I was helping Alexandre Porcelli from BRMS team to setup Ticket 
Monster as a demo. But as he had issues with unresolved dependencies and 
it seems that he have some restrictions to use the settings.xml file I'm 
bringing this subject again to be discussed.

Due to his short time to prepare the Demo, he will use Petclinic from 
Spring as he found that Ticket Monster is too tricky to build and run. 
Maybe he can give us more details/feedback but it was good to remember 
that we should improve our JBoss Developer Materials usability.

Thanks.

From max.andersen at redhat.com  Fri Oct 31 04:02:44 2014
From: max.andersen at redhat.com (Max Rydahl Andersen)
Date: Fri, 31 Oct 2014 09:02:44 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <5452ADAB.2060803@redhat.com>
References: <53FB3100.4020501@redhat.com>
	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>
	<53FCC4E6.2060603@redhat.com> <53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
	<540EEA6D.9060108@redhat.com>
	<34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>
	<540EED2F.9080407@redhat.com>
	<5280B001-83D7-491D-AB9E-EAB7258D7E3C@redhat.com>
	<540F0995.9030201@redhat.com>
	<0A6DCC3F-CE9F-45F8-B474-9EE865F382A4! @redhat.com>
	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>
	<246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>
	<5452ADAB.2060803@redhat.com>
Message-ID: <4A802246-C724-491F-8A4A-9480142A1B6A@redhat.com>

On 30 Oct 2014, at 22:29, Rafael Benevides wrote:

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

For now the split would stay, but we remove the /all grouping that was 
introduced by error (it was a neither or).

the final grouping says on line 110 on 
http://pad.engineering.redhat.com/wolf

"Pete and David to follow up offline, fix up mojo doc, and send to list 
for signoff."

I haven't seen this yet. Maybe I missed something while I was on PTO ?

> Today I was helping Alexandre Porcelli from BRMS team to setup Ticket 
> Monster as a demo. But as he had issues with unresolved dependencies 
> and it seems that he have some restrictions to use the settings.xml 
> file I'm bringing this subject again to be discussed.

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 ?

> Due to his short time to prepare the Demo, he will use Petclinic from 
> Spring as he found that Ticket Monster is too tricky to build and run. 
> Maybe he can give us more details/feedback but it was good to remember 
> that we should improve our JBoss Developer Materials usability.

Agreed.

/max
http://about.me/maxandersen

From mnovotny at redhat.com  Fri Oct 31 04:47:34 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Fri, 31 Oct 2014 09:47:34 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <4A802246-C724-491F-8A4A-9480142A1B6A@redhat.com>
References: <53FB3100.4020501@redhat.com> <53FCC4E6.2060603@redhat.com>
	<53FCF1A1.3000101@redhat.com> <53FCF46F.4010305@redhat.com>
	<53FCFBD2.1010005@redhat.com> <53FD97B0.6010201@redhat.com>
	<53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
	<540EEA6D.9060108@redhat.com>
	<34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>
	<540EED2F.9080407@redhat.com>
	<5280B001-83D7-491D-AB9E-EAB7258D7E3C@redhat.com>
	<540F0995.9030201@redhat.com>
	<0A6DCC3F-CE9F-45F8-B474-9EE865F382A4! @redhat.com>
	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>
	<246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>
	<5452ADAB.2060803@redhat.com>
	<4A802246-C724-491F-8A4A-9480142A1B6A@redhat.com>
Message-ID: <54534CA6.9050303@redhat.com>

On 31.10.2014 09:02, Max Rydahl Andersen wrote:
> On 30 Oct 2014, at 22:29, Rafael Benevides wrote:
>
>> On 9/22/14 10:54, Max Rydahl Andersen wrote:
>>> On 16 Sep 2014, at 11:56, Pete Muir wrote:
>>>
>>>> On 16 Sep 2014, at 00:27, Max Rydahl Andersen
>>>> <max.andersen at redhat.com> wrote:
>>>>
>>>>> On 9 Sep 2014, at 16:07, Rafael Benevides wrote:
>>>>>
>>>>>> We also need to check that with JBDS, because it's odd that
>>>>>> stacks only
>>>>>> uses "redhat-techpreview-all-repository" as additional repository.
>>>>>
>>>>> because it was the only thing we needed originally.
>>>>>
>>>>>> Max/Fred,
>>>>>>
>>>>>> Is there any issues having
>>>>>> https://maven.repository.redhat.com/earlyaccess/all/ as declared
>>>>>> inside
>>>>>> quickstarts pom.xml ?
>>>>>
>>>>> sorry - but I need to grok when earlyaccess/all is even needed 
>>>>> before answering that ? :)
>>>>>
>>>>> My default position would be that if you need earlyaccess you are
>>>>> expected to be able to understand why you need it.
>>>>>
>>>>> But i'm not sure if that is true anymore - hence wanting to ask
>>>>> why/when earlyaccess is ever needed ?
>>>>> is it for running quickstarts targeting a beta version of EAP ?
>>>>> (meaning no snapshots, but actual all releases in it?)
>>>>
>>>> Right, it?s where we put beta and alpha releases.
>>>>
>>>>>
>>>>> If yes, why doesn't /all get split up in /supported and
>>>>> /earlyaccess and /all will serve the combined result ?
>>>>
>>>> Propose this on the wolf list?
>>>
>>> Added as topic on tomorrows wolf call:
>>> http://pad.engineering.redhat.com/wolf
>>>
>>> /max
>>> /max
>>> http://about.me/maxandersen
>>
>> Max,
>>
>> What was the result of this subject in wolf call ?
>
> For now the split would stay, but we remove the /all grouping that was
> introduced by error (it was a neither or).
>
> the final grouping says on line 110 on
> http://pad.engineering.redhat.com/wolf
>
> "Pete and David to follow up offline, fix up mojo doc, and send to
> list for signoff."
>
> I haven't seen this yet. Maybe I missed something while I was on PTO ?
>
>> Today I was helping Alexandre Porcelli from BRMS team to setup Ticket
>> Monster as a demo. But as he had issues with unresolved dependencies
>> and it seems that he have some restrictions to use the settings.xml
>> file I'm bringing this subject again to be discussed.
>
> 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
from 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.


>
>> Due to his short time to prepare the Demo, he will use Petclinic from
>> Spring as he found that Ticket Monster is too tricky to build and
>> run. Maybe he can give us more details/feedback but it was good to
>> remember that we should improve our JBoss Developer Materials usability.
you should have the same result for jboss-wfk-quickstarts so I can't
believe it works and Timo doesn't.
>
> Agreed.
>
> /max
> http://about.me/maxandersen


-- 
Marek Novotny
--
WFK and Seam Product Lead

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




From vpereira at redhat.com  Fri Oct 31 07:57:46 2014
From: vpereira at redhat.com (Vineet Reynolds Pereira)
Date: Fri, 31 Oct 2014 07:57:46 -0400 (EDT)
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <54534CA6.9050303@redhat.com>
References: <53FB3100.4020501@redhat.com> <540F0995.9030201@redhat.com>
	<0A6DCC3F-CE9F-45F8-B474-9EE865F382A4!@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>
Message-ID: <1882962474.2957556.1414756666975.JavaMail.zimbra@redhat.com>



----- Original Message -----
> From: "Marek Novotny" <mnovotny at redhat.com>
> To: "Max Rydahl Andersen" <max.andersen at redhat.com>, "Rafael Benevides" <benevides at redhat.com>
> Cc: jbossdeveloper at lists.jboss.org, "Tomas Repel" <trepel at redhat.com>, "Nikoleta Ziakova" <nziakova at redhat.com>
> Sent: Friday, October 31, 2014 2:17:34 PM
> Subject: Re: [jbossdeveloper] <repository /> on quickstarts pom.xml
> 
> On 31.10.2014 09:02, Max Rydahl Andersen wrote:
> > On 30 Oct 2014, at 22:29, Rafael Benevides wrote:
> >
> >> On 9/22/14 10:54, Max Rydahl Andersen wrote:
> >>> On 16 Sep 2014, at 11:56, Pete Muir wrote:
> >>>
> >>>> On 16 Sep 2014, at 00:27, Max Rydahl Andersen
> >>>> <max.andersen at redhat.com> wrote:
> >>>>
> >>>>> On 9 Sep 2014, at 16:07, Rafael Benevides wrote:
> >>>>>
> >>>>>> We also need to check that with JBDS, because it's odd that
> >>>>>> stacks only
> >>>>>> uses "redhat-techpreview-all-repository" as additional repository.
> >>>>>
> >>>>> because it was the only thing we needed originally.
> >>>>>
> >>>>>> Max/Fred,
> >>>>>>
> >>>>>> Is there any issues having
> >>>>>> https://maven.repository.redhat.com/earlyaccess/all/ as declared
> >>>>>> inside
> >>>>>> quickstarts pom.xml ?
> >>>>>
> >>>>> sorry - but I need to grok when earlyaccess/all is even needed
> >>>>> before answering that ? :)
> >>>>>
> >>>>> My default position would be that if you need earlyaccess you are
> >>>>> expected to be able to understand why you need it.
> >>>>>
> >>>>> But i'm not sure if that is true anymore - hence wanting to ask
> >>>>> why/when earlyaccess is ever needed ?
> >>>>> is it for running quickstarts targeting a beta version of EAP ?
> >>>>> (meaning no snapshots, but actual all releases in it?)
> >>>>
> >>>> Right, it?s where we put beta and alpha releases.
> >>>>
> >>>>>
> >>>>> If yes, why doesn't /all get split up in /supported and
> >>>>> /earlyaccess and /all will serve the combined result ?
> >>>>
> >>>> Propose this on the wolf list?
> >>>
> >>> Added as topic on tomorrows wolf call:
> >>> http://pad.engineering.redhat.com/wolf
> >>>
> >>> /max
> >>> /max
> >>> http://about.me/maxandersen
> >>
> >> Max,
> >>
> >> What was the result of this subject in wolf call ?
> >
> > For now the split would stay, but we remove the /all grouping that was
> > introduced by error (it was a neither or).
> >
> > the final grouping says on line 110 on
> > http://pad.engineering.redhat.com/wolf
> >
> > "Pete and David to follow up offline, fix up mojo doc, and send to
> > list for signoff."
> >
> > I haven't seen this yet. Maybe I missed something while I was on PTO ?
> >
> >> Today I was helping Alexandre Porcelli from BRMS team to setup Ticket
> >> Monster as a demo. But as he had issues with unresolved dependencies
> >> and it seems that he have some restrictions to use the settings.xml
> >> file I'm bringing this subject again to be discussed.
> >
> > 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
> from 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.

I did verify 2.6.0.Final against techpreview/all not so long ago, and everything worked fine.
I do recall an issue I ran into several weeks ago, involving some ShrinkWrap dependency, but I can no longer reproduce it.

2.7.x-develop does require the EAP 6.3.1 and WFK 2.7.0 ER1 maven repos, so it wont work with techpreview/all at the moment.

> 
> 
> >
> >> Due to his short time to prepare the Demo, he will use Petclinic from
> >> Spring as he found that Ticket Monster is too tricky to build and
> >> run. Maybe he can give us more details/feedback but it was good to
> >> remember that we should improve our JBoss Developer Materials usability.
> you should have the same result for jboss-wfk-quickstarts so I can't
> believe it works and Timo doesn't.
> >
> > Agreed.
> >
> > /max
> > http://about.me/maxandersen
> 
> 
> --
> Marek Novotny
> --
> WFK and Seam Product Lead
> 
> Red Hat Czech s.r.o.
> Purkynova 99
> 612 45 Brno
> 
> 
> 
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


From pmuir at redhat.com  Fri Oct 31 08:52:05 2014
From: pmuir at redhat.com (Pete Muir)
Date: Fri, 31 Oct 2014 12:52:05 +0000
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <4A802246-C724-491F-8A4A-9480142A1B6A@redhat.com>
References: <53FB3100.4020501@redhat.com>
	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>
	<53FCC4E6.2060603@redhat.com> <53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
	<540EEA6D.9060108@redhat.com>
	<34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>
	<540EED2F.9080407@redhat.com>
	<5280B001-83D7-491D-AB9E-EAB7258D7E3C@redhat.com>
	<540F0995.9030201@redhat.com>
	<0A6DCC3F-CE9F-45F8-B474-9EE865F382A4! @redhat.com>
	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>
	<246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>
	<5452ADAB.2060803@redhat.com> <4A80!
	2246-C724-491F-8A4A-9480142A1B6A@redhat.com>
Message-ID: <BA8E9817-C0B8-4477-BFB9-5B74ACA2806E@redhat.com>


> On 31 Oct 2014, at 08:02, Max Rydahl Andersen <max.andersen at redhat.com> wrote:
> 
> On 30 Oct 2014, at 22:29, Rafael Benevides wrote:
> 
>> On 9/22/14 10:54, Max Rydahl Andersen wrote:
>>> On 16 Sep 2014, at 11:56, Pete Muir wrote:
>>> 
>>>> On 16 Sep 2014, at 00:27, Max Rydahl Andersen <max.andersen at redhat.com> wrote:
>>>> 
>>>>> On 9 Sep 2014, at 16:07, Rafael Benevides wrote:
>>>>> 
>>>>>> We also need to check that with JBDS, because it's odd that stacks only
>>>>>> uses "redhat-techpreview-all-repository" as additional repository.
>>>>> 
>>>>> because it was the only thing we needed originally.
>>>>> 
>>>>>> Max/Fred,
>>>>>> 
>>>>>> Is there any issues having
>>>>>> https://maven.repository.redhat.com/earlyaccess/all/ as declared inside
>>>>>> quickstarts pom.xml ?
>>>>> 
>>>>> sorry - but I need to grok when earlyaccess/all is even needed  before answering that ? :)
>>>>> 
>>>>> My default position would be that if you need earlyaccess you are expected to be able to understand why you need it.
>>>>> 
>>>>> But i'm not sure if that is true anymore - hence wanting to ask why/when earlyaccess is ever needed ?
>>>>> is it for running quickstarts targeting a beta version of EAP ? (meaning no snapshots, but actual all releases in it?)
>>>> 
>>>> Right, it?s where we put beta and alpha releases.
>>>> 
>>>>> 
>>>>> If yes, why doesn't /all get split up in /supported and /earlyaccess and /all will serve the combined result ?
>>>> 
>>>> Propose this on the wolf list?
>>> 
>>> Added as topic on tomorrows wolf call: http://pad.engineering.redhat.com/wolf
>>> 
>>> /max
>>> /max
>>> http://about.me/maxandersen
>> 
>> Max,
>> 
>> What was the result of this subject in wolf call ?
> 
> For now the split would stay, but we remove the /all grouping that was introduced by error (it was a neither or).
> 
> the final grouping says on line 110 on http://pad.engineering.redhat.com/wolf
> 
> "Pete and David to follow up offline, fix up mojo doc, and send to list for signoff."
> 
> I haven't seen this yet. Maybe I missed something while I was on PTO ?

See David?s email on 26th Sept entitled "[Wolf] /everything folder? - you replied to it on the 1st Oct that reviewing the doc was on your todo list.

> 
>> Today I was helping Alexandre Porcelli from BRMS team to setup Ticket Monster as a demo. But as he had issues with unresolved dependencies and it seems that he have some restrictions to use the settings.xml file I'm bringing this subject again to be discussed.
> 
> 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 ?
> 
>> Due to his short time to prepare the Demo, he will use Petclinic from Spring as he found that Ticket Monster is too tricky to build and run. Maybe he can give us more details/feedback but it was good to remember that we should improve our JBoss Developer Materials usability.
> 
> Agreed.
> 
> /max
> http://about.me/maxandersen

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

From benevides at redhat.com  Fri Oct 31 08:58:40 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 31 Oct 2014 10:58:40 -0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <54534CA6.9050303@redhat.com>
References: <53FB3100.4020501@redhat.com> <53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
	<540EEA6D.9060108@redhat.com>
	<34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>
	<540EED2F.9080407@redhat.com>
	<5280B001-83D7-491D-AB9E-EAB7258D7E3C@redhat.com>
	<540F0995.9030201@redhat.com>
	<0A6DCC3F-CE9F-45F8-B474-9EE865F382A4! @redhat.com>
	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>
	<246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>
	<5452ADAB.2060803@redhat.com>
	<4A802246-C724-491F-8A4A-9480142A1B6A@redhat.com>
	<54534CA6.9050303@redhat.com>
Message-ID: <54538780.5070509@redhat.com>

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

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


From mnovotny at redhat.com  Fri Oct 31 09:13:21 2014
From: mnovotny at redhat.com (Marek Novotny)
Date: Fri, 31 Oct 2014 14:13:21 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <54538780.5070509@redhat.com>
References: <53FB3100.4020501@redhat.com> <53FCF46F.4010305@redhat.com>
	<53FCFBD2.1010005@redhat.com> <53FD97B0.6010201@redhat.com>
	<53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
	<540EEA6D.9060108@redhat.com>
	<34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>
	<540EED2F.9080407@redhat.com>
	<5280B001-83D7-491D-AB9E-EAB7258D7E3C@redhat.com>
	<540F0995.9030201@redhat.com>
	<0A6DCC3F-CE9F-45F8-B474-9EE865F382A4! @redhat.com>
	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>
	<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>
Message-ID: <54538AF1.1080805@redhat.com>

On 31.10.2014 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.
ok, so what's wrong with clone, build and rung it with '-s settings.xml'
or just 'cp settings.xml to $home_dir/.m2/' ?

I would expect that education from JBoss developer showing a demo is
good thing. That should work before we add the repository into QS
pom.xml files ;)
>
> If I'm not wrong, this discussion started with similar issues in this
> Arun Gupta Twitter thread:
> https://twitter.com/arungupta/status/502854638832730112
>
> 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.
>>
>>
>


-- 
Marek Novotny
--
WFK and Seam Product Lead

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


From max.andersen at redhat.com  Fri Oct 31 09:22:07 2014
From: max.andersen at redhat.com (Max Rydahl Andersen)
Date: Fri, 31 Oct 2014 14:22:07 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <BA8E9817-C0B8-4477-BFB9-5B74ACA2806E@redhat.com>
References: <53FB3100.4020501@redhat.com>
	<4BDCA068-CA85-462B-877C-1D17783CE062@redhat.com>
	<53FCC4E6.2060603@redhat.com> <53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
	<540EEA6D.9060108@redhat.com>
	<34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>
	<540EED2F.9080407@redhat.com>
	<5280B001-83D7-491D-AB9E-EAB7258D7E3C@redhat.com>
	<540F0995.9030201@redhat.com>
	<0A6DCC3F-CE9F-45F8-B474-9EE865F382A4! @redhat.com>
	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>
	<246AF4BC-2A9F-45CF-ACF0-3362E23E24A3@redhat.com>
	<5452ADAB.2060803@redhat.com>
	<4A80! 2246-C724-491F-8A4A-9480142A1B6A@redhat.com>
	<BA8E9817-C0B8-4477-BFB9-5B74ACA2806E@redhat.com>
Message-ID: <F01A4ED4-ED7A-4ACB-BF30-E02ED76F6BF1@redhat.com>

On 31 Oct 2014, at 13:52, Pete Muir wrote:

> "Pete and David to follow up offline, fix up mojo doc, and send to 
> list for signoff."
>>
>> I haven't seen this yet. Maybe I missed something while I was on PTO 
>> ?
>
>
>
> See David?s email on 26th Sept entitled "[Wolf] /everything 
> folder? - you replied to?it on the 1st Oct that reviewing the doc 
> was on your todo list.

burn ;)

back on my todo list it goes!

/max
http://about.me/maxandersen

From max.andersen at redhat.com  Fri Oct 31 09:23:43 2014
From: max.andersen at redhat.com (Max Rydahl Andersen)
Date: Fri, 31 Oct 2014 14:23:43 +0100
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <54538780.5070509@redhat.com>
References: <53FB3100.4020501@redhat.com> <53FCF1A1.3000101@redhat.com>
	<53FCF46F.4010305@redhat.com> <53FCFBD2.1010005@redhat.com>
	<53FD97B0.6010201@redhat.com> <53FDC684.1010203@redhat.com>
	<4EF72F0E-8303-490E-B700-00F4ABF91857@redhat.com>
	<81E7B52E-11F2-4E20-BB3F-43C534787F7B@redhat.com>
	<540DD06D.2090806@redhat.com>
	<E582C25C-B6FE-4D75-80AF-4823496F360A@redhat.com>
	<540DDD1F.5020206@redhat.com>
	<ACC201C4-C0F6-4080-8A40-15201CBF9872@redhat.com>
	<540ED7E0.2000303@redhat.com>
	<B518CF2A-1ACD-479C-8E64-B686BFC35E93@redhat.com>
	<540EEA6D.9060108@redhat.com>
	<34E0E2AC-0776-43D0-B684-5A3AF8E1B66A@redhat.com>
	<540EED2F.9080407@redhat.com>
	<5280B001-83D7-491D-AB9E-EAB7258D7E3C@redhat.com>
	<540F0995.9030201@redhat.com>
	<0A6DCC3F-CE9F-45F8-B474-9EE865F382A4! @redhat.com>
	<A685863C-8A65-49E2-A88D-EAD711333335@redhat.com>
	<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>
Message-ID: <B20848FF-2F53-4AF6-9C8D-3E8CF25A1D96@redhat.com>

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 ?

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

From vpereira at redhat.com  Fri Oct 31 09:34:10 2014
From: vpereira at redhat.com (Vineet Reynolds Pereira)
Date: Fri, 31 Oct 2014 09:34:10 -0400 (EDT)
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <B20848FF-2F53-4AF6-9C8D-3E8CF25A1D96@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>
Message-ID: <1753895673.3004550.1414762450254.JavaMail.zimbra@redhat.com>



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

From benevides at redhat.com  Fri Oct 31 09:56:17 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 31 Oct 2014 11:56:17 -0200
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
Message-ID: <54539501.8030609@redhat.com>

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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141031/5b2dba61/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: {a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141031/5b2dba61/attachment-0001.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linkedin.png
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141031/5b2dba61/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: youtube.png
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141031/5b2dba61/attachment-0003.png 

From fbricon at redhat.com  Fri Oct 31 11:08:28 2014
From: fbricon at redhat.com (Fred Bricon)
Date: Fri, 31 Oct 2014 11:08:28 -0400
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <1753895673.3004550.1414762450254.JavaMail.zimbra@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>
Message-ID: <382B9D50-1E63-44C7-A21D-5638CDB6DB18@redhat.com>


> Le 31 oct. 2014 ? 09:34, Vineet Reynolds Pereira <vpereira at redhat.com> a ?crit :
> 
> 
> 
> ----- 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 <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.

+1
In JBT/JBDS, if you ctrl+space in the <repositories> section of a pom.xml, you?ll see templates to add JBoss/Red Hat repo definitions. This is what we add then :

    <!-- You should seriously consider using a repository manager or declare repositories in your settings.xml.
              See http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/   -->
     <repository>
        <!-- The JBoss Public repository is a composite repository of several major repositories. 
              See http://community.jboss.org/wiki/MavenGettingStarted-Users -->
        <id>jboss-public-repository</id>
        <url>http://repository.jboss.org/nexus/content/groups/public</url>
        <releases>
           <enabled>true</enabled>
        </releases>
        <!-- You can disable snapshot resolution to speed up your builds -->
        <snapshots>
          <enabled>true</enabled>
        </snapshots>        
     </repository>


> 
>> 
>> 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 <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/20141031/751f844c/attachment.html 

From pmuir at redhat.com  Fri Oct 31 11:16:18 2014
From: pmuir at redhat.com (Pete Muir)
Date: Fri, 31 Oct 2014 15:16:18 +0000
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: <1161C920-6DD4-46CD-97BA-D7EDEDCE1259@redhat.com>

Sounds good to me

> On 31 Oct 2014, at 13:56, Rafael Benevides <benevides at redhat.com> 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
> 
> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
> 
> Better technology. Faster innovation. Powered by community collaboration. 
> See how it works at www.redhat.com <http://www.redhat.com/> 
> 
> <linkedin.png> <http://www.linkedin.com/company/3258288> <youtube.png> <https://www.youtube.com/redhatlatam>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141031/569bbd74/attachment-0001.html 

From gdesmet at redhat.com  Fri Oct 31 11:20:03 2014
From: gdesmet at redhat.com (Geoffrey De Smet)
Date: Fri, 31 Oct 2014 16:20:03 +0100
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <1161C920-6DD4-46CD-97BA-D7EDEDCE1259@redhat.com>
References: <54539501.8030609@redhat.com>
	<1161C920-6DD4-46CD-97BA-D7EDEDCE1259@redhat.com>
Message-ID: <5453A8A3.7080800@redhat.com>

An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141031/0c1b28f4/attachment.html 

From manderse at redhat.com  Fri Oct 31 11:44:06 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 31 Oct 2014 11:44:06 -0400 (EDT)
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <1753895673.3004550.1414762450254.JavaMail.zimbra@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>
Message-ID: <638CC3E7-0036-4EF4-9C91-9F9F82DD805B@redhat.com>

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


From vpereira at redhat.com  Fri Oct 31 12:33:12 2014
From: vpereira at redhat.com (Vineet Reynolds Pereira)
Date: Fri, 31 Oct 2014 12:33:12 -0400 (EDT)
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <638CC3E7-0036-4EF4-9C91-9F9F82DD805B@redhat.com>
References: <53FB3100.4020501@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>
Message-ID: <1785776671.3146435.1414773192370.JavaMail.zimbra@redhat.com>



----- Original Message -----
> From: "Max Rydahl Andersen" <manderse at redhat.com>
> To: "Vineet Reynolds Pereira" <vpereira at redhat.com>
> Cc: "Max Rydahl Andersen" <max.andersen at redhat.com>, "Tomas Repel" <trepel at redhat.com>,
> jbossdeveloper at lists.jboss.org, "Alexandre Porcelli" <alexandre.porcelli at gmail.com>, "Nikoleta Ziakova"
> <nziakova at redhat.com>
> Sent: Friday, October 31, 2014 9:14:06 PM
> Subject: Re: [jbossdeveloper] <repository /> on quickstarts pom.xml
> 
> Didn't we do inject of these when Productization built them ?

I don't recall this ever being done. I've looked at the zips that we instruct users to download, as well as the ones QE signs off on. 

Rafael, correct me if I'm wrong.

> 
> Or was this only done for the archetypes ?

Doubtful we do it for archetypes. I verified this last week on JBDS 8 GA, and I've thus added instructions for users to follow in the introduction chapter of TiMo.

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

From kbabo at redhat.com  Fri Oct 31 11:48:47 2014
From: kbabo at redhat.com (Keith Babo)
Date: Fri, 31 Oct 2014 11:48:47 -0400
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: <7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>


Hey - this caught me a bit by surprise.  I thought that the JDF approach was to externalize repository definitions from the pom.xml and reference them via an external settings.xml.  I ask because we have traditionally included repo definitions in SY quickstarts.

thanks,
keith

On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com> 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
> 
> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
> 
> Better technology. Faster innovation. Powered by community collaboration. 
> See how it works at www.redhat.com 
> 
> <linkedin.png> <youtube.png>

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

From pmuir at redhat.com  Fri Oct 31 12:39:49 2014
From: pmuir at redhat.com (Pete Muir)
Date: Fri, 31 Oct 2014 16:39:49 +0000
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
Message-ID: <68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>

We?re switching back :-/

> On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com> wrote:
> 
> 
> Hey - this caught me a bit by surprise.  I thought that the JDF approach was to externalize repository definitions from the pom.xml and reference them via an external settings.xml.  I ask because we have traditionally included repo definitions in SY quickstarts.
> 
> thanks,
> keith
> 
> On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com <mailto:benevides at redhat.com>> 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
>> 
>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>> 
>> Better technology. Faster innovation. Powered by community collaboration. 
>> See how it works at www.redhat.com <http://www.redhat.com/> 
>> 
>> <linkedin.png> <http://www.linkedin.com/company/3258288> <youtube.png> <https://www.youtube.com/redhatlatam>

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

From benevides at redhat.com  Fri Oct 31 12:50:19 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 31 Oct 2014 14:50:19 -0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <638CC3E7-0036-4EF4-9C91-9F9F82DD805B@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>
Message-ID: <5453BDCB.1060104@redhat.com>

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


From sgilda at redhat.com  Fri Oct 31 12:49:19 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 31 Oct 2014 12:49:19 -0400
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
Message-ID: <5453BD8F.4080206@redhat.com>

Which reminds me. Should I remove the 3rd paragraph (see below) from 
this topic [1] in the JBoss EAP 6.4 Development Guide?

    This method of configuration is generally not recommended. If you
    decide to configure repositories in your project POM file, plan
    carefully and be aware that it can slow down your build and you may
    even end up with artifacts that are not from the expected repository.

[1] 
https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#Configure_the_JBoss_Enterprise_Application_Platform_Maven_Repository_Using_the_Project_POM


On 10/31/2014 12:39 PM, Pete Muir wrote:
> We?re switching back :-/
>
>> On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com 
>> <mailto:kbabo at redhat.com>> wrote:
>>
>>
>> Hey - this caught me a bit by surprise.  I thought that the JDF 
>> approach was to externalize repository definitions from the pom.xml 
>> and reference them via an external settings.xml.  I ask because we 
>> have traditionally included repo definitions in SY quickstarts.
>>
>> thanks,
>> keith
>>
>> On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com 
>> <mailto:benevides at redhat.com>> 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
>>>
>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>
>>> Better technology. Faster innovation. Powered by community 
>>> collaboration.
>>> See how it works at www.redhat.com <http://www.redhat.com/>
>>>
>>> <linkedin.png> <http://www.linkedin.com/company/3258288> 
>>> <youtube.png> <https://www.youtube.com/redhatlatam>
>>
>

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

From pmuir at redhat.com  Fri Oct 31 12:51:23 2014
From: pmuir at redhat.com (Pete Muir)
Date: Fri, 31 Oct 2014 16:51:23 +0000
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <5453BD8F.4080206@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
	<5453BD8F.4080206@redhat.com>
Message-ID: <E2455756-B8F0-43C8-B92D-04B762ECFB04@redhat.com>

No, it?s still not the recommend approach for real projects.

> On 31 Oct 2014, at 16:49, Sande Gilda <sgilda at redhat.com> wrote:
> 
> Which reminds me. Should I remove the 3rd paragraph (see below) from this topic [1] in the JBoss EAP 6.4 Development Guide?
> This method of configuration is generally not recommended. If you decide to configure repositories in your project POM file, plan carefully and be aware that it can slow down your build and you may even end up with artifacts that are not from the expected repository. 
> [1] https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#Configure_the_JBoss_Enterprise_Application_Platform_Maven_Repository_Using_the_Project_POM <https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#Configure_the_JBoss_Enterprise_Application_Platform_Maven_Repository_Using_the_Project_POM>
> 
> 
> On 10/31/2014 12:39 PM, Pete Muir wrote:
>> We?re switching back :-/
>> 
>>> On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com <mailto:kbabo at redhat.com>> wrote:
>>> 
>>> 
>>> Hey - this caught me a bit by surprise.  I thought that the JDF approach was to externalize repository definitions from the pom.xml and reference them via an external settings.xml.  I ask because we have traditionally included repo definitions in SY quickstarts.
>>> 
>>> thanks,
>>> keith
>>> 
>>> On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com <mailto:benevides at redhat.com>> 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
>>>> 
>>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>> 
>>>> Better technology. Faster innovation. Powered by community collaboration. 
>>>> See how it works at www.redhat.com <http://www.redhat.com/> 
>>>> 
>>>> <linkedin.png> <http://www.linkedin.com/company/3258288> <youtube.png> <https://www.youtube.com/redhatlatam>
>> 
> 

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

From benevides at redhat.com  Fri Oct 31 12:52:10 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 31 Oct 2014 14:52:10 -0200
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <5453BD8F.4080206@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
	<5453BD8F.4080206@redhat.com>
Message-ID: <5453BE3A.6040704@redhat.com>

Sande,

I think you can do it, after we "inject" the repository definition at 
the pom.xml sources. I'm not sure if we will be able to do that until 
6.4 release. (I'm not aware about the release schedule)

On 10/31/14 14:49, Sande Gilda wrote:
> Which reminds me. Should I remove the 3rd paragraph (see below) from 
> this topic [1] in the JBoss EAP 6.4 Development Guide?
>
>     This method of configuration is generally not recommended. If you
>     decide to configure repositories in your project POM file, plan
>     carefully and be aware that it can slow down your build and you
>     may even end up with artifacts that are not from the expected
>     repository.
>
> [1] 
> https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#Configure_the_JBoss_Enterprise_Application_Platform_Maven_Repository_Using_the_Project_POM
>
>
> On 10/31/2014 12:39 PM, Pete Muir wrote:
>> We?re switching back :-/
>>
>>> On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com 
>>> <mailto:kbabo at redhat.com>> wrote:
>>>
>>>
>>> Hey - this caught me a bit by surprise.  I thought that the JDF 
>>> approach was to externalize repository definitions from the pom.xml 
>>> and reference them via an external settings.xml.  I ask because we 
>>> have traditionally included repo definitions in SY quickstarts.
>>>
>>> thanks,
>>> keith
>>>
>>> On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com 
>>> <mailto:benevides at redhat.com>> 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
>>>>
>>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>>
>>>> Better technology. Faster innovation. Powered by community 
>>>> collaboration.
>>>> See how it works at www.redhat.com <http://www.redhat.com/>
>>>>
>>>> <linkedin.png> <http://www.linkedin.com/company/3258288> 
>>>> <youtube.png> <https://www.youtube.com/redhatlatam>
>>>
>>
>

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

From benevides at redhat.com  Fri Oct 31 12:53:56 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 31 Oct 2014 14:53:56 -0200
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <E2455756-B8F0-43C8-B92D-04B762ECFB04@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
	<5453BD8F.4080206@redhat.com>
	<E2455756-B8F0-43C8-B92D-04B762ECFB04@redhat.com>
Message-ID: <5453BEA4.7070306@redhat.com>

Thanks Pete,

I thought that part of documentation was applied to Quickstarts only.

Sande,

Sorry. As Pete said, in general we still no recommending that.

On 10/31/14 14:51, Pete Muir wrote:
> No, it?s still not the recommend approach for real projects.
>
>> On 31 Oct 2014, at 16:49, Sande Gilda <sgilda at redhat.com 
>> <mailto:sgilda at redhat.com>> wrote:
>>
>> Which reminds me. Should I remove the 3rd paragraph (see below) from 
>> this topic [1] in the JBoss EAP 6.4 Development Guide?
>>
>>     This method of configuration is generally not recommended. If you
>>     decide to configure repositories in your project POM file, plan
>>     carefully and be aware that it can slow down your build and you
>>     may even end up with artifacts that are not from the expected
>>     repository.
>>
>> [1] 
>> https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#Configure_the_JBoss_Enterprise_Application_Platform_Maven_Repository_Using_the_Project_POM
>>
>>
>> On 10/31/2014 12:39 PM, Pete Muir wrote:
>>> We?re switching back :-/
>>>
>>>> On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com 
>>>> <mailto:kbabo at redhat.com>> wrote:
>>>>
>>>>
>>>> Hey - this caught me a bit by surprise.  I thought that the JDF 
>>>> approach was to externalize repository definitions from the pom.xml 
>>>> and reference them via an external settings.xml.  I ask because we 
>>>> have traditionally included repo definitions in SY quickstarts.
>>>>
>>>> thanks,
>>>> keith
>>>>
>>>> On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com 
>>>> <mailto:benevides at redhat.com>> 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
>>>>>
>>>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>>>
>>>>> Better technology. Faster innovation. Powered by community 
>>>>> collaboration.
>>>>> See how it works at www.redhat.com <http://www.redhat.com/>
>>>>>
>>>>> <linkedin.png> <http://www.linkedin.com/company/3258288> 
>>>>> <youtube.png> <https://www.youtube.com/redhatlatam>
>>>>
>>>
>>
>

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

From sgilda at redhat.com  Fri Oct 31 12:56:08 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 31 Oct 2014 12:56:08 -0400
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <E2455756-B8F0-43C8-B92D-04B762ECFB04@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
	<5453BD8F.4080206@redhat.com>
	<E2455756-B8F0-43C8-B92D-04B762ECFB04@redhat.com>
Message-ID: <5453BF28.5080901@redhat.com>

Then maybe I should add a note to the README to that effect also, since 
we are presumed to be using best practices?

When is this change scheduled to happen?

On 10/31/2014 12:51 PM, Pete Muir wrote:
> No, it?s still not the recommend approach for real projects.
>
>> On 31 Oct 2014, at 16:49, Sande Gilda <sgilda at redhat.com 
>> <mailto:sgilda at redhat.com>> wrote:
>>
>> Which reminds me. Should I remove the 3rd paragraph (see below) from 
>> this topic [1] in the JBoss EAP 6.4 Development Guide?
>>
>>     This method of configuration is generally not recommended. If you
>>     decide to configure repositories in your project POM file, plan
>>     carefully and be aware that it can slow down your build and you
>>     may even end up with artifacts that are not from the expected
>>     repository.
>>
>> [1] 
>> https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#Configure_the_JBoss_Enterprise_Application_Platform_Maven_Repository_Using_the_Project_POM
>>
>>
>> On 10/31/2014 12:39 PM, Pete Muir wrote:
>>> We?re switching back :-/
>>>
>>>> On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com 
>>>> <mailto:kbabo at redhat.com>> wrote:
>>>>
>>>>
>>>> Hey - this caught me a bit by surprise.  I thought that the JDF 
>>>> approach was to externalize repository definitions from the pom.xml 
>>>> and reference them via an external settings.xml.  I ask because we 
>>>> have traditionally included repo definitions in SY quickstarts.
>>>>
>>>> thanks,
>>>> keith
>>>>
>>>> On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com 
>>>> <mailto:benevides at redhat.com>> 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
>>>>>
>>>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>>>
>>>>> Better technology. Faster innovation. Powered by community 
>>>>> collaboration.
>>>>> See how it works at www.redhat.com <http://www.redhat.com/>
>>>>>
>>>>> <linkedin.png> <http://www.linkedin.com/company/3258288> 
>>>>> <youtube.png> <https://www.youtube.com/redhatlatam>
>>>>
>>>
>>
>

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

From pmuir at redhat.com  Fri Oct 31 12:57:38 2014
From: pmuir at redhat.com (Pete Muir)
Date: Fri, 31 Oct 2014 16:57:38 +0000
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <5453BF28.5080901@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
	<5453BD8F.4080206@redhat.com>
	<E2455756-B8F0-43C8-B92D-04B762ECFB04@redhat.com>
	<5453BF28.5080901@redhat.com>
Message-ID: <9358BDDC-BE78-4999-A42D-91A71510CC0E@redhat.com>

Sounds like a good idea.

> On 31 Oct 2014, at 16:56, Sande Gilda <sgilda at redhat.com> wrote:
> 
> Then maybe I should add a note to the README to that effect also, since we are presumed to be using best practices?
> 
> When is this change scheduled to happen?
> 
> On 10/31/2014 12:51 PM, Pete Muir wrote:
>> No, it?s still not the recommend approach for real projects.
>> 
>>> On 31 Oct 2014, at 16:49, Sande Gilda <sgilda at redhat.com <mailto:sgilda at redhat.com>> wrote:
>>> 
>>> Which reminds me. Should I remove the 3rd paragraph (see below) from this topic [1] in the JBoss EAP 6.4 Development Guide?
>>> This method of configuration is generally not recommended. If you decide to configure repositories in your project POM file, plan carefully and be aware that it can slow down your build and you may even end up with artifacts that are not from the expected repository. 
>>> [1] https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#Configure_the_JBoss_Enterprise_Application_Platform_Maven_Repository_Using_the_Project_POM <https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#Configure_the_JBoss_Enterprise_Application_Platform_Maven_Repository_Using_the_Project_POM>
>>> 
>>> 
>>> On 10/31/2014 12:39 PM, Pete Muir wrote:
>>>> We?re switching back :-/
>>>> 
>>>>> On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com <mailto:kbabo at redhat.com>> wrote:
>>>>> 
>>>>> 
>>>>> Hey - this caught me a bit by surprise.  I thought that the JDF approach was to externalize repository definitions from the pom.xml and reference them via an external settings.xml.  I ask because we have traditionally included repo definitions in SY quickstarts.
>>>>> 
>>>>> thanks,
>>>>> keith
>>>>> 
>>>>> On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com <mailto:benevides at redhat.com>> 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
>>>>>> 
>>>>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>>>> 
>>>>>> Better technology. Faster innovation. Powered by community collaboration. 
>>>>>> See how it works at www.redhat.com <http://www.redhat.com/> 
>>>>>> 
>>>>>> <linkedin.png> <http://www.linkedin.com/company/3258288> <youtube.png> <https://www.youtube.com/redhatlatam>
>>>> 
>>> 
>> 
> 

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

From manderse at redhat.com  Fri Oct 31 13:07:09 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 31 Oct 2014 13:07:09 -0400 (EDT)
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <5453BDCB.1060104@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>
Message-ID: <0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com>

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
> 


From benevides at redhat.com  Fri Oct 31 13:08:45 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 31 Oct 2014 15:08:45 -0200
Subject: [jbossdeveloper] <repository /> on quickstarts pom.xml
In-Reply-To: <0FDD180A-039B-4D66-9B8F-A54DB12F627D@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>
Message-ID: <5453C21D.5040203@redhat.com>

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


From rcernich at redhat.com  Fri Oct 31 14:03:24 2014
From: rcernich at redhat.com (Rob Cernich)
Date: Fri, 31 Oct 2014 14:03:24 -0400 (EDT)
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
Message-ID: <779531216.3192423.1414778604873.JavaMail.zimbra@redhat.com>

So does that mean we can/should put the repository definitions back into the quickstart poms? 

----- Original Message -----

> We?re switching back :-/

> > On 31 Oct 2014, at 15:48, Keith Babo < kbabo at redhat.com > wrote:
> 

> > Hey - this caught me a bit by surprise. I thought that the JDF approach was
> > to externalize repository definitions from the pom.xml and reference them
> > via an external settings.xml. I ask because we have traditionally included
> > repo definitions in SY quickstarts.
> 

> > thanks,
> 
> > keith
> 

> > On Oct 31, 2014, at 9:56 AM, Rafael Benevides < benevides at redhat.com >
> > 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
> > 
> 

> > > <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
> > 
> 

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

> > > <linkedin.png> <youtube.png>
> > 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141031/77e9600b/attachment-0001.html 

From kbabo at redhat.com  Fri Oct 31 14:06:13 2014
From: kbabo at redhat.com (Keith Babo)
Date: Fri, 31 Oct 2014 14:06:13 -0400
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <779531216.3192423.1414778604873.JavaMail.zimbra@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
	<779531216.3192423.1414778604873.JavaMail.zimbra@redhat.com>
Message-ID: <053D9F52-B08D-4CE2-A13B-B35F5828B92A@redhat.com>


Sounds like this tool can take care of updating the repository refs to whatever JDF wants, so yeah, I think it would be good to have them in the project quickstarts.  

On Oct 31, 2014, at 2:03 PM, Rob Cernich <rcernich at redhat.com> wrote:

> So does that mean we can/should put the repository definitions back into the quickstart poms?
> 
> We?re switching back :-/
> 
> On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com> wrote:
> 
> 
> Hey - this caught me a bit by surprise.  I thought that the JDF approach was to externalize repository definitions from the pom.xml and reference them via an external settings.xml.  I ask because we have traditionally included repo definitions in SY quickstarts.
> 
> thanks,
> keith
> 
> On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com> 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
> 
> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
> 
> Better technology. Faster innovation. Powered by community collaboration. 
> See how it works at www.redhat.com 
> 
> <linkedin.png> <youtube.png>
> 
> 
> 

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

From benevides at redhat.com  Fri Oct 31 14:06:26 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 31 Oct 2014 16:06:26 -0200
Subject: [jbossdeveloper] <repository /> definition in pom.xml for
	Quickstarts and Demos
In-Reply-To: <779531216.3192423.1414778604873.JavaMail.zimbra@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
	<779531216.3192423.1414778604873.JavaMail.zimbra@redhat.com>
Message-ID: <5453CFA2.1060009@redhat.com>

Yeap.

I'm preparing QSTools to do that for us, using the approved Ids.

On 10/31/14 16:03, Rob Cernich wrote:
> So does that mean we can/should put the repository definitions back 
> into the quickstart poms?
>
> ------------------------------------------------------------------------
>
>     We?re switching back :-/
>
>         On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com
>         <mailto:kbabo at redhat.com>> wrote:
>
>
>         Hey - this caught me a bit by surprise.  I thought that the
>         JDF approach was to externalize repository definitions from
>         the pom.xml and reference them via an external settings.xml.
>          I ask because we have traditionally included repo definitions
>         in SY quickstarts.
>
>         thanks,
>         keith
>
>         On Oct 31, 2014, at 9:56 AM, Rafael Benevides
>         <benevides at redhat.com <mailto:benevides at redhat.com>> 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
>
>             <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>
>             Better technology. Faster innovation. Powered by community
>             collaboration.
>             See how it works at www.redhat.com <http://www.redhat.com/>
>
>             <linkedin.png> <http://www.linkedin.com/company/3258288>
>             <youtube.png> <https://www.youtube.com/redhatlatam>
>
>
>
>

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

From manderse at redhat.com  Fri Oct 31 15:51:57 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 31 Oct 2014 15:51:57 -0400 (EDT)
Subject: [jbossdeveloper] <repository /> definition in pom.xml
	for	Quickstarts and Demos
In-Reply-To: <5453BE3A.6040704@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
	<5453BD8F.4080206@redhat.com> <5453BE3A.6040704@redhat.com>
Message-ID: <5E02ED75-0B95-48DE-B512-212267CA4965@redhat.com>

This warning is still relevant no matter if we include it or not. 

/max
http://about.me/maxandersen


> On 31 Oct 2014, at 17:54, Rafael Benevides <benevides at redhat.com> wrote:
> 
> Sande,
> 
> I think you can do it, after we "inject" the repository definition at the pom.xml sources. I'm not sure if we will be able to do that until 6.4 release. (I'm not aware about the release schedule)
> 
>> On 10/31/14 14:49, Sande Gilda wrote:
>> Which reminds me. Should I remove the 3rd paragraph (see below) from this topic [1] in the JBoss EAP 6.4 Development Guide?
>> This method of configuration is generally not recommended. If you decide to configure repositories in your project POM file, plan carefully and be aware that it can slow down your build and you may even end up with artifacts that are not from the expected repository. 
>> [1] https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#Configure_the_JBoss_Enterprise_Application_Platform_Maven_Repository_Using_the_Project_POM
>> 
>> 
>>> On 10/31/2014 12:39 PM, Pete Muir wrote:
>>> We?re switching back :-/
>>> 
>>>> On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com> wrote:
>>>> 
>>>> 
>>>> Hey - this caught me a bit by surprise.  I thought that the JDF approach was to externalize repository definitions from the pom.xml and reference them via an external settings.xml.  I ask because we have traditionally included repo definitions in SY quickstarts.
>>>> 
>>>> thanks,
>>>> keith
>>>> 
>>>>> On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com>                        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
>>>>> 
>>>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>>> 
>>>>> Better technology. Faster innovation. Powered by community collaboration. 
>>>>> See how it works at www.redhat.com 
>>>>> 
>>>>> <linkedin.png> <youtube.png>
> 
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141031/55d63180/attachment-0001.html 

From manderse at redhat.com  Fri Oct 31 15:53:30 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 31 Oct 2014 15:53:30 -0400 (EDT)
Subject: [jbossdeveloper] <repository /> definition in pom.xml
	for	Quickstarts and Demos
In-Reply-To: <5453CFA2.1060009@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
	<779531216.3192423.1414778604873.JavaMail.zimbra@redhat.com>
	<5453CFA2.1060009@redhat.com>
Message-ID: <5BF3A11B-F227-4D81-9B77-36F2033DC8AC@redhat.com>

Yeah. Just to cover bases. The projects we generate for users shouldn't have it though. Here better to use our built in support for helping adding to settings.xml. 

/max
http://about.me/maxandersen


> On 31 Oct 2014, at 19:07, Rafael Benevides <benevides at redhat.com> wrote:
> 
> Yeap.
> 
> I'm preparing QSTools to do that for us, using the approved Ids.
> 
>> On 10/31/14 16:03, Rob Cernich wrote:
>> So does that mean we can/should put the repository definitions back into the quickstart poms?
>> 
>> We?re switching back :-/
>> 
>> On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com> wrote:
>> 
>> 
>> Hey - this caught me a bit by surprise.  I thought that the JDF approach was to externalize repository definitions from the pom.xml and reference them via an external settings.xml.  I ask because we have traditionally included repo definitions in SY quickstarts.
>> 
>> thanks,
>> keith
>> 
>> On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com> 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
>> 
>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>> 
>> Better technology. Faster innovation. Powered by community collaboration. 
>> See how it works at www.redhat.com 
>> 
>> <linkedin.png> <youtube.png>
> 
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141031/44180cc8/attachment.html 

From fbricon at redhat.com  Fri Oct 31 15:57:44 2014
From: fbricon at redhat.com (Fred Bricon)
Date: Fri, 31 Oct 2014 15:57:44 -0400
Subject: [jbossdeveloper] <repository /> definition in pom.xml
	for	Quickstarts and Demos
In-Reply-To: <5BF3A11B-F227-4D81-9B77-36F2033DC8AC@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
	<779531216.3192423.1414778604873.JavaMail.zimbra@redhat.com>
	<5453CFA2.1060009@redhat.com>
	<5BF3A11B-F227-4D81-9B77-36F2033DC8AC@redhat.com>
Message-ID: <F36C76C0-AD44-46C6-AB60-B852C7D4D08D@redhat.com>

That means we?d need to conditionally include repository definitions in archetypes using the -Denterprise flag, which JBT/JBDS supports already
 
> Le 31 oct. 2014 ? 15:53, Max Rydahl Andersen <manderse at redhat.com> a ?crit :
> 
> Yeah. Just to cover bases. The projects we generate for users shouldn't have it though. Here better to use our built in support for helping adding to settings.xml. 
> 
> /max
> http://about.me/maxandersen <http://about.me/maxandersen>
> 
> 
> On 31 Oct 2014, at 19:07, Rafael Benevides <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
> 
>> Yeap.
>> 
>> I'm preparing QSTools to do that for us, using the approved Ids.
>> 
>> On 10/31/14 16:03, Rob Cernich wrote:
>>> So does that mean we can/should put the repository definitions back into the quickstart poms?
>>> 
>>> We?re switching back :-/
>>> 
>>> On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com <mailto:kbabo at redhat.com>> wrote:
>>> 
>>> 
>>> Hey - this caught me a bit by surprise.  I thought that the JDF approach was to externalize repository definitions from the pom.xml and reference them via an external settings.xml.  I ask because we have traditionally included repo definitions in SY quickstarts.
>>> 
>>> thanks,
>>> keith
>>> 
>>> On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com <mailto:benevides at redhat.com>> 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
>>> 
>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>> 
>>> Better technology. Faster innovation. Powered by community collaboration. 
>>> See how it works at www.redhat.com <http://www.redhat.com/> 
>>> 
>>> <linkedin.png> <http://www.linkedin.com/company/3258288> <youtube.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/20141031/576e8c0e/attachment-0001.html 

From manderse at redhat.com  Fri Oct 31 16:01:03 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 31 Oct 2014 16:01:03 -0400 (EDT)
Subject: [jbossdeveloper] <repository /> definition in pom.xml
	for	Quickstarts and Demos
In-Reply-To: <F36C76C0-AD44-46C6-AB60-B852C7D4D08D@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
	<779531216.3192423.1414778604873.JavaMail.zimbra@redhat.com>
	<5453CFA2.1060009@redhat.com>
	<5BF3A11B-F227-4D81-9B77-36F2033DC8AC@redhat.com>
	<F36C76C0-AD44-46C6-AB60-B852C7D4D08D@redhat.com>
Message-ID: <AC795D48-D0C3-45E9-AE2E-082B383BABFC@redhat.com>


I mean when we create default empty projects. 

But thinking about it might just be best if add a validate warning for Pom.xml and provide a quick fix for it? Wdyt about that?

/max
http://about.me/maxandersen


> On 31 Oct 2014, at 20:57, Fred Bricon <fbricon at redhat.com> wrote:
> 
> That means we?d need to conditionally include repository definitions in archetypes using the -Denterprise flag, which JBT/JBDS supports already
>  
>> Le 31 oct. 2014 ? 15:53, Max Rydahl Andersen <manderse at redhat.com> a ?crit :
>> 
>> Yeah. Just to cover bases. The projects we generate for users shouldn't have it though. Here better to use our built in support for helping adding to settings.xml. 
>> 
>> /max
>> http://about.me/maxandersen
>> 
>> 
>>> On 31 Oct 2014, at 19:07, Rafael Benevides <benevides at redhat.com> wrote:
>>> 
>>> Yeap.
>>> 
>>> I'm preparing QSTools to do that for us, using the approved Ids.
>>> 
>>>> On 10/31/14 16:03, Rob Cernich wrote:
>>>> So does that mean we can/should put the repository definitions back into the quickstart poms?
>>>> 
>>>> We?re switching back :-/
>>>> 
>>>> On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com> wrote:
>>>> 
>>>> 
>>>> Hey - this caught me a bit by surprise.  I thought that the JDF approach was to externalize repository definitions from the pom.xml and reference them via an external settings.xml.  I ask because we have traditionally included repo definitions in SY quickstarts.
>>>> 
>>>> thanks,
>>>> keith
>>>> 
>>>> On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com> 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
>>>> 
>>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>> 
>>>> Better technology. Faster innovation. Powered by community collaboration. 
>>>> See how it works at www.redhat.com 
>>>> 
>>>> <linkedin.png> <youtube.png>
>>>> 
>>>> 
>>>> 
>>> 
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>> _______________________________________________
>> 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/20141031/7a28bb57/attachment.html 

From fbricon at redhat.com  Fri Oct 31 16:14:00 2014
From: fbricon at redhat.com (Fred Bricon)
Date: Fri, 31 Oct 2014 16:14:00 -0400
Subject: [jbossdeveloper] <repository /> definition in pom.xml
	for	Quickstarts and Demos
In-Reply-To: <AC795D48-D0C3-45E9-AE2E-082B383BABFC@redhat.com>
References: <54539501.8030609@redhat.com>
	<7AF11FA7-31AB-4CE5-A082-C47772BDC7E4@redhat.com>
	<68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com>
	<779531216.3192423.1414778604873.JavaMail.zimbra@redhat.com>
	<5453CFA2.1060009@redhat.com>
	<5BF3A11B-F227-4D81-9B77-36F2033DC8AC@redhat.com>
	<F36C76C0-AD44-46C6-AB60-B852C7D4D08D@redhat.com>
	<AC795D48-D0C3-45E9-AE2E-082B383BABFC@redhat.com>
Message-ID: <928B6845-36F5-45A7-9513-401A62470A88@redhat.com>


> Le 31 oct. 2014 ? 16:01, Max Rydahl Andersen <manderse at redhat.com> a ?crit :
> 
> 
> I mean when we create default empty projects. 
> 
Not when using the original maven wizard

> But thinking about it might just be best if add a validate warning for Pom.xml and provide a quick fix for it? Wdyt about that?
Yeah interesting idea. Severity needs to be customizable and ignored marker should be serialized in workspace

> 
> /max
> http://about.me/maxandersen <http://about.me/maxandersen>
> 
> 
> On 31 Oct 2014, at 20:57, Fred Bricon <fbricon at redhat.com <mailto:fbricon at redhat.com>> wrote:
> 
>> That means we?d need to conditionally include repository definitions in archetypes using the -Denterprise flag, which JBT/JBDS supports already
>>  
>>> Le 31 oct. 2014 ? 15:53, Max Rydahl Andersen <manderse at redhat.com <mailto:manderse at redhat.com>> a ?crit :
>>> 
>>> Yeah. Just to cover bases. The projects we generate for users shouldn't have it though. Here better to use our built in support for helping adding to settings.xml. 
>>> 
>>> /max
>>> http://about.me/maxandersen <http://about.me/maxandersen>
>>> 
>>> 
>>> On 31 Oct 2014, at 19:07, Rafael Benevides <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>> 
>>>> Yeap.
>>>> 
>>>> I'm preparing QSTools to do that for us, using the approved Ids.
>>>> 
>>>> On 10/31/14 16:03, Rob Cernich wrote:
>>>>> So does that mean we can/should put the repository definitions back into the quickstart poms?
>>>>> 
>>>>> We?re switching back :-/
>>>>> 
>>>>> On 31 Oct 2014, at 15:48, Keith Babo <kbabo at redhat.com <mailto:kbabo at redhat.com>> wrote:
>>>>> 
>>>>> 
>>>>> Hey - this caught me a bit by surprise.  I thought that the JDF approach was to externalize repository definitions from the pom.xml and reference them via an external settings.xml.  I ask because we have traditionally included repo definitions in SY quickstarts.
>>>>> 
>>>>> thanks,
>>>>> keith
>>>>> 
>>>>> On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides at redhat.com <mailto:benevides at redhat.com>> 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
>>>>> 
>>>>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>>>> 
>>>>> Better technology. Faster innovation. Powered by community collaboration. 
>>>>> See how it works at www.redhat.com <http://www.redhat.com/> 
>>>>> 
>>>>> <linkedin.png> <http://www.linkedin.com/company/3258288> <youtube.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 <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/20141031/6601dd4b/attachment-0001.html 

From benevides at redhat.com  Fri Oct 31 17:34:45 2014
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 31 Oct 2014 19:34:45 -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: <54540075.6020403@redhat.com>

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
>
> 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/20141031/3dc95e80/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/20141031/3dc95e80/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/20141031/3dc95e80/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/20141031/3dc95e80/attachment-0001.png