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 36891] New: - Optional ant-task build process is error prone and counter-intuitive
Date Sun, 02 Oct 2005 15:39:08 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36891>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36891

           Summary: Optional ant-task build process is error prone and
                    counter-intuitive
           Product: Ant
           Version: 1.6.5
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Build Process
        AssignedTo: dev@ant.apache.org
        ReportedBy: gregorypierce@mac.com


When going through the ant documentation I came across the scp task and determined that it
would 
suit my needs. The docs only spoke of needing the jsch.jar file, so I made sure that file
was in my lib 
directory and tried to run, then I discovered the evil horror of the optional build process
- optional files 
are build into the core ant.jar file but only if certain things were present when that version
of ant was 
compiled. 

This is just wrong! What results is not just different versions of ant separated by version
number, but 
also different versions of ant separated by the libraries available when it was built. Who
the heck knows 
what .jar files were around when that version of ant was built! If you are in a corporate
environment this 
is especially true as the ant version may already be installed by a system admin. There should
be a core 
ant and either one optional ant which ALWAYS includes all the optional tasks or a bunch of
separate 
optional ant jars that either get built or not(i.e. there is no artifact from the build process)
based on 
libraries being available.

What REALLY should happen is that the optional stuff should be split out on its own and these

misleading empty MANIFEST.MF .jar files should go away. What is the point of having these
.jar files 
which deceive you into believing that you have the optional .jar files already built.


If you do however insist on keeping the build process this way (which is not ideal in any
way), there 
needs to be a way to ask an ant .jar file which optional ant tasks it supports and a way from
the ant 
command line a way to push in new optional tasks.

overall, just kinda disappointed in the way the optional tasks work. If I have to open up
ant's source and 
build.xml to try and figure out why I have no optional tasks, and why when I add jars to the
/lib 
directory I don't get working optional tasks - something is wrong somewhere.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message