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 2003/01/23 17:19:39 UTC

DO NOT REPLY [Bug 16371] New: - Rmic may try to compile the same class more than once

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16371>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16371

Rmic may try to compile the same class more than once

           Summary: Rmic may try to compile the same class more than once
           Product: Ant
           Version: 1.6Alpha (nightly)
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Core tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: Larry.Isaacs@sas.com


Recent changes have caused Gump's jakarta-log4j build to fail on the rmic
task.  I think the cuprit may be SourceFileScanner, which when used with
RmicFileNameMapper is returning duplicate source files.  The following patch
to Rmic avoids the duplication.  I'm not sure if this is the correct place to 
avoid the duplication, but it does fix my local gump build for jakarta-log4j.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>