Right. The blog entry explains this "bootstrapping" problem quite well.
> -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Anders Hammar > Sent: Monday, October 04, 2010 1:02 PM > To: Maven Users List > Subject: Re: Company-wide settings > > It wouldn't work for other reasons as well. > Here's one case: > You're developing your Maven project. You specify the corp parent as the > parent. But that pom is in the corp repo and not on your hard drive. And > as > the info about that repo is in the parent, Maven doesn't know of the repo > and can't get the corp parent. > > It has to be defined in settings.xml. > > /Anders > On Mon, Oct 4, 2010 at 18:57, Thiessen, Todd (Todd) > <[email protected]>wrote: > > > I wouldn't personally. This blog at Sonatype explains why. > > > > > > http://www.sonatype.com/people/2009/02/why-putting-repositories-in- > your-poms-is-a-bad-idea/ > > > > > > > > > -----Original Message----- > > > From: Phillip Hellewell [mailto:[email protected]] > > > Sent: Monday, October 04, 2010 12:55 PM > > > To: Maven Users List > > > Subject: Re: Company-wide settings > > > > > > On Mon, Oct 4, 2010 at 9:11 AM, Phillip Hellewell <[email protected]> > > > wrote: > > > > Thanks all for the great suggestions. > > > > > > Do you think using a parent pom for the settings would also be a > > > workable solution? > > > > > > I'm already going to have to use a parent pom anyways, for the > default > > > distributionManagement (since that can't go in settings.xml), so > maybe > > > I should just do all my company-wide settings in a shared pom that > > > every project includes using <parent>. > > > > > > Phillip > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
