I'm using STS 4.12.0.RELEASE and try to install sonar lint 6.1 plugin from eclipse market place. But received java.lang.IllegalStateException: operation plan must be resolved as the attached image.
Is there any alternative way to install the sonar lint plugin?
Added additional image about failure message
The installation of the SonarLint plugin from the marketplace works for a fresh STS 4.12.0 distribution in general, so this might be a network glitch, stale cached data from the update site, or something in this area.
I would recommend to go to the Preferences -> Install/Update -> Available Update Sites and remove (not just disable) the update site for SonarLint in there, restart, and try again.
Related
I'm using Eclipse Photon and Windows 10 and trying to download the STS version 4 from the marketplace (or by drag and drop) the installation constantly stalls at 49 percent and I get this error:
Any tips or help appreciated!
This looks like a typical network or repository caching issue. I would recommend to go to the Preferences -> Install/Update -> Available Updtae Sites, select the one that is used and press reload. That refreshes the internal repository caches. Then try again the install. You could also delete all those STS-related update sites from that preference and try again the marketplace entry. That should solve the issue.
Reference: Eclipse Marketplace
I'm using Eclipse Neon and SonarQube 5.6.6(LTS). I've install sonarLint version 3.1.0. Following are my question.
In SonarLint whether there is an option to analyze the entire project? I can't able to find such option.
The issue showing in Eclipse reported by sonar lint is different from reported on server. When I'm wantedly creating the sonar issues(based on the rule) in eclipse but SonarLint is not recognizing . why?
From Eclipse I've made the connection to the SonarQube server and the connection was success, Whether it is using the activated quality profile rule?
After resolving the issues, how the issues will be reflected to the sonarQube server ? In case of Maven whether I need to add the sonar properties and sonar-maven plugin and trigger the build?
1. Select your project and in Eclipse's Quick Access, select Analyze - Analyze with SonarLint. You can also assign a keyboard shortcut to this action by going to Window -> Preferences -> General -> Keys.
2. It seems as if you are not running in connected mode. Connecting a SonarQube server is not enough, you also have to bind individual projects. To do this, right click on your project in Eclipse, and select SonarLint -> Bind to a SonarQube project... Search for the name of your project on the server by typing in the box under SonarQube project, as show in the following screenshot:
Once connected, a SonarQube symbol should appear on your project's icon in Eclipse.
3. Once connected, the quality profile of your SonarQube server project will be used.
4. SonarLint only provides on the fly feedback, but does not trigger any analysis server side. Personally I have a clean verify sonar:sonar Maven run configuration for my projects, and run it every now and again within Eclipse.
I recommend reading the SonarLint documentation for more information.
I personally recommend either to change your version or to be sure which configuration really applies to your machine. I had similar problem when i tried to associate my local project with the project name on Sonarqube Server . I was using Eclipse IDE for C/C++ Developers Version: Luna Service Release 2 (4.4.2) with Sonarlint version 4.0 . I uninstalled it(sonarlint) and installed the Sonarlint 3.6 version. After this i could associate my project with Sonarqube Server.
Hope it Helps the main question.
I've just downloaded Spring Tool Suite 3.6.4 (201503100339, Eclipse Luna SR1 (4.4.2)) on Windows 8. I'm attempting to import an existing Gradle project, but this option is not available within the import menu.
Playing a hunch that Gradle support may have been removed, I sought to install it from the Eclipse Marketplace. But when I found "Gradle Integration for Eclipse (4.4) 3.6.4.RELEASE" the only option available was "uninstall", implying that it was already installed.
Is there something I need to do to "Activate" the Gradle tooling?
The Gradle tooling is not installed by default if you download an STS distribution. You should be able to install it from the Eclipse marketplace or the dashboard.
If you are not sure whether this is installed or not, you can check that in the about dialog. There is an option to inspect the installation details.
#Martin - I repeated my last steps, and this time "Gradle Support" installed without incident. I have no clue what is different now, but the error about "connector not available" went away. I now have Gradle support. Thanks for your help! - k
I checked the issue with the Marketplace again and it looks like a limitation of the Eclipse Marketplace client at the moment.
More details:
The Gradle IDE contains three features that should be installed. One of these features is the dashboard - which comes with STS by default. It looks like the marketplace client checks the already installed features and whenever it finds one of the features of the item to be installed in the existing installation, it enables the "uninstall" button. This seems to be the reason why the Gradle IDE entry from the Marketplace is listed as "uninstall".
I filed a bug for this against the Eclipse Marketplace. Lets see that happens. As a workaround, you should be able to install the Gradle tooling from the dashboard or the STS update site directly.
This is the situation: I am the admin of a shared installation of Eclipse, and I want regular users (who do not have write-permission to the installation directory) to be able to update existing plugins. If they try this now they get an error saying something like:
"Your original request has been modified.
[Plugin name] will be ignored because it is already installed, and updates are not permitted.
..."
It works perfectly well for users to install new plugins, just not update existing ones.
Steps to reproduce:
Install Eclipse (I've tried, among others, Eclipse Classic 3.6.2 and
3.7, in Linux SUSE Enterprise 10).
As an admin with write-permission to the installation directory, install a plugin, e.g. EGit 1.0 from
http://download.eclipse.org/egit/updates-1.0
As a user (without
write-permission), try to install a newer version of the plugin (e.g.
EGit 1.3 from http://download.eclipse.org/egit/updates-1.3).
Perhaps related: If a regular user opens "About Eclipse SDK --> Installation Details --> Installed Software", the "Update" and "Uninstall" buttons are greyed out for every item on the list, though they are not for the admin.
So my questions are: Is this on purpose? and: Can I do something to allow users to update plugins?
I just have the same error. I removed the plugin of the update configuration file (but it's not the best solution)
%eclipse_home%\configuration\org.eclipse.update\platform.xml
This error is easily reproducible, install a plugin directly into the main configuration directory, and do a manual plugin install, like :
%eclipse_home%\eclipse.exe -configuration %eclipse_home%\configuration
Install > New software ...
So, the update will not working if you do that.
To correctly install a plugin, you just have to drop it into the "dropins" dir, like :
%eclipse_home%\configuration\dropins\yourplugindir
Then, the user could use it, or do an update
(init configuration) %eclipse_home%\eclipse.exe -initialize
(refresh workspace) %eclipse_home%\eclipse.exe -clean
%eclipse_home%\eclipse.exe
Install > New software ...
The Eclipse runtime options
Best regards,
When I select "Help->Check for Updates" in eclipse, I get the following error message at the bottom of the window. From this message "Only one of the following can be installed at once: " it appears I have multiple copies of the same component installed. Under "About Eclipse SDK=>Installation Details" I found at least two instances of Equinox P2 Provisioning: under "Eclipse SDK" and "PHP Development Tools".
Any suggestions on how to get this resolved would be much appreciated.
I'm running eclipse helios 3.6.1 on CentOS 5.2.
Cannot complete the install because of a conflicting dependency.
Software being installed: Eclipse SDK 3.6.2.M20110210-1200 (org.eclipse.sdk.ide 3.6.2.M20110210-1200)
Software currently installed: Shared profile 1.0.0.1288623084982 (SharedProfile_SDKProfile 1.0.0.1288623084982)
Only one of the following can be installed at once:
Equinox p2 Provisioning 2.0.1.r361_v20100903-897HFZFFZRuSD2LMtVxyz0Vr (org.eclipse.equinox.p2.user.ui.feature.jar 2.0.1.r361_v20100903-897HFZFFZRuSD2LMtVxyz0Vr)
Equinox p2 Provisioning 2.0.0.v20100503-897HFZ-FdHjO2NQo0sD_Nt (org.eclipse.equinox.p2.user.ui.feature.jar 2.0.0.v20100503-897HFZ-FdHjO2NQo0sD_Nt)
Equinox p2 Provisioning 2.0.1.r361_v20100903-897HFa-FX0z-z-ntoaavz0JPX628 (org.eclipse.equinox.p2.user.ui.feature.jar 2.0.1.r361_v20100903-897HFa-FX0z-z-ntoaavz0JPX628)
Cannot satisfy dependency:
From: Shared profile 1.0.0.1288623084982 (SharedProfile_SDKProfile 1.0.0.1288623084982)
To: org.eclipse.equinox.p2.user.ui.feature.jar [2.0.1.r361_v20100903-897HFZFFZRuSD2LMtVxyz0Vr]
Cannot satisfy dependency:
From: Equinox p2 Provisioning 2.0.1.r361_v20100903-897HFa-FX0z-z-ntoaavz0JPX628 (org.eclipse.equinox.p2.user.ui.feature.group 2.0.1.r361_v20100903-897HFa-FX0z-z-ntoaavz0JPX628)
To: org.eclipse.equinox.p2.user.ui.feature.jar [2.0.1.r361_v20100903-897HFa-FX0z-z-ntoaavz0JPX628]
Cannot satisfy dependency:
From: Eclipse SDK 3.6.2.M20110210-1200 (org.eclipse.sdk.ide 3.6.2.M20110210-1200)
To: org.eclipse.equinox.p2.user.ui.feature.group [2.0.1.r361_v20100903-897HFa-FX0z-z-ntoaavz0JPX628]
Update 9/15: I read somewhere that this may be due to a permissions issue and that I should run eclipse as root and perform the update. I was indeed able to complete the 3.6.2 SDK update as root but then afterwards all of my add-on components (e.g. subclipse, PDT, etc.) were gone.
You are getting this message because you are trying to install into a read-only (shared) location. The indication is at this line:
Software currently installed: Shared profile 1.0.0.1288623084982 (SharedProfile_SDKProfile 1.0.0.1288623084982)
The reason why there is a failure is that your install plan would remove an old version of a feature that is part of the shared install. Since a shared install cannot be changed, you get the conflicting dependency.
As it happens, I am working on a patch for exactly this bug. See:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=332158
The fix would not allow you to install in this situation, but it would at least provide a better error message for you.
I got this message or something similar because I had installed Eclipse to my C: drive on Windows 7. Trying to do an update required escalation but Eclipse wasn't prompting me. When I restarted Eclipse using "Run as Administrator", it had the proper permissions to continue and it let me upgrade.
Cannot satisfy dependency:
From: Eclipse SDK 3.6.2.M20110210-1200
It needs a dependency that only exists in the update site for Helios 3.6.2 and you are running 3.6.1. You can either upgrade to the latest version of Helios (or better yet, Indigo) or add the update sites. I don't know the URL's off the top of my head, but you can try this method:
Download a fresh copy of Helios and install it to a separate folder. Open up help>install new software and click "available software sites". Then export the default sites and import them into your existing Eclipse installation. Your plugins should now update correctly.
EDIT: add this to your update sites: http://download.eclipse.org/eclipse/updates/3.6/
Note that shared install have now (upcoming Eclipse 4.3, 2013) a way to:
Detect shared install changes:
When Eclipse is running in a read-only folder (also known as shared install) and the read-only installation has changed (e.g. new plugins installed, new version of Eclipse installed), Eclipse will now detect this change and warn that your personal additional plugins have been uninstalled.
Provide a Migration Wizard:
Eclipse now includes a migration wizard to help users through the re-ininstallation of their plug-ins.
This wizard is presented in two situations.
First, when a read-only installation of Eclipse is being changed (i.e. Eclipse is being updated or plugins are added / remove),
second when a new read-only installation of Eclipse is run for the first time.
See also "Shared installs just got better!" for more:
Building on this support, we've also decided to assist users in re-importing their plug-ins from a previous read-only installation.
The reason is simple, many corporations chose to deploy new versions of Eclipse in different folders. This is required to give teams the ability to adopt Eclipse at their own pace, but it also means that when users start using a new Eclipse install, they need to re-install the plug-ins they had installed on their own.
Of course users could use the import/export feature provided by p2, but the time wasted by the user wondering why the plug-ins have vanished and then figuring out what to re-install can be significant, which is why in such situation we are also presenting the migration wizard.