On 03/15/2012 12:17 PM, Max Rdahl Andersen wrote:
please stop just replying to me ;)
Oops, sorry.
And sure - if I remove all my mirrors from settings.xml, do not build
other plugins than from one specific branch/trunk on my machine with the same ~/.m2/repo
in it then you are correct.
Having stuff is a settings.xml makes build non portable.
It reduces the
control build provider have on dependency management since you (as a
consumer) decided to use other repositories. Having a settings.xml with
repo in it is just like adding stuff to the parent pom, we cannot
guarantee that much with customized pom.xml, it's the responsability of
the user.
I agree that having a clean repo for each branch is an annoying step.
But that's the only way I know to guarantee build isolation and
consistency (cf Jenkins), and it's working well.
We build from multiple branches
Ok.
we want to use mirrors
Really? How useful is it? Having
customized mirrors in settings.xml is
not very compatible with having strong management of dependency sources.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>