ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruce Atherton <>
Subject Re: debian packaging related tasks - sandboxable?
Date Thu, 24 May 2007 19:47:41 GMT
I agree you'd need a way to turn it off, but I disagree that just adding 
to the LOCALCLASSPATH solves the problem. Or at least, we could do a 
better job in my opinion.

What I was thinking of is something like this: running "ant -install 
new-antlib.jar" could automatically copy the file to ${ANTLIB_HOME}, or 
if that were not set to a compiled-in default location (or loaded from 
an ant.conf file) like "${ANT_HOME}/antlib". That way different 
distributions could define the default location they preferred, but a 
user could still change it either temporarily or permanently.

The advantage to this is that control of the antlibs would be given to 
ant, which knows the most about them. Antlib-specific behaviour like 
validating the antlib, or providing a versioning mechanism, or some 
other feature we think of later would be much easier to do this way, it 
seems to me.

The downside is that the control is pretty coarse-grained: either you 
accept all the antlibs installed in ${ANTLIB_HOME}, or none of them. 
There is also the potential for all of the issues that installed 
extensions have had.

Stefan Bodewig wrote:
> On Fri, 11 May 2007, Bruce Atherton <> wrote:
>> What do people think about Ant supporting a way to install and
>> remove antlibs from the command line into a standard antlib
>> directory that is automatically added to the classpath on startup?
>> That would support the creation of separate debian packages for
>> individual antlibs. Installed antlibs could be made automatically
>> available to any build file.
> This would be a system wide installation, so as a user you'd need a
> way to turn it off.  There may be situations where your system
> administrator has installed something into that directory that you
> don't want to have on your CLASSPATH (version conflicts ...).
> We already have a lot of support for RPM builds in our starter script.
> We could simply hook in Debian systems using the same mechanisms
> without changing anything.  Just provide a /etc/ant.conf which adds
> the directory (or the jars contained in it) you talk about to
> LOCALCLASSPATH and you are done.
> Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message