I know it works for maven 2, however it seems broken for maven 3. I am going to test this a bit more, and report back. This might be a symptom of something else.
I have also made expressions work for parent versions using a modified install & deploy plugin. I was hoping this would not be necessary in maven 3. We have multiple products which are build independently, but some of them have dependencies on each other. We do not want to have to specify the version for every product everywhere we use that, as it simply doesn't scale. We do not use the release plugin, as our versioning setup does not match how the release plugin works, and we don't want to modify YET another plugin just to make this broken plugin work. --Erlend On Wed, Dec 9, 2009 at 8:29 AM, Baptiste MATHUS <[email protected]> wrote: > And by the way, using variables for specifying dependencies versions > perfectly work out of the box with maven2. > > For example, we have a whole project hierarchy of 20+ modules that all have > the same version. Each module always references the parent version since it > must be there. But it doesn't have its own <version> tag, or even > <groupId>. > And referencing between modules is then just done by the standard variable > ${project.version}. > > FWIW. > Cheers. > > 2009/12/9 Paul Benedict <[email protected]> > > > Dana, just to clarify, he was asking about variables in dependencies. > > I don't think the parent is considered a <dependency> in the technical > > sense that Maven uses. > > > > On Tue, Dec 8, 2009 at 6:40 PM, Lacoste, Dana (TSG Software San Diego) > > <[email protected]> wrote: > > > No, with maven 2 you cannot have a variable in the parent version. The > > string will be interpreted literally without dereferencing the variable > > name. > > > > > > Similarly, you can't have an empty version number: the parent MUST have > a > > defined version number and it MUST be absolute and not contain any > > variables. > > > > > > variables work fine in any other version number, however. ranges, on > the > > other hand, do not ;) > > > > > > Dana Lacoste > > > > > > -----Original Message----- > > > From: [email protected] [mailto:[email protected]] > > On Behalf Of Paul Benedict > > > Sent: Tuesday, December 08, 2009 4:37 PM > > > To: Maven Users List > > > Subject: Re: maven 3 inheritance > > > > > >> ...and parent versions? > > > > > > Good question. You'll have to find out if the project hierarchy or > > > dependency resolution is processed first. Report back and tell us! > > > > > > Paul > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! >
