>-----Original Message----- >From: [email protected] [mailto:[email protected]] On > >On Mon, Oct 25, 2010 at 11:09 PM, Paul Benedict <[email protected]> >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: [email protected] For additional commands, e-mail: [email protected]
