Couldn't you do this with the build-number plugin. I seem to recall it was able to determine the scm rev?
-----Original Message----- From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason Dillon Sent: Thursday, July 19, 2007 7:14 PM To: Maven Developers List Subject: Including SCM details in a artifact's meta-data? Hey, any thoughts about including some of the SCM details in an artifacts meta-data? I mean, like the SVN revision of the workspace, or the P4 change number, etc. So that one can crack open a Maven generated jar file, peep at the meta-data and know where that stuff came from. Of course that won't always be 100% since the local workspace could have modifications, but assuming that some automated build process ensured this was never the case for bits that are published, then it would be a good tool to help link artifacts back to the SCM. Any ideas comments on if this is a good idea and how to get it working? --jason --------------------------------------------------------------------- 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]
