On Sun, 24 Feb 2002 19:58, Jose Alberto Fernandez wrote:
> > > > Myrmidon just declares dependencies via the JDK1.3
> > > > "Optional Package" spec on libraries and then all dependencies will
> > > > loaded into same classloader (unless they already exist in parent
> > > > ClassLoader).
> > >
> > > This is also available in Antlib proposal. However, in my experience
> > > ans due to the fact that many 3rd party libraries have a different
> > > release cycle than ANT, you finish with libraries with the wrong name,
> > > and it is difficult to use libraries relative to the project.
> >
> > Not sure what you mean. The jars don't need to be relative to project -
> > they could be but thats not important. Whats important is that they
> > declare dependency information and it is up to runtime to locate it given
> > a specified designation.
>
> The JDK spec specifies that all dependant jars are named relative to the
> jar requiring it, and the only variable allowed is the ${os_name} or
> something like that to work arround native libraries. So, libraries of a
> project have no way to express dependencies on libraries that come with
> ANT, or your AppServer, etc.
Nope. Go read the spec.
> > Use of a separate instance of ClassLoader for each task instance. So
> > ideally if you run velocity twice then separate ClassLoaders will be
> > created for each run. This is because some tasks use static variables
> > through dependent libraries.
>
> So, do you want in ANT that each use of each task be with a separate
> ClassLoader? That should really break everything, don't you think?
No more than separate ClassLoaders for each library.
--
Cheers,
Pete
"You know what a dumbshit the 'average man' on the street is? Well, by
definition, half of them are even dumber than that!"
J.R. "Bob" Dobbs
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
