hi.
Tom Morris schrieb:
On Sun, Jun 15, 2008 at 5:39 PM, alexander krohn <[EMAIL PROTECTED]> wrote:
i don't think that a vm that runs argo would load different versions of the
jars, since the modules won't run in different vm's with different
classpaths. i think there's only one org.antlr.* namespace in the running
vm, from the first or the last loaded jar that contains it, but that's pure
speculation.
This can definitely be made to work because all the Java containers
(JBoss, etc) do it. It's possible it will take more classloader
wizardry than we currently use. What we'd need to do, if we're not
already is create a new delegating classloader for the module which
delegates back to the main ArgoUML classloader for anything that it
can't find. This will isolate anything that the module loads to just
that module.
Enforcing (or trying to enforce) lock step synchronization of version
dependencies among all plugin modules just isn't practical. We need
all the modules to be independent of each other.
Tom
so we have 3 different ways:
1.) adding jars to core-lib where they don't belong
2.) create a common-lib directory for modules maybe seperated in
"necessary for build/necessary at runtime"
3.) create a delegating classloader
my vote for 1.) because of my infinite lazyness ;)
regards,
alexander
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
