An error occurred while collecting items to be installed
session context was:(profile=epp.package.committers, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Unable to read repository at http://beust.com/eclipse/updatesites/6.11.0.201703011520/plugins/org.testng.eclipse_6.11.0.201703011520.jar.
Read timed out
I have tried every solution that was available on google...Nothing worked. Please help!!
if you still have the installation issue, i guess there might be some firewall/network settings impacts that.
as a workaround, you can download the zipped update-site to you local, and install from the archive file.
see the list of zipped update-site: https://github.com/cbeust/testng-eclipse#update-sites
Related
I tried to import the spring starter pom.xml in my Eclipse Luna. I was getting the below error. I dont remember getting this error before after I installed and reinstalled it. Any thoughts
The type org.springframework.context.ConfigurableApplicationContext cannot be resolved. It is indirectly referenced from required .class files
I tried the below thread, but didnt help.
https://java.net/jira/browse/PINEAPPLE-764
Your maven cache seems corrupted. You need to purge local repository.
See my answer at this link for the detailed steps to solve this problem.
I am trying to follow some existing tutorials on Hadoop that I found online.
I have installed cloudera and am using it as the setup environment for all of the work. However when I try to create a Maven project in Eclipse, I end up having issues referencing to the quickstart archetype.
The error I get is the following:
'Creating maven-archetype-quickstart' has encountered a problem.
Could not resolve archetype org.apache.maven.archetypes:maven-archetype-quickstart:RELEASE from any of the configured repositories
The issue seems to be linked with the ~/.m2/ folder. My settings.xml file has been set up per the tutorial and links to the online repositories.
Could not write artifact lastUpdated status /home/cloudera/.m2/repository/org/... (Permission denied)
Please note that I created the whole directory .m2/ as it did not exist. I am running out of ideas, maven is clearly installed on the VM. I am just unsure why everything is referenced back to ~/.m2/ which did not exist and had to be created (and therefore isn't populated).
Whatever help would be appreciated, thanks again for your time!
I am experiencing difficulty in the retrieval of repositories from URL sites for eclipse kepler. I have several URL's that I am attempting to fetch to no avail; they are mostly zip files, a few check sums, and a few tar bzip files. Each URL, when you navigate to it in a web browser, has intact files and none of them are broken sites. This tells me that there must be some kind of error in my eclipse build regarding its repository management. I am sharing my current build with a colleague who is not experiencing these repository issues, which is what has led me to post a question here.
I am going to keep tracing the stack, but I would greatly appreciate any cues!
org.eclipse.equinox.p2.core.ProvisionException: No repository found at http://googleappengine.googlecode.com/files/appengine-java-sdk-1.8.1.1.ziptype%2520or%2520select%2520a%2520site.
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692)
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:83)
at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
And here is another example of a repository that I am trying to access:
org.eclipse.equinox.p2.core.ProvisionException: No repository found at http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/2.0/runtimes/xulrunner-2.0.en-US.linux-i686.tar.bz2.
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692)
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:83)
at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Does someone mind telling me why this provision exception occurs? Am I missing critical plugins for eclipse? I'd be interested to know if there is a way to automate the resolution of these exceptions in finding the repositories as well...
I am trying to export an Xtext project as an Eclipse Product. The launch configuration works flawlessly if launched from within Eclipse, but I am unable to export it to make a self-contained product. I get:
An error occurred while collecting items to be installed
session context was:(profile=profile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Problems downloading artifact: osgi.bundle,org.eclipse.sdk,4.2.0.v201206081400.
org.eclipse.sdk-4.2.0.v201206081400 is already imported as project in the workspace. I'm trying to export using "all workspace and enabled target plugin" rather than selecting the plugins one by one.
I'm on Linux 64bit (Sabayon).
Building for the running platform should not be a problem. Did you create a product and try to run that in a eclipse? I suspect you are running the project as an eclipse instance not from the product project
Can you make sure you change the splash screen on your product and run it in eclipse?
If you see the splash screen you changed and it works, it should be
working when you try to build the product.
If not you need to check what is missing between run config and the
product configuration.
I have just download the eclipse and go to Help -> Install new Software, choose the Helios - http://download.eclipse.org/releases/helios
as the repository, then the exception
coms out as ,
org.eclipse.equinox.p2.core.ProvisionException:
Unable to connect to repository
http://download.eclipse.org/releases/helios/compositeContent.jar
at
org.eclipse.equinox.internal.p2.repository.CacheManager.updateCache(CacheManager.java:357)
at
org.eclipse.equinox.internal.p2.repository.CacheManager.createCache(CacheManager.java:205)
at
org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.getLocalFile(CompositeMetadataRepositoryFactory.java:74)
at
org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:99)
at
org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
at
I am sure I could download the compositeContent.jar file from http://download.eclipse.org/releases/helios/compositeContent.jar for I have downloaded it within the firefox.
So what's wrong?
Since eclipse would typically catch a completely failed connection, your error suggests you are getting part of the update site but not all of it. There's quite a few files in an update site, mainly xml and jars.
If a proxy isn't the issue as Bobby suggested i would first try creating a new workspace and updating then to make sure eclipse hasnt cached anything corrupt. Otherwise you might have to resort to creating a local mirror of the update site.