Community
Participate
Working Groups
This failure caused the whole build to fail, in what would have been the I-build I20130305-2000. This bug is specifically for "why did the build fail", instead of logging as a compile error and continuing on? Is there a separate "compile" for apibuild.xml? Is it related to annotation processing? Or ... just normal, run-of-the-mill expectation and something that should cause the build to fail? [INFO] Building jar: /opt/public/eclipse/builds/4I/master/gitCache/eclipse.platform.releng.aggregator/eclipse.platform.ui/bundles/org.eclipse.jface.databinding/target/org.eclipse.jface.databinding-1.6.200-SNAPSHOT.jar [INFO] Building jar: /opt/public/eclipse/builds/4I/master/gitCache/eclipse.platform.releng.aggregator/eclipse.platform.ui/bundles/org.eclipse.e4.ui.workbench3/target/org.eclipse.e4.ui.workbench3-0.12.0-SNAPSHOT.jar Generating .apibuild.xml [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.17.0-SNAPSHOT:compile (default-compile) on project org.eclipse.equinox.util: Compilation failure: Compilation failure: [ERROR] /opt/public/eclipse/builds/4I/master/gitCache/eclipse.platform.releng.aggregator/rt.equinox.bundles/bundles/org.eclipse.equinox.util/src/org/eclipse/equinox/internal/util/impl/tpt/threadpool/ThreadPoolManagerImpl.java:[84,0] [ERROR] Object result = (ServiceFactoryImpl.privileged()) ? AccessController.doPrivileged(this) : new Executor(); [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [ERROR] Incompatible conditional operand types T and Executor [ERROR] /opt/public/eclipse/builds/4I/master/gitCache/eclipse.platform.releng.aggregator/rt.equinox.bundles/bundles/org.eclipse.equinox.util/src/org/eclipse/equinox/internal/util/security/PrivilegedRunner.java:[102,0] [ERROR] return (context != null) [ERROR] // [ERROR] ? AccessController.doPrivileged(runner, (AccessControlContext) context) [ERROR] : AccessController.doPrivileged(runner); [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [ERROR] Incompatible conditional operand types T and T [ERROR] 2 problems (2 errors)
Created attachment 227975 [details] zipped up version of target The @dox.xml file looks relatively normal to my naive eyes ... that is, it has -proceedOnError, and other things inherited from eclipse-platform-parent pom. There is a generated-sources/annotations directory, but its empty.
Created attachment 227976 [details] full output log of whole run I have started to run without -X on the mvn command line ... so, a) smaller than usual, b) might be less useful for this case?
Jan, I don't know if this is related to the work you have been doing (I'm not even sure if we are yet using the work you've been doing!) but CCing you just for your awareness. Appears, from my quick read, to happen during the generation of data for API Tools, and ideally would not and to continue with rest of build. But, not sure ... maybe this was the very last thing it was doing? Just FYI.
Is this similar to bug 399617 and an indication that either -Pno-bree-libs was not used or -Pbree-libs is used but the proper EE jars are not setup in the build?
(In reply to comment #4) > Is this similar to bug 399617 and an indication that either -Pno-bree-libs > was not used or -Pbree-libs is used but the proper EE jars are not setup in > the build? Thanks for the hint. I see the libs are still there, still in toolchain, but I might have messed up the part of the script where it is "passed in" to mvn. I'll check that angle.
Confirmed. I messed up that part of the command line. There's one build in progress expected to fail, then I'll start another after fixing the script. Thanks for the quick pointer.
http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=9b30b6bb6cf5f92c09e7c735dddc8655095dac35 I missed one spot of renaming a bash variable (from COMPARATOR to MVN_DEBUG) hence effectively causing a bash function call to have 7 arguments instead of 8 ... thus wrecking havoc with the 4 or so variables that followed it. $MAVEN_BREE being one of those.
mass change to 'verified', since these are all routine or obviously fixed.
