Hi Chad,
If your artifacts are JARs, one perhaps less disruptive option is to add a
timestamp to the JAR manifest:
<properties>
<!-- NB: Specify formatting of the maven.build.timestamp property. -->
<maven.build.timestamp.format>yyyy-MM-dd'T'HH:mm:ssZ</maven.build.timestamp.format>
</properties>
...
<plugin>
<artifactId>maven-jar-plugin</artifactId>
<version>2.4</version>
<configuration>
<archive>
<manifestEntries>
<!-- Add a formatted timestamp for the build. -->
<Implementation-Date>${maven.build.timestamp}</Implementation-Date>
</manifestEntries>
</archive>
</configuration>
</plugin>
Then you can use a script to dump the "Implementation-Date" entry from the
JAR's manifest.
Regards,
Curtis
On Tue, Sep 18, 2012 at 10:00 AM, Davis, Chad <[email protected]> wrote:
> 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]
>
>
