> > >
> > I don't see a problem with this, but only the jars in lib
> > should be on the
> > system classpath. I had the impression from an earlier mail
> > that you wanted
> > to put both lib and lib/ext jars in the system classpath.
> >
>
> Yes - I do want to do that - but I still can't see a reason why we shouldn't
> just put them all on the classpath.
>
> I can see that we still need the mlet classloader - for stuff that is
> perhaps remote/in another directory.
>
> ...but why the split of directories?
>
> I want to remove the explicit definition of files that go into lib versus
> lib/ext from the build.xml.
>
> Just a thought,
> Chris
>
My reasoning for not doing it is to limit what jars have to be handled by the run
scripts.
Writing cross platform scripts that automatically pickup all jars in a directory is
more
of a challenge than using the ClassPathExtension mechanism. Since only a few
jars actually need to be on the system classpath they could simply be hard coded
in the run scripts for simplicity.
