Red Hat Bugzilla – Bug 831820
Torquebox compilation fails with JDK 7
Last modified: 2015-08-02 19:42:52 EDT
Description of problem:
Torquebox compilation fails with JDK 7.
Extract from the maven output:
19:54:38 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project torquebox-core: Compilation failure: Compilation failure:
19:54:38 [ERROR] could not parse error message: warning: [options] bootstrap class path not set in conjunction with -source 1.6
19:54:38 [ERROR] /mnt/hudson_workspace/workspace/wfk-2.0-torquebox/85a40f63/wfk-torquebox-ci/jboss-wfk-2.0.0.ER7/src/torquebox-2.0.3.redhat.1/modules/core/src/main/java/org/torquebox/core/datasource/processors/DatabaseProcessor.java:32: warning: [deprecation] ConnectorServices in org.jboss.as.connector has been deprecated
19:54:38 [ERROR] import org.jboss.as.connector.ConnectorServices;
19:54:38 [ERROR] ^
19:54:38 [ERROR] /mnt/hudson_workspace/workspace/wfk-2.0-torquebox/85a40f63/wfk-torquebox-ci/jboss-wfk-2.0.0.ER7/src/torquebox-2.0.3.redhat.1/modules/core/src/main/java/org/torquebox/core/datasource/processors/DatabaseProcessor.java:[32,29] [deprecation] ConnectorServices in org.jboss.as.connector has been deprecated
When maven-compiler-plugin version in torquebox-parent pom is changed from 2.0.2 to 2.5.1, compilation is successful.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
When compiling TorqueBox from sources using JDK 7, you should update maven-compiler-plugin version in torquebox-parent pom is changed from 2.0.2 to 2.5.1, than the compilation is successful.
Updated to maven-compiler-plugin 2.5.1 in upstream
Product Mead environment uses version 2.3.2-redhat-1.
I don't understand why you would like to compile TB sources with JDK 7. We have set up only JDK 6 in MEAD.
Compilation from sources is needed in order to execute integration tests attached to the project.
This is not related to bits in MEAD.
There is a requirement to build with JDK7 for integration tests?
I would say that requires to be run on JDK7, but not compiled.
Nope. You can still build the binaries for end users with jdk6 only. However, it is required to be able to reproduce the process with JDK7 as well.
OK, but you should use what was built in MEAD environment, not what you build in integration testsuite, that is my point. The integration tests then are not valid for WFK Torquebox IMO.
And what is more important, this issue reports using version 2.0.2, but that is not the version used in WFK torquebox. This bz report seems like running community bits. ;-)
Plugins are managed in jboss-parent and if you need run productized integration testsuite you should use those versions (compiler 2.3.2 or 2.3.2-redhat-1)
I won't change anything in TB for this issue and honestly will reject it if you doesn't explain it more where 2.0.2 version show up in productized torquebox.
Moved to ON_QA, will be (re)verified in WFK 2.1.0.CR1.
Distributed as a part of WFK 2.1.0.GA release.