DO NOT REPLY [Bug 36523] New: - task, incompatibleWithSpawn is too restrictive

[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=36523>.
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=36523

           Summary: <java> task, incompatibleWithSpawn is too restrictive
           Product: Ant
           Version: 1.6.5
          Platform: All
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: bernard.cena@morganstanley.com


I'm trying to write a macro wrapper for <java> which provides sensible default 
values for attributes for our environment and manages the classpath. I've hit 
an issue with spawn and timeout attributes: if I supply a default value for 
timeout, then there is no way to use spawn="true". This is because the 
incompatibleWithSpawn flag is set when timeout is set with any default value, 
and it is impossible to reset timeout to null to enable spawn to be used. 
Perhaps the easiest thing to do is to relax the incompatibleWithSpawn check - 
surely spawn can be made to ignore timeout ?
This problem also applies to other tasks in general - it should be able to 
wrap tasks in macros or predefs without needing to code for special cases like 
this (similar problem will occur for junit and timeout settings, compiler 
setting for javac etc).

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