Am 04.09.2011 20:43 schrieb "Benson Margulies" <bimargul...@gmail.com>: > > On Sun, Sep 4, 2011 at 2:34 PM, Ansgar Konermann > <ansgar.konerm...@googlemail.com> wrote: > > Am 04.09.2011 20:29 schrieb "Brian Fox" <bri...@infinity.nu>: > >> > >> Release forks the build and therefore not all the parameters are > >> passed through. There is a parameter for the plugin though to specify > >> which agurments to pass, I forget what it is, but I'm sure you know > >> how to find it ;-) > > > > -Darguments="..." > > I wonder: why? Does anyone know a use case in which it's important to > make the setttings or global settings different in the forked > execution?
I'm not a Maven guru, but no, all the use cases I encountered involved passing the same set of parameters to the forked lifecycle. I'd also love to understand the motivation behind making this *not* the default behaviour. Best Ansgar > > > > >> > >> On Sun, Sep 4, 2011 at 1:48 PM, Benson Margulies <bimargul...@gmail.com > > > wrote: > >> > I was a bit taken aback when a run of the maven release plugin failed > >> > because I ran > >> > > >> > mvn -gs my_settings.xml release:prepare > >> > > >> > and then the build couldn't find the repositories from the global > > settings? > >> > > >> > Is there really on purpose, or should I write up a JIRA? > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> > For additional commands, e-mail: users-h...@maven.apache.org > >> > > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
