Thanks, But I guess this solves only part of the problem. if one of the pom's is missing it doesn't look at settings.xml to resolv any settings (at least not the proxy). Does someone know anything about that problem as well?
Thanks for your help and the number of votes should be increased by now :) -Roy On 5/29/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
Roy van der Kuil wrote on Monday, May 29, 2006 9:07 AM: > Hi all, > > We have a project setup that uses a 'root' pom for specifying > things like > the source directory/plugins used in the build process etc. > This pom file > has been uploaded to our local maven repository. This local > maven repository > is available through the maven proxy which is specified in the > ~/.m2/settings.xml file. The problem starts when the 'root' pom is not > available then it somehow doesn't pickup the settings.xml > file to use the > proxy. > > So I figuered people need to install or download the pom.xml > file from the > cvs repository manually and all things go well. The problem > then exists that > whenever the pom file is available you'll need to keep it up to date > yourself. > > Is there something I am missing here so that people do not > need to have the > 'root' pom and still the settings.xml file is used to find the proxy? > > Our file sturcture: > pom.xml > /plugins/pom.xml > plugins/theplugin/pom.xml > client/pom.xml > > all poms available depend on the pom specified in the parent > directory by specifying something like: > <parent> > <groupId>company</groupId> > <artifactId>company</artifactId> > <version>1.0-SNAPSHOT</version> > </parent> > > -Roy Vote here: http://jira.codehaus.org/browse/MNG-2289 ;-) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
