ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16428] New: - Avoid requirement of putting jars in ant/lib
Date Sun, 26 Jan 2003 03:50:39 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16428>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16428

Avoid requirement of putting jars in ant/lib

           Summary: Avoid requirement of putting jars in ant/lib
           Product: Ant
           Version: 1.5.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Other
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: per@velschow.com


Now that Ant has chosen to define a lot of optional tasks via the optional.jar 
in the ant/lib directory, we are forced to put the required 3rd party libraries 
in that directory. To me that is work only half done. 

I do understand that the Ant distribution cannot include all the required 
libraries (due to license and maintenance issues). But this requirement is the 
only thing that prevents us from checking all the needed libraries for a 
project into a source control system and simply asking users to checkout and 
type ant. 

Ok, that was the problem. Here is how I think it could be solved. There are a 
few ways as I see it. 

Option 1) AFAIK, Ant implements its own ClassLoader. Wouldn't it be possible to 
somehow pass the location of required libraries to that class loader at startup 
time? 

Option 2) Extend the Ant wrapper scripts with a classpath argument that will be 
appended to the the classpath before executing Ant. 

Option 3) Extend the Ant wrapper scripts so that it will include a .antrc from 
the directory of the build file. 

The first option is in my view the right way of doing it. The second and third 
are a work-arounds that for most cases would probablt be good enough. 

I am aware that you can have the wrapper scripts read a .antrc from the user's 
home directory. But this is not good enough because different projects have 
different library requirements.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message