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=26921>. 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=26921 problem running <borland> task on multiple ejb jars Summary: problem running <borland> task on multiple ejb jars Product: Ant Version: 1.6.1 Platform: All OS/Version: All Status: NEW Severity: Minor Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When the <borland> subtask is run on multiple directories to produce multiple ejb jars, each directory includes generated classes from the previous directories. In other words, if the task is run on directories X, Y and Z, Y.jar contains classes from X and Z.jar contains classes from Y and Z. If the task is run separately on X, Y and Z only the correct classes are included. The files that are added are of the form: <*>POAInvokeHandler.class <*>POA.class <*>Operations.class <*>.class <*>.class The problem seems to be in the writeJar() method in BorlandDeploymentTool.java: ... _genfiles.clear(); // <--- added this line buildBorlandStubs(homes.iterator()); //add the gen files to the collection files.putAll(_genfiles); super.writeJar(baseName, jarFile, files, publicId); ... And the correct files were incorporated in ejb jars. Not sure of this is the correct solution but it seems to be. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
