Ok - I've just updated the root merlin maven.xml to generate a build signature. If build somethign like repository/spi (after updating from CVS) or any other sub-project you will a property file with a name corresponding to the artifact id. E.g. for repository/spi:


avalon-repository-spi.build

 #
 # Artifact build descriptor.
 #

 build.group = avalon-repository
 build.name = avalon-repository-spi
 build.version = 1.1-dev
 build.signature = avalon-repository-spi-20031104.011352

Next step is the generation of the repository implementation version property file - and the open question is - how do we automate the collection of the impl version? What I'm thinking is that we should generate the repository version identifier inside the impl project and use the impl project's depedency on spi as the key to get the version we use to identify the property filename.

Steve.


[EMAIL PROTECTED] wrote:


Ok that's cool with me.



Cool but your first option of reading the version from the manifest sounds cleaner. It is always the same value as the POM version right?



No. Its always the same version as the jar file containing the class. For example under the cli bootstrap loader, the version would be 1.0, under the unit test package it would 3.2.3. However, as we move forward we should be able to arrive at a single parameterizable bootstrapper for all environments - and it would be that jar file which would be the definative version. Anyway - in the meantime, using a bit of jelly is easy - I'll put something in place asap.

Steve.

--

Stephen J. McConnell
mailto:[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]





--


Stephen J. McConnell
mailto:[EMAIL PROTECTED]




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to