IIRC Maven 2.1.0 and 2.2.0 try to fix this/a similar issue... they failed, which is why we say avoid Maven [2.1.0,2.2.0]
On 26 February 2010 14:04, Stephen Connolly <[email protected] > wrote: > By all means try... > > the root of the issue is that deployed poms must be final w.r.t. GAV > coordinates > > The fix appears deceptively simple (i.e. just write out the final pom where > GAV has been expanded to it's final values) > > But then you enter the real of other plugins which generate hashes of the > pom.xml, or which generate signed versions, etc > > And that is where the excrement collides with the air circulating device > > But by all means give it a try! > > -Stephen > > > On 26 February 2010 13:53, Gajo Csaba <[email protected]> wrote: > >> On 02/26/2010 02:09 PM, Wendy Smoak wrote: >> >>> 2010/2/26 Gajo Csaba<[email protected]>: >>> >>> >>> >>>> I would like to use an environment variable to define the parent >>>> project. So >>>> I wrote that it's version is >>>> <parent> >>>> ... >>>> <version>${env.VERSION_NUMBER}</version> >>>> </parent> >>>> >>>> >>> In short, you can't do that. Take a look at >>> http://jira.codehaus.org/browse/MNG-2569 and the linked issues, as >>> well as previous discussions (probably on the dev list) for more info. >>> >>> >>> >> >> Hmm bug reported in 2006 and last message is from 2008. Is it really such >> a complicated issue? Maybe I can give it a try and fix it? >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >
