ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 47003] New: Add to ant lib classpath from within project file
Date Wed, 08 Apr 2009 21:25:33 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=47003

           Summary: Add to ant lib classpath from within project file
           Product: Ant
           Version: 1.7.1
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Optional Tasks
        AssignedTo: notifications@ant.apache.org
        ReportedBy: Martin.vGagern@gmx.net


I'm trying to write ant build files that only require developers to have ant
core installed, and resolve any optional tasks through ivy. For some tasks that
works fairly well by <taskdef>ing them with a proper nested classpath argument.
At least in the case of <junitreport>, however, this approach fails when trying
to format the combined report, due to missing TraXLiaison. I just filed bug
#47002 about this.

On the whole, a cleaner solution would be preferable, though. I would imagine
some expandable class loader within ant itself. Then there could be some task
which adds a given resource collection to the internal ant classpath, making it
available whenever an UnknownElement is instantiated or a task is executed.

This way, I could declare all optional tasks in ivy, could tell ivy to retrieve
them, then could ant to add them to its classpath, and start using the tasks
without any need to redefine tasks or specify bulky classpaths. Especially now
that ivy is an official ant project, I would consider such scenarios very
useful.

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

Mime
View raw message