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


On 31 Oct 2014, at 19:07, Rafael Benevides <benevides@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@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@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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossdeveloper
_______________________________________________
jbossdeveloper mailing list
jbossdeveloper@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossdeveloper