[EMAIL PROTECTED] wrote:
build.group = avalon-repository
build.name = avalon-repository-spi
build.version = 1.1-dev
build.signature = avalon-repository-spi-20031104.011352
Works like a champ for me thanks.
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.
Collection of impl version? I guess you mean grabbing the urls out of the POM for the dependencies? Are there some tags in jelly to query the maven POM?
What I mean is that what we need is somethign like:
repository-catalogue-[REPOSITORY-SPI-VERSION].properties
Where the contents of the properties file is the build signature document form the impl package.
Steve.
Alex
--------------------------------------------------------------------- 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]
