Well, I use properties and publish POMs with them. I don't have an issue with them. I am sorry the variable replacements don't meet your needs; I don't know what else to suggest.
On Tue, Oct 26, 2010 at 11:46 AM, Haszlakiewicz, Eric <ehas...@transunion.com> wrote: >>-----Original Message----- >>From: paulus.benedic...@gmail.com [mailto:paulus.benedic...@gmail.com] > On >>Behalf Of Paul Benedict >>Sent: Tuesday, October 26, 2010 11:22 AM >>To: Maven Users List >>Subject: Re: avoiding dependency version number duplication >> >>>>Which is a problem because there's lots of other ways for that > variable >>>> to be set that aren't going to be available after the pom is > deployed. >> >>I wouldn't deploy a POM with variables that are not set. Won't the >><properties> tag be included either in the POM or the parent POM? > > Variables can be set in profiles.xml, or on the command line, or it'll > might be conditional based on how the build is done (e.g. "mvn -P > devbuild deploy" vs "mvn -P releasebuild deploy", and perhaps those > profile define different values). > Those are just the few cases that I can think of off the top of my head, > but I wouldn't be surprised if there are others. > > eric > > --------------------------------------------------------------------- > 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
