> From: Peter Reilly [mailto:[EMAIL PROTECTED]
>
> Jose Alberto Fernandez wrote:
>
> >
> >As the URI protocol "antlib:" provides a shortcut for the
> >above, I am just thinking on providing something similar for the
> >classpath declaration when needed.
> >
> >.
> >
> >
> >
> I have bee
Jose Alberto Fernandez wrote:
As the URI protocol "antlib:" provides a shortcut for the
above, I am just thinking on providing something similar for the
classpath declaration when needed.
.
I have been doing a little thinking about this.
What about a task to specify the classpath to use if
its own
set of third party libraries.
Jose Alberto
> -Original Message-
> From: didge [mailto:[EMAIL PROTECTED]
> Sent: 03 April 2004 00:02
> To: Ant Developers List
> Subject: RE: antlib and classloaders
>
>
> So what's to say that we can't build up an
script.
> But then you may have to maintain that script too during the life of the
> project.
>
> My aim is to try to provide an in-buildfile alternative.
>
> Jose Alberto
>
> > -Original Message-
> > From: didge [mailto:[EMAIL PROTECTED]
> > Sent: 02 A
--- Mariano Benitez <[EMAIL PROTECTED]> wrote:
> The context in which I say this is: I have a big
> application
> (www.fuego.com) that provides ant tasks to perform
> most of its admin
> operation,
> it is a requirement to have the application
> installed and then define a
> property "fuego.base
Jose Alberto Fernandez wrote:
From: Mariano Benitez [mailto:[EMAIL PROTECTED]
The context in which I say this is: I have a big application
(www.fuego.com) that provides ant tasks to perform most of its admin
operation,
it is a requirement to have the application installed and
then define
> From: Mariano Benitez [mailto:[EMAIL PROTECTED]
>
>
> The context in which I say this is: I have a big application
> (www.fuego.com) that provides ant tasks to perform most of its admin
> operation,
> it is a requirement to have the application installed and
> then define a
> property
The only problem with this is that the user build script
needs to set the correct property before the antlib is activated.
Which I think it is not much to ask.
I have a conceptual problem of usability on an antlib written like this,
remember, in the broader sense, the antlib is written by a
> From: Peter Reilly [mailto:[EMAIL PROTECTED]
>
>
> Hi,
> This sounds nice but does it save that much on
>
>
>
>
> .
>
>
>
>
>
>
Well I could ask the same question about antlib's namespace.
Why having some magic URI when users could just write:
and make the loading
> From: Peter Reilly [mailto:[EMAIL PROTECTED]
>
> Mariano's original question was why
> was classpath ignored in an antlib definition.
>
>
> loaderref="mytasks.ref">
>
>
>
> loaderref="mytasks.ref"/>
>
>
> This could be supported easily in the current code b
Hi,
This sounds nice but does it save that much on
.
Peter
Jose Alberto Fernandez wrote:
Hi, I have been giving some thought on ways to solve this nagging
issue of needing to put antlib jars on the lib directory.
We hear over and over people wanting to keep their third party
librar
Mariano's original question was why
was classpath ignored in an antlib definition.
This could be supported easily in the current code base.
-i.e. if an typedef/taskdef in an antlib sets the classpath, this classpath
will be used instead
of the antlibdefinition classp
to provide an in-buildfile alternative.
Jose Alberto
> -Original Message-
> From: didge [mailto:[EMAIL PROTECTED]
> Sent: 02 April 2004 01:16
> To: Ant Developers List
> Subject: RE: antlib and classloaders
>
>
> How about just supporting an equivalent of a
How about just supporting an equivalent of an LD_LIBRARY_PATH for antlibs,
called ANTLIB_PATH or some such?
didge
> -Original Message-
> From: Matt Benson [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 01, 2004 1:58 PM
> To: Ant Developers List
> Subject: Re: antlib a
I'm not sure I followed your suggestion. As far as
allowing a way to automagically include stuff without
adding it to the base installation, Antoine added the
-lib option and Conor extended it to pull all jars
from directories on (looks like) a path-style argument
specified with that option (as we
I have this issue in mind:
Since I need to provide antlibs to my customers, I would like them to
have to manually configure as less as possible, that means that the
previous way of saying -b /antlib was quite cool.
The problem is that I do need to control the classloader where the tasks
are loa
16 matches
Mail list logo
