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 31611] New: - Extend 'macrodef' to allow use 'target' element in it
Date Sat, 09 Oct 2004 11:53:32 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=31611>.
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=31611

Extend 'macrodef' to allow use 'target' element in it

           Summary: Extend 'macrodef' to allow use 'target' element in it
           Product: Ant
           Version: 1.6.2
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: thealx@poczta.onet.pl


Macrodef can contain only "tasks" (as described in "sequential" doc) 
It would be useful to be able to use macrodef to include whole "target" in macro
definition. 

Steps to reproduce:
1. Create build.xml with defined macrodef containing "target" element

2. Use the defined macrodef somewhere (outside of any other "target" element)

3. Run the build and observe the following message returned by Ant:

Could not create task or type of type: target. Ant could not find the task or a
class this task relies upon. 
This is common and has a number of causes; the usual solutions are to read the
manual pages then download and install needed JAR files, or fix the build file: 
- You have misspelt 'target'. Fix: check your spelling. 
- The task needs an external JAR file to execute and this is not found at the
right place in the classpath. Fix: check the documentation for dependencies.
Fix: declare the task. 
- The task is an Ant optional task and the JAR file and/or libraries
implementing the functionality were not found at the time you yourself built
your installation of Ant from the Ant sources. Fix: Look in the ANT_HOME/lib for
the 'ant-' JAR corresponding to the task and make sure it contains more than
merely a META-INF/MANIFEST.MF. If all it contains is the manifest, then rebuild
Ant with the needed libraries present in ${ant.home}/lib/optional/ , or
alternatively, download a pre-built release version from apache.org 
- The build file was written for a later version of Ant Fix: upgrade to at least
the latest release version of Ant 
- The task is not an Ant core or optional task and needs to be declared using
<taskdef>. 
- You are attempting to use a task defined using <presetdef> or <macrodef> but
have spelt wrong or not defined it at the point of use Remember that for JAR
files to be visible to Ant tasks implemented in ANT_HOME/lib, the files must be
in the same directory or on the classpath Please neither file bug reports on
this problem, nor email the Ant mailing lists, until all of these causes have
been explored, as this is not an Ant bug.

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


Mime
View raw message