[EMAIL PROTECTED] wrote:
Steve,
OOoooh - it might not be all that beneficial since I need the resource loading file to be in the jar with the build spec anyway. Scratch my last email.
Good - because I was looking at your last email and as I was rreading it and re-reading it I was getting a headache. Then then this post came and headache dissapear! What I think we can do is to key against suprojects that contain a "bootstrap" subproject. This will enable a clean seperation of boot semantics and dependecies from things like API/SPI/IMP.
I.e. from top level build:
* if a project deployment directory ends with /bootstrap then create a group catalog properties file
* during the build of the install - check for group catalog property files and add them to respect repository groups
During runtime:
* get a property/parameter/whatever of the bootstrap scenario (e.g. cli, unit
test, servlet, etc.), build as per you earlier email (strandard factory, etc.).
What this implies is that we move boot logic out of repository/spi and into a
repository/bootstrap.
Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
