Compilation fails on warning messages from javac (Java 6)

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 2.0.2
Fix Version/s: 2.1
Labels:
None
Environment:

Hide
Mac OSX 10.4.10

Maven version: 2.0.7
Java version: 1.6.0-dp
OS name: "mac os x" version: "10.4.10" arch: "i386"

java version "1.6.0-dp"
Java(TM) SE Runtime Environment (build 1.6.0-dp-b88-34)
Java HotSpot(TM) Client VM (build 1.6.0-b88-17-release, mixed mode, sharing)

Show
Mac OSX 10.4.10 Maven version: 2.0.7 Java version: 1.6.0-dp OS name: "mac os x" version: "10.4.10" arch: "i386" java version "1.6.0-dp" Java(TM) SE Runtime Environment (build 1.6.0-dp-b88-34) Java HotSpot(TM) Client VM (build 1.6.0-b88-17-release, mixed mode, sharing)

Number of attachments :
2

Description

The attached project fails due to an inability to parse the following warning messages from the Java compiler (Java 6)

[INFO] Compilation failure
could not parse error message: /Users/tmeighen/compiler-warning/entity/target/classes/test/MyEntity.class: warning: Cannot find annotation method 'name()' in type 'javax.persistence.Table': class file for javax.persistence.Table not found
/Users/tmeighen/compiler-warning/logic/src/main/java/test/Logic.java:7: warning: [deprecation] deprecateMe() in test.MyEntity has been deprecated
entity.deprecateMe();
^

could not parse error message: /Users/tmeighen/compiler-warning/entity/target/classes/test/MyEntity.class: warning: Cannot find annotation method 'name()' in type 'javax.persistence.Table': class file for javax.persistence.Table not found
/Users/tmeighen/compiler-warning/logic/src/main/java/test/Logic.java:7: warning: [deprecation] deprecateMe() in test.MyEntity has been deprecated
entity.deprecateMe();
^

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

compiler-warning.tar.gz

27/Sep/07 1:27 PM

2 kB

Tim Meighen
warning.tar.gz

30/Dec/07 1:05 PM

0.8 kB

Christian Bach

Issue Links

depends upon

PLXCOMP-87 The Javac Compiler Wrapper breaks the Build on Warnings in Java 6.

Activity

Ascending order - Click to sort in descending order

Christian Bach made changes - 30/Dec/07 1:05 PM

Field	Original Value	New Value
Attachment		warning.tar.gz [ 31534 ]

Hide

Permalink

Christian Bach added a comment - 30/Dec/07 1:15 PM - edited

The project in the second attachment fails in similar fashion when built using Java 6 on Linux.

The problem is rooted in the compiler-plugin's dependency on plexus-compiler-javac which, in its current version 1.5.3, is not capable of parsing Java 6 warning and/or error messages properly.

see also here: http://jira.codehaus.org/browse/PLXCOMP-87

Show

Christian Bach added a comment - 30/Dec/07 1:15 PM - edited The project in the second attachment fails in similar fashion when built using Java 6 on Linux. The problem is rooted in the compiler-plugin's dependency on plexus-compiler-javac which, in its current version 1.5.3, is not capable of parsing Java 6 warning and/or error messages properly. see also here: http://jira.codehaus.org/browse/PLXCOMP-87

Brian Fox made changes - 01/Jan/08 9:21 AM

Link

This issue depends upon ~~PLXCOMP-87~~ [ ~~PLXCOMP-87~~ ]

Hide

Permalink

Ben Tatham added a comment - 22/Jan/08 2:49 PM

I have the same problem on this warning:
C:\work\.....java:176: warning: sun.misc.Cleaner is Sun proprietary API and may be removed in a future release

sun.misc.Cleaner cleaner = (sun.misc.Cleaner) getCleanerMethod

If I turn off verbose on the compiler-plugin, it passes the build. With verbose=true, the build gets a Compilation Failure.

Show

Ben Tatham added a comment - 22/Jan/08 2:49 PM I have the same problem on this warning: C:\work\.....java:176: warning: sun.misc.Cleaner is Sun proprietary API and may be removed in a future release sun.misc.Cleaner cleaner = (sun.misc.Cleaner) getCleanerMethod ^ If I turn off verbose on the compiler-plugin, it passes the build. With verbose=true, the build gets a Compilation Failure.

Hide

Permalink

John Casey added a comment - 12/Feb/08 3:37 PM

Applied patch for ~~PLXCOMP-87~~ from Christian Bach, and all is well. Tested against the attached warning.tar.gz...

Show

John Casey added a comment - 12/Feb/08 3:37 PM Applied patch for PLXCOMP-87 from Christian Bach, and all is well. Tested against the attached warning.tar.gz...

John Casey made changes - 12/Feb/08 3:37 PM

Assignee		John Casey [ jdcasey ]
Resolution		Fixed [ 1 ]
Fix Version/s		2.1 [ 12304 ]
Status	Open [ 1 ]	Closed [ 6 ]

Hide

Permalink

John Casey added a comment - 13/Feb/08 11:48 AM

Need to look into NPE caused by move to 1.6-SNAPSHOT for plexus compiler stuff, and also whether the fix for this NPE is actually going to fix the problem...some indications I'm getting right now say no.

Show

John Casey added a comment - 13/Feb/08 11:48 AM Need to look into NPE caused by move to 1.6-SNAPSHOT for plexus compiler stuff, and also whether the fix for this NPE is actually going to fix the problem...some indications I'm getting right now say no.

John Casey made changes - 13/Feb/08 11:48 AM

Status	Closed [ 6 ]	Reopened [ 4 ]
Resolution	Fixed [ 1 ]

Hide

Permalink

John Casey added a comment - 13/Feb/08 2:39 PM

added some more defensive code to the call to log information about the sources being compiled...for instance, if JavacCompiler is constructed without an accompanying call to enableLogging(..) because of some incompatibility with the AbstractLogEnabled/LogEnabled class/interface (like if it were loaded from the wrong classloader for some reason), then it should make sure the logger is not null before using it.

Also, I adjusted the version for plexus-utils back to 1.0.4, and marked the plexus-container-default version to scope == test, since maven will provide its own.

Show

John Casey added a comment - 13/Feb/08 2:39 PM added some more defensive code to the call to log information about the sources being compiled...for instance, if JavacCompiler is constructed without an accompanying call to enableLogging(..) because of some incompatibility with the AbstractLogEnabled/LogEnabled class/interface (like if it were loaded from the wrong classloader for some reason), then it should make sure the logger is not null before using it. Also, I adjusted the version for plexus-utils back to 1.0.4, and marked the plexus-container-default version to scope == test, since maven will provide its own.

John Casey made changes - 13/Feb/08 2:39 PM

Status	Reopened [ 4 ]	Closed [ 6 ]
Resolution		Fixed [ 1 ]

Hide

Permalink

Mike Calmus added a comment - 24/Mar/09 2:09 PM

Should this be working now in Maven 2.1.0? I'm still getting fatal errors when I have verbose compilation turned on.

Show

Mike Calmus added a comment - 24/Mar/09 2:09 PM Should this be working now in Maven 2.1.0? I'm still getting fatal errors when I have verbose compilation turned on.

Hide

Permalink

Ricardo Borillo added a comment - 09/May/09 11:54 AM

Hi all,

Any news on this?? I'm still getting the same errors on 2.1.0 too ... Any workaround??

Thanks

Show

Ricardo Borillo added a comment - 09/May/09 11:54 AM Hi all, Any news on this?? I'm still getting the same errors on 2.1.0 too ... Any workaround?? Thanks

Hide

Permalink

Jean-Marc Borer added a comment - 27/May/09 2:31 AM

I confirm that the problem still exists with 2.1.0. Turning off the "verbose" mode for the external compiler solves the problem. That's the workaround (for me at least).

Show

Jean-Marc Borer added a comment - 27/May/09 2:31 AM I confirm that the problem still exists with 2.1.0. Turning off the "verbose" mode for the external compiler solves the problem. That's the workaround (for me at least).

Hide

Permalink

Jonathan Johnson added a comment - 27/May/09 12:55 PM

My build is now breaking too after adding the SwingSet2.jar to one of my maven modules. This happens under Windows and Linux.

Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
Java version: 1.6.0_12
Java home: /usr/java/jdk1.6.0_12/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.18-92.1.18.el5" arch: "i386" Family: "unix"

[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

could not parse error message: DemoModule.java(:DemoModule.java):214: warning: [deprecation] show() in java.awt.Window has been deprecated
frame.show();
^

could not parse error message: SwingSet2.java(:SwingSet2.java):748: warning: [deprecation] show() in java.awt.Window has been deprecated
f.show();
^

could not parse error message: SwingSet2.java(:SwingSet2.java):1316: warning: [deprecation] show() in java.awt.Dialog has been deprecated
aboutBox.show();

Show

Jonathan Johnson added a comment - 27/May/09 12:55 PM My build is now breaking too after adding the SwingSet2.jar to one of my maven modules. This happens under Windows and Linux. Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400) Java version: 1.6.0_12 Java home: /usr/java/jdk1.6.0_12/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux" version: "2.6.18-92.1.18.el5" arch: "i386" Family: "unix" [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure could not parse error message: DemoModule.java(:DemoModule.java):214: warning: [deprecation] show() in java.awt.Window has been deprecated frame.show(); ^ could not parse error message: SwingSet2.java(:SwingSet2.java):748: warning: [deprecation] show() in java.awt.Window has been deprecated f.show(); ^ could not parse error message: SwingSet2.java(:SwingSet2.java):1316: warning: [deprecation] show() in java.awt.Dialog has been deprecated aboutBox.show();

People

Assignee:

John Casey

Reporter:

Tim Meighen

Vote (1)

Watch (5)

Dates

Created:

27/Sep/07 1:27 PM

Updated:

27/May/09 12:55 PM

Resolved:

13/Feb/08 2:39 PM