When I try to install Eclipse plugins, I often get an error with details like:
An error occurred while collecting
items to be installed No repository
found containing:
org.eclipse.equinox.concurrent/osgi.bundle/1.0.0.v20090520-1800
This is clearly a bug in Eclipse. The bundle I'm installing doesn't need any special version of anything, it's just a profiler plugin that works in literally any build of Eclipse 3.4. Refusing to install my plugin is not an acceptable course of action. Eclipse should stop showing this message and install the plugin.
I'm not sure exactly what error the Eclipse developers made, but I can see that the version compatibility checker is absolutely strict, and it should not be. Either it is incorrectly evaluating the required bundles, and failing as a result of its own blunder, or the version requirements of the bundles are loosely defined in a way that the version checker does not really understand.
So, is there a way to simply disable this version checker? The thing is crippling my Eclipse install. Frankly, Eclipse would be better if the thing were completely deleted from the application. We only need it to choose the correct version of existing plugins for binding OSGi services. We don't need our development tools to kibitz about whether a plugin seems proper.
Thanks in advance for any suggestions.
Byron
As mentioned in the wiki
The message indicates that the Eclipse provisioning system P2 has found meta data to install a plug-in but can not locate an artifact repository that provides the required downloads
It is suggested to remove update sites and re-add the same update sites, to trigger a refresh, but in your case, it is not your plugin update site which is involved.
There is indeed a bug (236437) with Eclipse 3.4 about "Lost artifact repositories". It has been solved in Eclipse3.5, but if you cannot use that version, there may be a workaround:
1) export the update site listing to bookmarks.xml file (Software Updates->Manage Sites->Export)
2) stop eclipse
3) remove configuration/.settings/org.eclipse.equinox.p2.*.prefs files
4) start eclipse
5) import the bookmarks.xml file (Software Updates->Manage sites->Import) that was exported in step 1
Comment #59 helped me fix my updating problem, thanks!
Though, I think maybe it was enough to just delete the configuration/.settings/org.eclipse.equinox.p2.*.prefs files as I have a feeling that the problem was already resolved before I imported the bookmarks file (things happened a bit in parallel for me here).
Note for Eclipse3.5 users:
I am seeing this in 3.5.1 when trying to install stuff from an old style update
site when I include site.xml:
http://www.perforce.com/downloads/http/p4-wsad/install/site.xml
If I remove site.xml I can install things fine.
Related
Within the context of upgrading plugins explain how to resolve plugin dependencies when NetBeans user interface's reports specific missing dependencies, yet these do not resolve with a google search or are unmentioned in the netbeans FAQ.
The practical example leading me to ask this question was when I attempted to install an in-development-plugin org-netbeans-modules-htmlprojects.nbm. It requires General Queries API v1.24 and I have v1.19.1.
Have a look at the bug report that mentions the nbm, it's for version 7. This also means that the mentioned version for GQA is also version 7 specific.
You best choice is probably to upgrade to version 7, it has some nice improvements over version 6.9 like HTML5 support. As a new install picks up the configuration of an installed previous version upgrading shouldn't be a lot of work.
EDIT based on restated question:
The short form: you cannot, it's not meant to work that way.
The long form: due to what happened here and the inner workings of Netbeans the error message was less clear than it could have been...
you downloaded a module for a higher version than the installed one
Netbeans' nbm deployment descriptor states dependencies on editor modules, not on editor versions - see inside the nbm which is actually a ZIP file Info/info.xml, manifest element, OpenIDE-Module-Module-Dependencies attribute.
Normally that error would not happen, as the version of the nbm will normally match the editor version, and the dependencies should either be satisfied or satisfiable by on-the-fly installation of the missing dependencies.
Bootstrapping Eclipse on new machines is such a time consuming process, you wind up asking yourself whether you really need each plugin. But there all handy, and help develop consistent habits.
Eclipse bootstrapping problems include:
Explaining / documenting what needs to happen
The actual time pasting in the right URLs and downloading
Version compatibility and dependencies
Eclipse likes to restart after each one
The changeover to the Eclipse Marketplace means that some plugins and instructions you find on the web tend to be inconsistent, depending on when they were written.
The Licenses... over and over and over... yes, yes, yes... I understand that the person installing needs to be aware of it, and have a chance to review them, but there's got to be a better way.
It'd be nice to have "patch file" (either binary or meta) that spells out what I want to add on top of stock Eclipse installation. I'd really like to find (or create) a 1 or 2 step process that sets up Eclipse, plus a favorite batch of plugins:
subclipse
m2eclipse
jetty support like runjettyrun
android sdk and plugin (or at least just the plugin)
aspectj
Web Objects / WOLiops
python, other langs
JVM Monitor, maybe EclEmma
probably a git plugin pretty soon.
Does command line maven help with any of this? It seems like its repository management would fit at least part of the functionality.
On a machine with an Eclipse installation matching your needs use File -> Export -> Install -> Installed software items to file. Import the generated file using the same menu on all other machines.
As Scott says, a good approach is to simply package a fully prepared Eclipse installation once all the plugins you need are installed. The downside is that you have to update most plugins afterwards.
Another option is to use Yoxos. With it, you can create a profile and configure it with all the plugins you need (and apparently Yoxos can do more than that).
Finally, this page might interest you concerning the configuration side of things.
Solution 1 is too search for more advanced Eclipse distributions.
For example, STS (Spring Tool Suite) comes with
AspectJ
EGit
m2e
(and of course) Spring IDE
One small trick can be done with m2e-android - Android Configurator for M2E Maven Integration. If installing it on clean Eclipse, it will also automatically resolve to install :
m2e
Android Developer Tools (ADT)
Is it possible to disable or remove the built-in Java compiler from an Eclipse installation?
I would like to use the XML editing and validation features of Eclipse in an environment that forbids installation of compilers. Can the compiler be disabled/removed without breaking the XML editing and validation functions? How?
Comments in this related question suggest that it can't be done, but I don't need the Java development features of Eclipse (and don't expect them to work without the compiler).
Yes, it is certainly possible to create an Eclipse install without the Java compiler (or JDT to be specific). The real question is whether the XML tools have an indirect dependency on JDT that will pull that back in.
Here is what I would try...
Download Eclipse Platform zip. You can get it from this URL:
http://download.eclipse.org/eclipse/downloads/
Look under the Latest Releases heading. You will want to download something stable. The latest release now is 3.6.1...
http://download.eclipse.org/eclipse/downloads/drops/R-3.6.1-201009090800/index.php
Now find a heading called "Platform Runtime Binary" and download the zip that's right for your platform. Verify that file name is "eclipse-platform-[version]-[platform].zip". If it isn't you've downloaded the wrong thing.
Unzip it as you usually would an Eclipse distro. You now have a runnable Eclipse install, minus any and all interesting IDE functionality. In particular, there is no JDT.
Now it's time to install XML tools. Go to Help->Install New Software->Add and use this URL for the repository: http://download.eclipse.org/releases/helios/
Uncheck "contact all update sites during install to find required software".
Type in XML into the filter field. The feature you want is called "Eclipse XML Editors and Tools". Select it and hit finish.
Assuming it installs correctly, you will want to confirm that it didn't silently pull in JDT. Look at your Eclipse install in the plugins directory. See if you have org.eclipse.jdt.core plugin present. That's where the Java compiler lives.
Good luck and if you run into problems, a good place to ask follow-up questions is on the following forum. There a few people hanging out there that are pretty dedicated to the notion of some day creating an "XML IDE" eclipse distribution, so they should be glad to help you out.
http://www.eclipse.org/forums/index.php?t=thread&frm_id=88&
I would ideally suggest you to move away from eclipse, coz there are a ton of tools (Quanta Plus IDE, Bluefish etc) that provide you with great XML editing and validation feature.
However, this forum might help you -> http://www.eclipsezone.com/eclipse/forums/t40126.html.
You can un-tick Project > Build Automatically for automatic builds not to happen and even remove the buttons with the Run and Debug functionality in order not to press them accidentally.
I'm trying to install the WTP (web platform tools) to my Eclipse installation so I can get the XSL transformations working. The base Eclipse they installed for me here was the plain Java IDE (the splash screen says "Ganymede" if that means anything). Looking at this site, the URL to get the download should be here: http://download.eclipse.org/webtools/updates/ ...But when I give that URL to the Eclipse update manager, I get an error telling me: "No repository found at http://download.eclipse.org/webtools/updates/"
Anyone else had this problem? Anyone know what might be up? Anyone know how to get the xsl-transform plugin installed?
EDIT:
I should have mentioned before that I want to find a way to do this without installing any new instances of Eclipse. This process will eventually be sent to several other developers who already have Eclipse (same version that I'm testing with) and I'd rather just do an in-place upgrade rather than have everyone go and install a new product.
UPDATE:
I found another plugin, Xcarecrows 4 XML which can also do XSL transforms. The interface is ugly and seems more than a little quirky, but it's also a small download, and at least it runs and transforms. Unless I can find an easy way to get WTP working, I'll probably just stick with this.
You can try and install WTP through the main Ganymede update site:
http://download.eclipse.org/releases/ganymede/
Or you can download the latest Java EE bundle and use that instead of your current Eclipse
(do NOT unpack it on top of your current Eclipse, but unpack it elsewhere, to test that second installation: it will come with WTP inside)
Note: check then "How do I start Eclipse" to point to your existing workspace in order to see all your previous project in your new Eclipse installation.
As mentioned in your link, XSL Tools is now part of WTP (for Eclipse 3.5 Galileo), and that may explain why your Eclipse Ganymede (3.4) might not interpret correctly the P2 update site for WTP (P2 being the new Eclipse provisioning mechanism introduced late in the 3.4 release cycle)
For Eclipse 3.5, you have an XSL Tools installation illustrated here:
But Eclipse3.4 is more likely to be compatible with XSLT0.5 and you will need a separate installation, because "XSL Tools" wasn't yet part of WTP.
I am not sure, however, where to find such an installation package within the Eclipse projects.
Use the following update site :
For Juno :
http://download.eclipse.org/webtools/repository/juno/
For Indigo :
http://download.eclipse.org/webtools/repository/indigo/
I'm assuming you don't have any firewall exceptions for Eclipse right?
The site for the WTP update is indeed the one you've listed. Maybe post a screenshot? You've added it specifically to your remote update site list?
Either way try a manual update which should be more reliable and get you up and running for now.
All-In-One Update (Eclipse IDE included):
Go to the Eclipse Download site.
Grab the all-in-one package: Eclipse IDE for Java EE Developers
Install, have a coffee and enjoy. (WTP is included)
Manual Update your existing installation of Eclipse:
Download the applicable WTP source package to your desktop
Shutdown Eclipse
Extract the package to your Eclipse installation directory
Startup Eclipse. (WTP is now available)
Follow the steps in the FAQ at http://wiki.eclipse.org/WTP_FAQ#How_do_I_install_WTP.3F .
Are you behind a proxy? If so, you need to make sure you configure your proxy settings in Eclipse.
Window > Preferences
General > Network Connections
Ok, I can probably get it working if I do a clean install of Eclipse. I can do that on my machine, but not the other team members' machines (at least not without going through many emails and paper work) so I'm going to say that XCarecrows 4 XML is the solution. It is able to do XSL transformations in Eclipse 3.4 and doesn't require anything else to be installed. Since XSLT is all I need, the plugin will do.
you can use the marketplace:
https://marketplace.eclipse.org/content/eclipse-java-ee-developer-tools-0
like the site says:
Drag to Install!Drag to your running Eclipse Workspace.
I'm trying to install an Eclipse plugin for Mylyn/Fogbugz, and I get the following error when I try either EclipseBugz or Foglyn:
Cannot find a solution satisfying the following requirements Match[requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.swt
I'm using Eclipse 3.4.1
what other update sites do you have enabled in your Eclipse installation?
I had similar problem when upgrading from older Mylyn, and found out that it helps to disable other updates sites. When installing new plugins, or even updating old ones, Eclipse has a tendency to contact all enabled update sites. I don't know what exactly it is trying to do, but it helped me to disable all sites except one I wanted to use.
Btw, Eclipse 3.5M6 has option to use only selected update site -- it is great help when updating/installing plugins. I cannot wait to see Eclipse 3.5 final released, just for this feature.
Eclipse plungins require Equinox UI for dependency.Please read Equinox installer .I hope can help you. : )