Hi, Actually, it seems like there's different solutions depending on your needs.
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. If you want to have a differently locally named artifact, then you could use finalName tag. 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 :). HTH. Cheers Le 18 sept. 2012 17:01, "Davis, Chad" <[email protected]> a écrit : > I frequently deploy artifacts that I build locally to some of my dev > environment servers. Later I have trouble figuring out which one of my > local dev builds I'm looking at in a given dev environment; this is because > they are all named "blahblah-SNAPSHOT.run" > > So, I'd like to add a timestamp to that, just like what occurs when during > the deploy of that same artifact to nexus, but: > > 1) I don't know how > > 2) I don't know if it would cause other troubles > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
