So, basically, you use a "wrapper" to get around maven? I do something similar: I use a .properties file, then run an <xmltask> ant script to update the maven pom.xml files. Very predictable, very manageable, and bypasses the maven-release-plugin which caused ALL KINDS of headaches because it doesn't work with perforce properly.
James, that'd be my recommendation: update the maven info to fit your build before you run maven :) Dana Lacoste -----Original Message----- From: David C. Hicks [mailto:[email protected]] Sent: Friday, August 28, 2009 11:01 AM To: Maven Users List Subject: Re: inject version into source? I have done this by setting up a properties file that gets filtered at build time. Then, I use that properties file in a Spring PlaceholderConfigurer to get the value injected where I need it. James Russo wrote: > Hello, > > New maven user here. Really am liking it, just trying to get > project back online and running after switching from ant.. Is there > any standard maven way to inject maven variables (like version) into > source code, prior to compile? Is this maybe were I should just > leverage my existing any scripts to accomplish the task? > > thanks, > > -jr > > --------------------------------------------------------------------- > 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]
