Have you tried executing your Maven build specifying -Dinvoker.settingsFile=<my-settings-file> from command line on your pc. If it works the issue is related to Jenkins. It should work as it should override the pom configured value.
/Anders On Tue, Jun 21, 2011 at 18:56, Asmann, Roland <[email protected]>wrote: > Hi all, > > I configured the invoker-plugin in my POM to use the settings-file in > "${maven.home}/conf/settings.xml" -- which works fine for local > development. > > However, when running my Projects on Jenkins, I have configured the > project with a different settings-file, since the Maven on the server > uses the default file that came with the Maven-Install. > I told Jenkins to run the job with '-s <my-settings-file>' and added > '-Dinvoker.settingsFile=<my-settings-file>' to let the invoker now as well. > > The problem is, the invoker is still trying to open > '${maven.home}/conf/settings.xml' on which Jenkins apparently has no > read-access (don't ask me why other builds work, I am not allowed to > access the server directly). > > Can it be that the configuration given with '-D' does not override the > configuration in the POM? > > Is there a way to get around this problem and get my build running on > both Jenkins and a developer-machine? > > Thanks. > > -- > Roland Asmann > Senior Software Engineer > > adesso Austria GmbH > Floridotower 26. Stock T +43 1 2198790-27 > Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 > A-1210 Wien M +43 664 88657566 > E [email protected] > W www.adesso.at > > ------------------------------------------------------------- > >>> business. people. technology. <<< > ------------------------------------------------------------- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
