[pde-dev] error in 3.4 M6 interacting with 3.3 update site

[Ryan Huff <rhuff@xxxxxxxxxxxxx>]

Greetings,

 

I am just getting started with working on 3.4 compatibility, and I wanted to test if our update site for a 3.3 compatible plug-in would work in the new update manager.  Whether I drag the URL from my browser to the “Available Features” pane, or use “Manage sites…” to add the site, I am getting an npe from “Fetching children of Known Repositories.”  I can’t find any information on this, and I was under the impression that the update site built on 3.3 should be compatible with the new update manager.  Below is the trace:

 

 

!ENTRY org.eclipse.core.jobs 4 2 2008-04-24 11:50:52.328

!MESSAGE An internal error occurred during: "Fetching children of Known Repositories".

!STACK 0

java.lang.NullPointerException

        at org.eclipse.equinox.internal.p2.metadata.generator.features.DigestParser.parse(DigestParser.java:83)

        at org.eclipse.equinox.internal.p2.updatesite.UpdateSite.loadFeaturesFromDigest(UpdateSite.java:295)

        at org.eclipse.equinox.internal.p2.updatesite.UpdateSite.loadFeatures(UpdateSite.java:279)

        at org.eclipse.equinox.internal.p2.updatesite.metadata.UpdateSiteMetadataRepository.generateMetadata(UpdateSiteMetadataRepository.java:84)

        at org.eclipse.equinox.internal.p2.updatesite.metadata.UpdateSiteMetadataRepository.<init>(UpdateSiteMetadataRepository.java:66)

        at org.eclipse.equinox.internal.p2.updatesite.metadata.UpdateSiteMetadataRepositoryFactory.load(UpdateSiteMetadataRepositoryFactory.java:43)

        at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:382)

        at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:358)

        at org.eclipse.equinox.internal.provisional.p2.ui.query.QueryableMetadataRepositoryManager.query(QueryableMetadataRepositoryManager.java:89)

        at org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchChildren(RemoteQueriedElement.java:56)

        at org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchDeferredChildren(RemoteQueriedElement.java:35)

        at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:234)

        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

 

 

 

Is this an issue with the Eclipse framework or how my update site is built?  Thanks.

 

- Ryan Huff