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=31604>. 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=31604 Build problems against jdk1.5 Summary: Build problems against jdk1.5 Product: BCEL Version: 5.1 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Main AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] There are two apparent problems. The first is that BCEL's "Deprecated" class has a name clash with the new "Deprecated" interface in java.lang, which first appeared in jdk1.5. Two obvious solutions to this are to (1) rename BCEL's class to something like "DeprecatedAttr" (which would break source that used this class) or (2) change all internal references to "Deprecated" to the fully qualified class name "org.apache.bcel.classfile.Deprecated". The second is much more minor. In "build.xml" the "jar" target depends on the "examples" target. Shouldn't it depend on "compile" (or perhaps "test"). In the "jar" target build instructions, there is also a mandatory dependency on the file "manifest.txt" it seems like this should be optional. If not present, let "jar" itself generate a Manifest. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
