You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2005/11/14 11:20:12 UTC
DO NOT REPLY [Bug 37475] -
ImportTask object puts artifical limit on where a file can be included
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=37475>.
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=37475
stevel@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From stevel@apache.org 2005-11-14 11:20 -------
Its not intended to be a complete replacement for &include; references; I think
xml:include will fulfil that role. Instead what <import> does is
-import files at a time when all preceeding properties have been resolved.
-import complete ant projects, not XML fragments.
-have rules for overriding and invoking targets across multiple build files.
the latter is where <import> really wins out.
I understand your need, but <import> isnt the solution.
If you have a custom ant task and want to enable reuse of core bits of it, try
creating custom ant datatypes. If it is someone else's task, look at using
presetdef and macrodef.
I'm marking this as wontfix, though think maybe we should rename it and open it
as a feature request, "add way of importing XML under tasks/targets", without
implying it is a specific failing of import.
--
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