Olaf Bergner wrote:
Well, I think I will revert to housekeeping. I set "maven.jar.manifest.extensions.add" to "false" in maven.xml - which I copied from merlin-cvs -, rebuilt, cleaned my local cache, and now it works like a charm. Steve, apologies if I caused you any trouble, but I was just being stupid.
Not at all!
The current implementation of the repository only resolves resources based on exclit requests (e.g. in a classloader defintion, or as part of a bootstrap parameter). The extension handling (which is what the second problem concerns) could be handled by the repository *if* the repository (a) maintained a cache of repository entries, and (b) included the extensions package as part of its implementation. Then when resolving classloaders and resoruces - we could could basically push all of this out to the repository and things would be even cleaner.
Now someone mentioned thay were looking at creating a repository cache - anyone remember who that was?
Cheers, Steve.
Regards,
Olaf
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
