Firstly may I say that I am probably doing something completely wrong.
I have an update site where I am able install plug-ins successfully using Eclipse Indigo using the Help -> Install New Software... feature.
However, I now want to add a dependency on the same update site by using a target definition.
So, I create a new Target Definition file and add a new Software Site, and reference the same site as I did above.
The problem being that I am unable to retrieve any plug-ins. It just gives me the error:
0 plug-ins available.
Missing requirement: Immutify Eclipse Utilities 1.1.1.201105200936 (org.immutify.eclipse.util.1.1.1.201105200936) requires 'bundle.org.eclipse.ui 3.4.0' but it could not be found
Just wondering why it works on the Install New Software option but not on the software site option of the Target Definition.
Any help would be greatly appreciated.
The option "Include required software" must not be checked. Here is an example of target definition that shows the steps to follow.
http://wiki.eclipse.org/EIG:Add_to_Target_Platform
Related
I had made an maven project and it worked fine.
Then I installed plugins
EclEmma Java Code Coverage,
PHP Development Tools (PDT),
Eclipse.orgSonarQube
Then I worked on some other project. When I again wanted to create an maven project,it threw the following error window which said
The selected wizard could not be started
reason
plug-in org.eclipse.m2e.core.ui was unable to load class
org.eclipse.m2e.core.ui.internal wizards.MavenProjectWizard
Removed SonarQube plugin .This solved the issue.
Now it works all fine.
But is there any other solution to this problem since I have to use sonar.
Click on eclipse help tab and open installation details search sonar and remove all related plugins.
That's not quite the right characterization of what it says on the page,Please check your .log file /path/workspace/.metadata/
Find the correct plugin which is causing this problem and update to compatible version of the plugin with eclipse version.
To find the hidden files in the workspace use Ctrl+H
I had the same problem, and I've tried so many solutions. But what I did to solve the problem, is that I just upgraded my Eclipse IDE (2019-06 to 2020-03) by following these steps (from https://wiki.eclipse.org/FAQ_How_do_I_upgrade_Eclipse_IDE%3F) :
You first need to add the new release's repository as follows:
1-1. Window > Preferences > Install/Update > Available Software Sites
1-2. Click 'Add'
1-3. Enter the URL https://download.eclipse.org/releases/2020-03/
1-4. Click 'Ok'
Help > Check for Updates
If updates are found, proceed through the install wizard and restart the IDE when
prompted. Otherwise, read carefully the error message to find out which component
is conflicting and establish your resolution strategy.
Note that the start splash screen may be cached and will not necessarily be
updated to the latest version after the IDE is restarted. Performing a full
relaunch should display the new version number.
I have a number of tools that I typically install with Eclipse, such as Subversive, PMD, EclEmma, etc. Every time I update Eclipse, I have to manually go through and add each of the tools as well. Is there a way to package the tools so I can install them together rather than individually?
I know of two possible solutions - none of them exactly what you ask for, but...
Use the Export wizard "Install" -> "Installed Software Items to File" to create a descriptive file with the features and update site you use. You get to choose which features to include. Also note that the generated p2f file does not include the binary features and plug-ins themselves - just a descriptive reference. (I should say, that I have had some problems with the corresponding import wizard, but YMMV...)
Alternatively, you can use the import wizard "Install" -> "From Existing Installation" to install features from an old(er) Eclipse installation into the new(er) Eclipse installation. It is a one time operation, and you can then update the installed features the usual way via the appropriate update sites (these are usually installed automaticaly).
Personally, I use the second method, as I then don't have to keep updating the p2f file whenever I find some new interesting features and - as noted above - the import wizard doesn't always work as I would expect.
I keep the old Eclipse installation around for some time anyway to ensure I have something to fall back on in case of problems...
First thing that comes to me is downloading every plugin you need. Store it in a folder and in the Eclipse Update dialog, select that folder in place of the URL.
Cannot remember if you also need to compile some sort of XML list of plugins installed.
With this setup, each time you install Eclipse, simply you use its update procedure and install every package you find using as Update Url your directory.
PS: Take a good look at this excellent question here on SO
In my project we control the plug-ins through the "Manage Configuration" possibility.
Downloaded plu-ins etc. are loaded thorugh an extension point from a file location (managed by SVN)
This has proven to be a reliable way of making sure all developers in a team share the same configuration.
I am now updating our project to Juno, and even after enabling the "Classic Update" in preferences, the menu item Help->Software Update->Manage Configuration is missing.
It also seems to be missing in the documentation for juno at http://help.eclipse.org/juno/index.jsp
Any help?
The Update Manager was deprecated a while ago, and has finally been removed in Juno (4.2). You can use the p2 director to perform command-line based installs.
There are other command line apps that can assist with mirroring features in existing update sites to a local directory that can be shared within a company or creating a composite repo that points off to multiple separate update sites (kinda one-stop-shopping) and even publishers that can take featuers and plugins without metadata and prep them for use with the p2 director.
EDIT: A quick tour of options is available here: http://pweclipse.blogspot.ca/2011/06/p2-cheatsheet.html
I'm trying to get the GNATbench plugin to work with Eclipse. I put the plugin and feature files in the correct places. I restart Eclipse and I am now given the option to create a new Ada project but when I try to do it I get this error:
The selected wizard could not be started. Plug-in com.adacore.gnatbench.cdt was unable to load class
com.adacore.gnatbench.ui.internal.wizards.NewAdaProject. An error
occurred while automatically activating bundle
com.adacore.gnatbench.ui (235).
Any idea what is causing this?
This is the issue you'll see if you attempt to use GNATbench with the 64-bit version of Eclipse. As the system requirements note in the readme, it's only compatible with the 32-bit version. I just did a quick test, which confirmed the issue.
I checked the README file of this plugin, it says this is required:
"C/C++ Development Tools (CDT) plug-in for Eclipse 3.5.x or 3.6.x"
Have you installed that?
The other important thing is that the downloaded archive file is actually a P2 repository installable file. In this case I would unzip a new eclipse (or remove manually the related plugins you copied over, this is the hard way), start it, click on help/install new software, click add, select archive, point to your downloaded GNATbench zip file, select the 2 features appearing on the avail "software" list and continue the wizard normally (next, finish...). If there is a version problem the wizard should "validate" it.
There was a plugin for Ada called Hibachi, IIRC... I'm not sure where it stands on development or completeness though.
I'm building an Eclipse RCP application, and am in the process of setting up the target platform.
In "Eclipse Rich Client Platform" 2nd edition it is noted that one should uncheck the "include required software" option when adding the RCP SDK to the target definition, and install the Delta Pack. This is mentioned across the web as well.
A second option, however, is to uncheck the "include required software" option, so that one can select "include all environments". This isn't mentioned in the book, but it is mentioned acros the web.
So my question basically is: When unchecking the "include required software", should I then (in terms of a "best practice" or similar)
leave the "include all environments" unchecked, and install a Delta Pack, or
check the "include all environments" option?
And furthermore, if 2. is preferrable, do I still have to install the Delta Pack, or is checking the option "include all environments" a full replacement for installing a Delta Pack?
Further info that might (?) influence answers: I plan to build with Tycho...
Many thanks in advance to all who help me!
I have not actually used this (because it's very new), but I think your suspicions are correct according to the documentation. Option 2 is the best choice and you therefore don't need the delta pack.
The delta pack has been around for ages and that's how you get the plugins that are specific for all environments. It looks like with this new thing based on getting stuff from p2 that it can easily get the plugins for all environments that way, eliminating the need to manually install the delta pack.
You can certainly verify this when you build to make sure you have the os-specific plugins for your desired environments (look at the SWT plugins for example).