Community
Participate
Working Groups
The N20090225-2000 build drops are missing 13MB and missing a lot of content. Looking at the logs, there is an an exception in org.eclipse.equinox.p2.extensionlocation.artifactRepository I moved to a new builder last night with new equinox bundles to support the slicer and other bugs. However, I ran a test build on Tuesday with this builder and ran many of the tests. The zips were fine and the tests all passed. eclipse.buildId=200806132000 java.version=1.5.0_14 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -application org.eclipse.equinox.p2.director.app.application -flavor tooling -installIU org.eclipse.sdk.ide -version 3.5.0.N20090225-2000 -p2.os win32 -p2.ws win32 -p2.arch x86 -roaming -profile SDKProfile -profileProperties org.eclipse.update.install.features=true -metadataRepository file:/builds/transfer/files/updates/3.5-N-builds/N20090225-2000 -artifactRepository file:/builds/transfer/files/updates/3.5-N-builds/N20090225-2000 -metadataRepositoryName Eclipse Project Test Site -artifactRepositoryName Eclipse Project Test Site -destination /builds/N200902252000/org.eclipse.releng.eclipsebuilder/../src/N20090225-2000/p2temp/equinox.p2.build/sdk.install.win32.win32.x86/eclipse -bundlepool /builds/N200902252000/org.eclipse.releng.eclipsebuilder/../src/N20090225-2000/p2temp/equinox.p2.build/sdk.install.win32.win32.x86/eclipse Command-line arguments: -os linux -ws gtk -arch x86 -application org.eclipse.equinox.p2.director.app.application -consoleLog -flavor tooling -installIU org.eclipse.sdk.ide -version 3.5.0.N20090225-2000 -p2.os win32 -p2.ws win32 -p2.arch x86 -roaming -profile SDKProfile -profileProperties org.eclipse.update.install.features=true -metadataRepository file:/builds/transfer/files/updates/3.5-N-builds/N20090225-2000 -artifactRepository file:/builds/transfer/files/updates/3.5-N-builds/N20090225-2000 -metadataRepositoryName Eclipse Project Test Site -artifactRepositoryName Eclipse Project Test Site -destination /builds/N200902252000/org.eclipse.releng.eclipsebuilder/../src/N20090225-2000/p2temp/equinox.p2.build/sdk.install.win32.win32.x86/eclipse -bundlepool /builds/N200902252000/org.eclipse.releng.eclipsebuilder/../src/N20090225-2000/p2temp/equinox.p2.build/sdk.install.win32.win32.x86/eclipse !ENTRY org.eclipse.equinox.p2.artifact.repository 4 0 2009-02-25 22:16:00.135 !MESSAGE Unexpected error loading extension: org.eclipse.equinox.p2.extensionlocation.artifactRepository !STACK 0 java.lang.AbstractMethodError at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.factoryLoad(ArtifactRepositoryManager.java:59) at org.eclipse.equinox.internal.p2.core.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:651) at org.eclipse.equinox.internal.p2.core.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:610) at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.loadRepository(ArtifactRepositoryManager.java:93) at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.loadRepository(ArtifactRepositoryManager.java:89) at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.restoreSpecialRepositories(ArtifactRepositoryManager.java:110) at org.eclipse.equinox.internal.p2.core.helpers.AbstractRepositoryManager.restoreRepositories(AbstractRepositoryManager.java:883) at org.eclipse.equinox.internal.p2.core.helpers.AbstractRepositoryManager.contains(AbstractRepositoryManager.java:252) at org.eclipse.equinox.internal.p2.director.app.Application.initializeRepositories(Application.java:180) at org.eclipse.equinox.internal.p2.director.app.Application.run(Application.java:388) at org.eclipse.equinox.internal.p2.director.app.Application.start(Application.java:509) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:556) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511) at org.eclipse.equinox.launcher.Main.run(Main.java:1270) at org.eclipse.equinox.launcher.Main.main(Main.java:1246)
The basebuilder has an old version: org.eclipse.equinox.p2.extensionlocation_1.0.100.v20081206.jar You will need v20090223 because of changes in p2.artifact.repository. As for the lack of failure during the test build, I doubt the extensions returned from the registry have any kind of order, perhaps you were just lucky during the test to get the simple artifact repository before trying the extension location repo.
Andrew, does this mean that the base builder was updated with some new versions of bundles but not all of them or is there something else going on here?
The AbstractMethodError suggests your version of org.eclipse.equinox.p2.core and org.eclipse.equinox.p2.artifact.repository were not compiled together. There was a signature change on that method to add an int flag, so if the two bundles are from different builds, you would get this error.
Sorry, Andrew is right, it's org.eclipse.equinox.p2.extensionlocation that is old. >As for the lack of failure during the test build, I doubt the extensions >returned from the registry have any kind of order, perhaps you were just lucky >during the test to get the simple artifact repository before trying the >extension location repo. We actually always try to load the simple artifact repository first, and only if that fails do we try other repository types. So it could have been some kind of connectivity problem that resulted in the other repository type being tried.
My intentions were good. I tried to only change the bundles I needed. The results was not good and there was build breakage. I am very sorry that I broke the build. In any case, I'm running a test build now with all the equinox bundles + osgi from the last I-build plus running tests.
Can you post the link here when that test build is done? There is a p2 fix I have been waiting to propagate into the builder that I want to verify the fix for.
I can't run a test build today. The servers are hosed. I have reverted to the previous builder. When I can run a test build, I'll post a link.
I copied the orbit jars from the previous build and the build is now running. It will just run a few tests, not the entire suite. http://eclipsebuildserv.ottawa.ibm.com/downloads/bogus/downloads/drops/N20090226-1110/index.php
The build is ready now http://eclipsebuildserv.ottawa.ibm.com/downloads/bogus/downloads/drops/N20090226-1110/index.php
I ran another test build this morning with tests for this bug and others, and the build seemed to be okay - no test failures. John, did you see any issues with the test build?
It looked good to me. I started it up, and did some basic sanity testing and all appears well.
