I may be over my head here, but I think that when you do a *release* (using the release plugin), there is an option to have a version of the pom created for the tag that has the properties fully resolved. See http://maven.apache.org/plugins/maven-release-plugin/prepare-with-pom-mojo.html
Does this address your use case? -Marshall Schor On 10/26/2010 12:05 PM, Haszlakiewicz, Eric wrote: >> -----Original Message----- >> From: paulus.benedic...@gmail.com [mailto:paulus.benedic...@gmail.com] > On >> On Mon, Oct 25, 2010 at 11:09 PM, Paul Benedict <pbened...@apache.org> >> wrote: >>> I don't believe that's supposed to happen. >> I realized how vague my answer was. Sorry! I mean the replacement is >> NOT supposed to happen. It's a substitution variable. You won't get >> the real value in there because it's resolved at build time. > 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. > This has been argued about several times, and it looks like it's not > going to get fixed because the maven people have something against > having a build generate an appropriate pom for deployment. > > Babak, if you really want to make this work right, you're probably going > to have to end up with a weird multi-stage build where first you > generate the pom.xml file (perhaps with another pom.xml, or an ant > build) and then build using the generated one. > > 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
