The problem with that set statement is the context it is set into. If you echo that variable out in any project you will get your new value, however it has not been passed on to Maven itself to use, and probably not to the plugins that are initialised before maven.xml.
You might be able to work around this by setting it in the parent scope (j:set scope="parent"), but I wouldn't rely on it working forever. Eventually parent project properties will be implemented - patience :) Cheers, Brett > -----Original Message----- > From: Sean Timm [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 29 October 2003 11:58 AM > To: Maven Users List > Subject: RE: Overall preGoal in parent maven.xml? > > > > I haven't checked for a while, but I believe build:start > > still exists and is attained first. > > This didn't seem to work... > > > However, if you put the code inside the parent maven.xml, > > outside of any goal definitions, it should be executed before > > any goals are attained. > > That seemed to hold true for a while, but I started getting > strange behavior occasionally where variables weren't getting > set. For example, I've got the following at the root maven.xml file: > > <j:set var="maven.repo.remote" value="http://starforge/repository"; /> > > This should set the artifact plugin to retrieve from my > intranet-hosted repository, but it doesn't seem to work. I > ended up moving it to $USER_HOME/build.properties...which > really stinks when I want to update something like that. > > -- Sean T. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
