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...
Related
I just installed eclipse oxygen and I want to program using maven. I´m newbie with maven and I wonder if I need to set up something else, related with the m2 folder.
I would like to install Jersey, but I got the error :
Can't resolve Archetype
org.glassfish.jersey.archetypes:jersey-heroku-webapp:2.21
org.eclipse.core.runtime.CoreException: Could not resolve artifact
I already tried different options, this was my previous post jersey post
I´m looking for other alternatives, and in other posts I read about the folder m2, do I need to do something in there? if so, could you please provide a link with the steps.
Thank you!
The artifact org.glassfish.jersey.archetypes:jersey-heroku-webapp:2.21 is in MavenCentral. If you cannot get it you either:
use a settings.xml which does not allow you do access MavenCentral (by e.g. mirroring it). If you never wrote or copied a settings.xml this will not be the case.
or you have network problems. Your proxy or firewall might restrict the access to MavenCentral. This is especially likely if you are in a company network.
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!
Situation:
I have an Eclipse RCP Application, which I am trying to build with tycho plugin for Eclipse.
When I am executing my Eclipse Application inside of the IDe - the Application is executed normally.
When using tycho to build the Application - the following error is thrown:
The type org.eclipse.swt.widgets.Button cannot be resolved. It is indirectly referenced from required .class files
What I did :
In other cases where a "missing requirenments" exception was thrown, which I found
- a missing transitive plugin-dependency was the reason.
In my case an SWT widget "Button" is missing, so I am trying to import swt.
SWT is platform dependant so I am importing swt inside of the product, as described here.
Anyway, during compilation the error occurs again.
Question:
Do someone have any Idea, how to solve this Problem?
I got the answer from the mailing list (Thnx Jeff MAURY!) - it seems to be a bug of tycho.
Here is a patch available.
For those, who do not know GIT yet, like me:
When checking out the patch on windows use TortoiseGit or MSYGit clients, not the EGit Client - it wont recognize the repository.
Additionally use the https repository, not the git repository - git didn't work for me
And the checkot syntax is git clone https://git.eclipse.org/r/tycho/org.eclipse.tycho.git - https://git.eclipse.org/r/tycho/org.eclipse.tycho.git is the repository URL here
i am using eclipse 3.5 to create a simple plugin bearing an extension point. i built it using headless pde build via ant. the plugin functions properly. i then proceeded to test its extension point by placing my plugin jar into eclipse_home/dropins with intention of eventually creating an extension. but after i start eclipse, i get the following error in its log:
!ENTRY org.eclipse.equinox.p2.core 4 0 2012-03-22 01:00:45.270
!MESSAGE Provisioning exception
!STACK 1
org.eclipse.equinox.internal.provisional.p2.core.ProvisionException: No repository found at file:/C:/eclipse35/dropins/MyPlugin/.
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:380)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:641)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:88)
at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.loadMetadataRepository(Activator.java:90)
at org.eclipse.equinox.internal.p2.reconciler.dropins.DropinsRepositoryListener.getMetadataRepository(DropinsRepositoryListener.java:184)
at org.eclipse.equinox.internal.p2.reconciler.dropins.DropinsRepositoryListener.addRepository(DropinsRepositoryListener.java:79)
at org.eclipse.equinox.internal.p2.reconciler.dropins.DropinsRepositoryListener.added(DropinsRepositoryListener.java:57)
at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.processFile(DirectoryWatcher.java:200)
at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.scanDirectories(DirectoryWatcher.java:161)
at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.poll(DirectoryWatcher.java:108)
at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.watchDropins(Activator.java:491)
at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Activator.java:167)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
i have tried both just placing the plugin jar directly in the dropins directory, as well as using the following directory structure: eclipse_home/dropins/MyPlugin/plugins/myplugin.jar. both approaches work just fine with 3rd party plugins, but not with mine. please let me know what i am doing wrong. thank you!
It seems like two problems. The "no repository found" error message looks like this problem. And then there is the issue with your plugin not starting.
First you should check if the plugin is found.
Then you should check if the plugin is resolved, i.e if all requirements are fulfilled.
If you have the plugin development version of Eclipse, then you can open the plugin registry view. See if your plugin is in the list, if so, then the atleast it has been found. Then right click on it, enable advanced operations, and after that choose diagnose. Some requirement has probably not been fulfilled.
If you dont have the Plugin version of Eclipse, you can use the osgi console. Go to console view, and choose OSGI console in the view menu.
Run command ss to list all plugins, and diag 123 where the number is the id of your plugin to diagnose it.
Also, see a previous answer to a similar question
Edit: Oh, and I have been having some serious problems getting plugins placed in the dropins catalog to work at times... You could try to copy it to the eclipse/plugins catalog directly.
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.