DO NOT REPLY [Bug 33333] New: - Enable task within targets

[bu...@apache.org]

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=33333>.
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=33333

           Summary: Enable <import> task within targets
           Product: Ant
           Version: 1.6.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: ah08010-apache@yahoo.com


I'm generating a buildfile fragment dynamically, and my primary buildfile needs
to  do dependency checking on this fragment to determine if a new fragment
should be generated.

The operating scenarios are:

1. No fragment exists.

2. Fragment exists but is out-of-date.

3. Fragment exists and is fine.

Currently, I am using a HUUUUUUUUUUGE HAAAAAAACK involving <exec> to do 'black
box' recursion: 

A. <available> & <property> to provide a default (empty) fragment (I don't want
to use <import optional="true"/> because it ISN'T optional, just missing, in
case 1.)

B. Target-based checking and regeneration of the fragment in the init step of
all the primary targets.

C. <exec> ant with overridden properties to force the inclusion of the
known-good fragment.

All this hackery and cruft would go away if my init step could check the
fragment, maybe regenerate it, and then import it.

-- 
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