have a look in the pom file that gets deployed.... if the property is still unexpanded in the deployed pom file then you are screwed
and it depends on the version of maven you are using. it will only work if you use one of the ___majorly___ borked versions of maven, e.g. 2.1.0 or 2.2.0 On 19 July 2010 08:59, Haszlakiewicz, Eric <[email protected]> wrote: > >-----Original Message----- > >From: Stephen Connolly [mailto:[email protected]] > > > >On 19 July 2010 06:10, Haszlakiewicz, Eric <[email protected]> > wrote: > >> You can also set the version as a property in a top-level > profiles.xml > >> file, and refer to it in all of your pom files. > > > >If it's the /project/version or /project/parent/version that you are > trying > >to use a property for then you will completely mess up the remote repo > you > >are deploying to. > > > >For updating those versions, which AFAIK is what the OP was after, you > have > >three choices: > >1. do it all by hand > >2. versions:set -DnewVersion=_____ > >3. that goal on the release plugin > > huh? Mess it up how? Does something go wrong with the property > expansion when deploying? I do use a property reference for both > /project/version and /project/parent/version. I thought it worked ok > when I tried it, but maybe I wasn't paying enough attention. > The project where I'm using this currently has a version set in the > profiles.xml of "3.1-SNAPSHOT", and when I deploy it ends up in > directory of that name, with the artifacts being named things like > "foo-3.1-20100719.075537-2.jar". Isn't that what is supposed to happen? > > eric > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
