[Bug 55112] New: Java task sets incompatibleWithSpawn in setAppend, regardless of value.

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=55112

            Bug ID: 55112
           Summary: Java task sets incompatibleWithSpawn in setAppend,
                    regardless of value.
           Product: Ant
           Version: 1.9.1
          Hardware: PC
                OS: Mac OS X 10.4
            Status: NEW
          Severity: major
          Priority: P2
         Component: Core tasks
          Assignee: notifications@ant.apache.org
          Reporter: nigel.magnay@gmail.com

See:
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/Java.java

Line 620.. does the following:

620  public void setAppend(boolean append) {
621            redirector.setAppend(append);
622            incompatibleWithSpawn = true;
623        }


however - this means that the stanza
java.setAppend(false);

sets incompatibleWithSpawn. 

I suspect it should do
incompatibleWithSpawn |= append;

Which is the style in other methods. There seem to be other
incompatibleWithSpawn setters that also have this bug.

Projects that re-use this JAR (e.g: Cargo) therefore also exhibit this problem,
where containers fail to start because of a belief that a non-spawnable setting
has been used.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 55112] Java task sets incompatibleWithSpawn in setAppend, regardless of value.

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=55112

Stefan Bodewig <bo...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Stefan Bodewig <bo...@apache.org> ---
should be fixed with svn revision 1494173

one could argue that some of the other setter should only set
incompatibleWithSpawn if their arguments are not-null but Ant's runtime will
never invoke the setter for null-args and many tasks rely on this.

-- 
You are receiving this mail because:
You are the assignee for the bug.