Community
Participate
Working Groups
As reported in dash-dev@eclipse.org: > I'm still trying to get our build to work. With the R36_M4 basebuilder, the plugins are now compiled correctly according to their dependencies, but the build fails every time during the pack200 stage. I noticed that other have experienced the same problem, but since the 3.5 basebuilder doesn't work with our build it would be good to know if the cause of this problem has already been identified. > java.lang.RuntimeException: Application > "org.eclipse.update.core.siteOptimizer" could not be found in the registry.
Created attachment 170703 [details] use org.eclipse.equinox.p2.jarprocessor*.jar if available; else fall back to old way
nick, these modification breaks EEF builds : https://build.eclipse.org/hudson/job/cbi-emf-eef-0.7-nightly/411/console [build] Trying to override old definition of task resolvepath [build] [build] get.PACK200_JAVA_HOME: [build] Trying to override old definition of task resolvepath [build] [build] get.baseoswsarch: [build] [echo] Pack with /opt/public/common/ibm-java2-ppc-50/jre/bin/pack200 [build] [build] BUILD FAILED [build] /opt/public/cbi/build/org.eclipse.dash.common.releng/buildAll.xml:378: The following error occurred while executing this line: [build] /opt/public/cbi/build/org.eclipse.dash.common.releng/buildAll.xml:419: The following error occurred while executing this line: [build] /opt/public/cbi/build/org.eclipse.dash.common.releng/tools/scripts/buildAllHelper.xml:872: The following error occurred while executing this line: [build] /opt/public/cbi/build/org.eclipse.dash.common.releng/tools/scripts/buildAllHelper.xml:1360: The following error occurred while executing this line: [build] /opt/public/cbi/build/org.eclipse.dash.common.releng/tools/scripts/buildAllHelper.xml:820: Java returned: 1 [build] [build] Total time: 1 minute 37 seconds BUILD FAILED /opt/users/hudsonbuild/.hudson/jobs/cbi-emf-eef-0.7-nightly/workspace/org.eclipse.emf/org.eclipse.emf.eef/releng/build.xml:52: The following error occurred while executing this line: /opt/public/cbi/build/org.eclipse.dash.common.releng/build.xml:40: The following error occurred while executing this line: /opt/public/cbi/build/org.eclipse.dash.common.releng/buildAll.xml:329: The following error occurred while executing this line: /opt/public/cbi/build/org.eclipse.dash.common.releng/buildAll.xml:350: Java returned: 13
(In reply to comment #0) > > I'm still trying to get our build to work. With the R36_M4 basebuilder Have you tried the R36_RC2 basebuilder, which is currently recommended? http://wiki.eclipse.org/Platform-releng-basebuilder#Current_build_tag_for_3.6_stream_builds_.28Helios.29 > > java.lang.RuntimeException: Application > > "org.eclipse.update.core.siteOptimizer" could not be found in the registry. FWIW, in my "legacy" (non-Athena) builds, I'm running the siteOptimizer from the installed Eclipse and not from the Basebuilder, and that works fine for me. From a shellscript: tgtlauncher=`ls ${HOME}/ws2/eclipse/plugins/org.eclipse.equinox.launcher_* | sort | tail -1` java -jar ${tgtlauncher} \ -application org.eclipse.update.core.siteOptimizer \ -digestBuilder -digestOutputDir=$SITE \ -siteXML=$SITE/site-europa.xml Any change to the builder carries enormous risk at this stage in the Helios endgame. If the R36_RC2 basebuilder works, that would be best. How sever is the problem of not having siteOptimizer after all? What could a fix with minimal risk look like? The changes from the attachment have broken people, can they be reverted to unblock Helios builds?
Issue here was that there were builds failing because the optimizer step was failing. I applied this fix before I saw Kim's note that basebuilder R36_RC2 fixed this (missing jar in R36_M4). So... this fix appears to not in fact be needed.
