On Tuesday 02 March 2004 10:31, Cameron Fieber wrote: I haven't forgotten about it... Just took a while to get around looking at it.
> Anyway, I think the problem may be partly due to the fact that there > isn't a separation of API and Impl for excalibur-thread, but the > ThreadPool interface is part of the API of cornerstone-threads so that > excalibur-thread has to be imported in the top level classloader. Duuuuhhhh.... It is releated to that the Cornerstone and Excalibur libraries has not been upgraded to Avalon-Meta compliant. I.e. When you create your own components, perhaps using the template, Maven will generate .meta files, which contains the dependencies, and is needed by Merlin to resolve Jar downloads. Ok... Now we are touching on a very tochy subject, and that is the Avalon Community's own inability to support its own technologies, and currently debated in the PMC. Meanwhile, if you follow the "Merlin style" of component creation, it will work as you expect, and you will appreciate it I am sure. As for Cornerstone and Excalibur, I can't give you a clear answer yet. Cheers Niclas -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
