> If you want to basically override the deployed x.y-SNAPSHOT version with the > last deployed one, then you might want to have a look at buildnumber- > maven-plugin. This is going to create a variable (say > buildnumber) in your context. Then you can use that variable in a generated > manifest. >
The buildnumber-maven-plugin sounds good. One thing is that I'm not building a jar file; it's a binary executable installer. But I can use the buildnumber-maven-plugin to pump a value in for my names. Thanks! > But in the end, I feel you're doing something wrong. Instead of (or > complementary to) doing what u describe. I would advice you set up > continuous integration that will deploy continuously (!) artifacts to a > repository manager. Then you're just left with either manually deploying the > last or the version you want (standardly timestamped) to your appserver, or > even setting up a dedicating job to deploy the last version continuously :). This is for an individual developer prior to checking in their code . . . we have a CI server but that's after you've already checked in your code.
