Göran  Hultgren wrote:

> Well, the classpath in Java has a few problems. The constant adding/removing
> stuff to the classpath variable is a bit annoying. Sometimes I simplify it
> by just having one directory in the classpath where I simply unpack all the
> jarfiles into one big tree.
> 
> Another thing is that the order matters in the classpath since the
> jarfiles/directories in the beginning might include classes that override
> classes in a jarfile later in the path. That can really make you go nuts
> trying to find out why something isn't working.

Yes, problems such as these are among what I the virtual module hierarchy is
meant to avoid.

> Some form of distributed registry over the net which can resolve symbolic
> names into concrete urls

Yeah, that sounds pretty similar to how URLs are computed from module paths,
even though the repository code is just a skeleton yet.

Henrik