I'm still interested in this, mostly for Apache Geronimo, but really I think that if its simple and works well (and quick) then it may be highly desirable as part of the defaults. I dug up the mail about the plugin and replied for some more intel/status on it. I'm gonna wait around for a few days (er maybe a week, cause I have other stuff to get done) and if I don't hear anything, then I'm going to roll my own (in groovy of course).

--jason


On Jul 19, 2007, at 5:29 PM, Brian E. Fox wrote:

For the archives:
http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/ install.htm
l

-----Original Message-----
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
Sent: Thursday, July 19, 2007 8:10 PM
To: Maven Developers List
Subject: Re: Including SCM details in a artifact's meta-data?

Aighty, I'll take a look.  Got a URL to the home of that puppy?

--jason


On Jul 19, 2007, at 4:58 PM, Brian E. Fox wrote:

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]



---------------------------------------------------------------------
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]

Reply via email to