Community
Participate
Working Groups
I20090224-0800 I clicked the Cancel button in a modal dialog that tried to access an update site. !ENTRY org.eclipse.equinox.p2.artifact.repository 4 0 2009-02-27 10:49:14.203 !MESSAGE Unexpected error loading extension: org.eclipse.equinox.p2.updatesite.artifactRepository !STACK 0 org.eclipse.core.runtime.OperationCanceledException at org.eclipse.equinox.internal.p2.updatesite.UpdateSite.loadSiteFile(UpdateSite.java:146) at org.eclipse.equinox.internal.p2.updatesite.UpdateSite.load(UpdateSite.java:92) at org.eclipse.equinox.internal.p2.updatesite.artifact.UpdateSiteArtifactRepositoryFactory.initializeRepository(UpdateSiteArtifactRepositoryFa ctory.java:67) at org.eclipse.equinox.internal.p2.updatesite.artifact.UpdateSiteArtifactRepositoryFactory.load(UpdateSiteArtifactRepositoryFactory.java:50) 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.core.helpers.AbstractRepositoryManager.basicRefreshRepository(AbstractRepositoryManager.java:202) at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.refreshRepository(ArtifactRepositoryManager.java:97) at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningUtil.refreshArtifactRepositories(ProvisioningUtil.java:232) at org.eclipse.equinox.internal.provisional.p2.ui.dialogs.RepositoryManipulationPage$18.run(RepositoryManipulationPage.java:492) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
The UI looks for this exception but the problem is that the AbstractRepositoryManager is logging it. See AbstractRepository line 637... } catch (Exception e) { //catch and log unexpected errors and move onto the next factory log("Unexpected error loading extension: " + providers[i].getUniqueIdentifier(), e); //$NON-NLS-1$ I could fix this myself but I think we need a general sweep over the load code to find other places, so assigning to John for now.
Fixed in HEAD. I verified in the debugger that cancel during load was correctly propagated back up to the handler in the UI.