https://issues.apache.org/bugzilla/show_bug.cgi?id=47595
--- Comment #7 from Curt Arnold <[email protected]> 2009-10-04 06:17:10 PDT --- Good to know the problem you were trying to fix. Is this observed with Eclipse projects that are generated with "mvn eclipse:eclipse", with projects that Eclipse reads directly or is it using Maven with the Eclipse java compiler? Leaving the byte-code at 1.1 allows us to binary diff the generated classes with earlier versions of log4j 1.2 to determine that we didn't make inadvertent changes between versions. That is an auditing step that we could still do by rolling back the target, but it is an extra annoyance and it is a nice check for something as widely deployed as log4j. The assert keyword was added in the Java language at 1.4. I'm not sure if that required upgrading the byte-code version to 1.4 also. Could you try just upgrading the source to 1.4 and see if that eliminates your issue with Eclipse. Updating source to 1.5 definitely requires updating the byte-code to 1.5 since there are productions that can not be generated using 1.1 byte code. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
