[Hawkular-dev] Maven repositories in Hawkular Parent

[Stefan Negrea]

Hello Peter,

This came up on Friday, when me and Mazz worked on getting all the Travis builds to publish -SNAPSHOT artifacts. The goal was to get the main project (with the pinger) built both on Travis and locally. 

I think it is essential to have the default repositories in the parent pom. Community users should just do 'clone & mvn' to get started. Anything more complicated (like changing settings.xml or setting up profiles) is completely unacceptable. Since we are working with snapshots and have a myriad of projects, the essential repositories need to be in the parent pom.

If you notice, the repositories are in a profile that can be disabled. So there is a lot of configuration flexibility for power users (eg. the link you posted below).

Please do not revert these changes.

Thank you,
Stefan

----- Original Message -----
> From: "Peter Palaga" <ppalaga at redhat.com>
> To: "Stefan Negrea" <snegrea at redhat.com>
> Cc: hawkular-dev at lists.jboss.org
> Sent: Monday, February 16, 2015 8:22:06 AM
> Subject: Maven repositories in Hawkular Parent
> 
> Hi Stefan,
> 
> what was your specific motivation for adding the JBoss Repos?
> 
> The topic was discussed before [1] with the result, that we will not
> hard code any Maven repositories in Hawkular Parent. All we produce and
> all we depend on should be on Maven Central.
> 
> The only inconvenience with Central is that JBoss Nexus is synced to
> central once a day only. The ones wanting to rely on freshly released
> artifacts are recommended to add JBoss Nexus to their settings.xml. This
> holds also for CI jobs.
> 
> Thanks,
> 
> Peter
> 
> [1] on #hawkular on 2015-01-21, reasons against it are summed in
> http://blog.sonatype.com/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/
>