Re: [cross-project-issues-dev] Indigo M7 repository is ready

[David M Williams <david_williams@xxxxxxxxxx>]

I've not seen that "NoClassDefFoundError" but don't often test "return to an update site after install" (in other words, the fact I've not seen it doesn't mean much ... I wonder if related to bug 344977, which John mentioned on this list ... sounds like same use-case path, but bug doesn't mention that particular error.

As for your other questions ... buried at the end of your note:

> 1. No matter what we do to our project update sites, the Indigo
> provisioning will not be broken. (Please don't ask me why I ask...)

Pretty much. There is indirection used for a few sites, but wouldn't be "your" site (it is only for Eclipse (platform) project and EPP features site).

> 2. Conversely, once M7 is out (i.e. now) what was there at that time
> is exactly what people will get until RC1 even if that isn't what we'd like.

Again, pretty much ... but ... you'll notice that once something is installed from /releases/indigo you'll get a bunch more software repository sites automatically added to your client. I _think_ none of those are enabled by default (shouldn't be) but users could go and enable one, and therefore has a chance to get something more recent from one of those enabled sites.

I'll be quick to point out though, since you say "no matter what we do to our project update site", that 1) it'd be easy for you to break upcoming aggregation builds! and 2) projects are encouraged to maintain your own software repository sites, even if duplicated in "indigo" repository, so your users can get fixes from there, or extra things from there, not in the indigo common repository, and 2) so future aggregation builds/rebuilds will not be broken.

Hope this helps,




Miles Parker ---05/06/2011 07:01:56 PM---I'm wondering if anyone else is seeing: java.lang.NoClassDefFoundError: Could not initialize class o

From: Miles Parker <milesparker@xxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 05/06/2011 07:01 PM
Subject: Re: [cross-project-issues-dev] Indigo M7 repository is ready
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

---

I'm wondering if anyone else is seeing:

java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.httpclient.HttpClient
at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientBrowseFileTransferFactory$1.sendBrowseRequest(HttpClientBrowseFileTransferFactory.java:53)
at org.eclipse.ecf.provider.filetransfer.browse.MultiProtocolFileSystemBrowserAdapter.sendBrowseRequest(MultiProtocolFileSystemBrowserAdapter.java:95)
at org.eclipse.equinox.internal.p2.transport.ecf.FileInfoReader.sendBrowseRequest(FileInfoReader.java:186)
at org.eclipse.equinox.internal.p2.transport.ecf.FileInfoReader.getRemoteFiles(FileInfoReader.java:112)
at org.eclipse.equinox.internal.p2.transport.ecf.FileInfoReader.getRemoteFile(FileInfoReader.java:128)
at org.eclipse.equinox.internal.p2.transport.ecf.FileInfoReader.getLastModified(FileInfoReader.java:133)
at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.getLastModified(RepositoryTransport.java:203)
at org.eclipse.equinox.internal.p2.repository.CacheManager.createCache(CacheManager.java:134)
at org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.getLocalFile(SimpleMetadataRepositoryFactory.java:66)
at org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.load(SimpleMetadataRepositoryFactory.java:88)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:746)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:651)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117)
at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102)
at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:82)
at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

org.eclipse.equinox.p2.core.ProvisionException: Error while reading from repository: http://download.eclipse.org/releases/staging/site.xml.
at org.eclipse.equinox.internal.p2.updatesite.UpdateSite.loadActualSiteFile(UpdateSite.java:233)
at org.eclipse.equinox.internal.p2.updatesite.UpdateSite.load(UpdateSite.java:144)
at org.eclipse.equinox.internal.p2.updatesite.metadata.UpdateSiteMetadataRepositoryFactory.initializeRepository(UpdateSiteMetadataRepositoryFactory.java:87)
at org.eclipse.equinox.internal.p2.updatesite.metadata.UpdateSiteMetadataRepositoryFactory.load(UpdateSiteMetadataRepositoryFactory.java:56)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:746)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:651)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117)
at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102)
at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:82)
at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

When returning to update sites after an install.

In a hopefully *completely* unrelated topic, I just wanted to check my understanding of the way things are set up. I think that the aggregator is set up to mirror all artifacts into the Indigo repos proper and never uses indirection, correct? That is:

1. No matter what we do to our project update sites, the Indigo provisioning will not be broken. (Please don't ask me why I ask...)
2. Conversely, once M7 is out (i.e. now) what was there at that time is exactly what people will get until RC1 even if that isn't what we'd like.

I mean, I realize that that is why they call it a "Milestone" but I wanted to be sure that the above was correct. :)

cheers,

Miles


On May 4, 2011, at 6:45 PM, David M Williams wrote:

While Papyrus isn't in it ... everything else is, so I suggest we declare this repository done, create the EPP packages ... and move on towards RC1.

But, feel free to disagree or let us know if blocking issues are found.

I have disabled the aggregation builds for now, to help avoid confusion, so if anyone does require a rebuild, please ask and explain here on this list.

Remember to enable only the staging repository,
http://download.eclipse.org/releases/staging/
to test "pure" M7 ... but enable both it, and the /releases/indigo repository to test what our composite repository will look like on Friday,
which will be a composite of M6 and M7, unless we decide otherwise.

Thanks everyone ...

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev