Nicola Ken Barozzi wrote:
Niclas Hedhman wrote:
On Monday 21 June 2004 13:04, Nick Chalko wrote:
...
Classloading is a real problem in java, and an important one to tackle but I prefer to keep the scope of Depot limited. Other project's like Avalon can tackle the classloaders. Perhaps we can take over the version/download/security stuff.
I don't agree here, Nick, classloading is part of artifact handling, albeit in the JVM.
It can and IMHO should live as a Depot subproject.
I withdraw my -1,
Classloading as a separate project does make sense for Depot. I should have used a -0 at worst.
R, Nick
