I made a bad sonar upgrade from 3.4.1 to 3.7.2. I did not upgrade plugins first, and directly upgrade sonar to 3.7.2. After that I found sonar cannot be started due to plugin consistency issue. I removed all plugins and restart sonar. Sonar started normally, but all quality profile rules are empty now, even after I re-installed all plugins from upgrade center. Any ideas?
Best Regards,
This is a known limitation. See http://jira.codehaus.org/browse/SONAR-4642 and http://jira.codehaus.org/browse/SONAR-4764. For now, the only way to get back the default profiles is to export them from a fresh install and import them into your production instance.
Related
To upgrade to a new version, the eclipse FAQ suggests to add a new repository and then install available updates. Upgrading to Neon, the corresponding repository is http://download.eclipse.org/releases/neon/.
On this page, it says:
NOTE: Due to structural changes you cannot update from a Mars (or prior) all-in-one package to a Neon version. If interested in the technical details, see bug 332989 and bug 490515.
I still tried to above procedure, but no updates were found. What is the best way to upgrade from Mars to Neon? A complete new installation? How do I preserve my settings?
The note on the repository page is right. Thanks to your report, I edited the FAQ to make it clear that upgrading packages from Mars to Neon is not supported.
Instead you need to to a fresh install for Neon (or later).
I tried to upgrade in the recommended way, by adding the repository links and doing an update, but then I got a lot of conflict messages. I foolishly tried to remove the conflicting software components, until it told me that Eclipse itself was the conflict! I posted my problem to the Eclipse Forums, and was told by a regular with tens of thousands of posts that Neon was so different that I should not even try to upgrade, just create a new installation. When I tried to do that however, I got lots of warnings "That the artifact download is progressing very slowly from ..."
It is not possible to upgrade from Mars (or earlier versions), so a new install is needed.
This can be in parallel with the old install. From the FAQ:
Fresh install
If you prefer not performing an update (for example
because some 3rd-party content isn't ready for the current release of
Eclipse IDE so the update reports conflicts), you can still download a
fresh install of the Eclipse IDE and install it in another location on
your filesystem, and use it together with the previous version.
To do so, download a new build from the Eclipse download Web site
(https://www.eclipse.org/downloads/eclipse-packages/) and run the
installer or unzip the archive in a new directory. We strongly
recommend against installing/unzipping over your existing version of
Eclipse IDE as it may corrupt your installation.
When you start a new version of Eclipse IDE, you can use the same
existing workspace folder that you were using with older version. The
workspace will be migrated to newer version and Eclipse IDE will to
reuse all configuration. The workspace is forward compatible
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.
I'm running Sonar both on Jenkins and local Eclipse. Recently I've updated Sonar plugin for Eclipse and since then I keep on getting the upper mentioned error. I've updated the plugin on Jenkins as well, but it did not fix the issue. I can connect to server from Eclipse and see Sonar reports there, but local analysis won't start. How can this be fixed? Thank you.
You are trying to connect to a Sonar server which version is less than 3.4.
If you upgrade your Sonar server to lastest version (3.4.1), everything will be back to normal.
I am using eclipse helios (IDE for Java EE developers) 64 bit latest version
and when I am trying to update it from help>check for updates
I am getting the error:
Cannot complete the install because of a conflicting dependency
Why I am getting this error, and how can I solve it?
You are getting this because there is a conflicting dependency somewhere. For example, if you have plugin A that depends on dependency.X-1.0.0 installed, and try to install plugin B that depends on dependency.X-1.1.0, there is a conflict. When you check for updates, Eclipse will check all plugins and features you have installed in the past. Try to update one thing at a time to identify which update has a conflicting dependency.
Hope this helps!
Download bundles from here:
linux 64 bit vm: http://dl.google.com/android/adt/adt-bundle-linux-x86_64-20140702.zip
linux 32 bit vm: http://dl.google.com/android/adt/adt-bundle-linux-x86-20140702.zip
mac: http://dl.google.com/android/adt/adt-bundle-mac-x86_64-20140702.zip
win32: http://dl.google.com/android/adt/adt-bundle-windows-x86-20140702.zip
win64: http://dl.google.com/android/adt/adt-bundle-windows-x86_64-20140702.zip
Starting with ADT bundle 23.0.2, you should be able to update to future versions of ADT.
I couldnt get things working in the 'normal' update screen, but when going to 'About eclipse platform' screen and push the 'installation details' button. I got another screen, where you can select an installed plugin and update it.... in there it worked.
In there I first selected the plugin that seemed to be causing the conflict, and update it. Then the other one conflicting with this one... (the conflict in my case was between the android sdk and my java development tools)
Don't ask me why and what's the difference.... this option might be of help to others...
If running on Windows 7, these errors can often be resolved by running Eclipse as Administrator, then update. https://bugs.eclipse.org/bugs/show_bug.cgi?id=339659
I Could resolve it by checking already installed plugins at where it was giving me this error. I just uninstalled all the plugins which had conflicting dependency and try to install the updates. It worked well.!
check the marked area in this linked image
Generally, why it should happen is that while updating plugins lately,they have evolved 2-3 updates and during which plugins have introduced some new functions that have to be installed and also are to be updated. This thing creates conflicts of dependency. Eclipse tries to update which is not already existing/installed and it also tells install it first which creates conflicts.
So, when you uninstall the plugins, now it installs the latest plugins rather then updating. it means you updating eclipse plugins manually(by uninstalling older and installing latest). This may happen if you have skipped 2-3 updates and now looking for latest update.
I agree with Michel.iamit. I tried all other options of updating the ADT and it did not work. With Michel's solution, my environment did not work and it complained about the conflict.
So here is what I did and got it to work:
First uninstall all ADP Plugins.
Then check for updates and it will prompt you regarding the missing plugins.
Select all, accept all licences and proceeed.
Hope this helps someone.
I solved this problem by downloading the latest ADT release from following urls
linux 64 bit vm:
http://dl.google.com/android/adt/adt-bundle-linux-x86_64-20140702.zip
linux 32 bit vm:
http://dl.google.com/android/adt/adt-bundle-linux-x86-20140702.zip
mac:
http://dl.google.com/android/adt/adt-bundle-mac-x86_64-20140702.zip
win32:
http://dl.google.com/android/adt/adt-bundle-windows-x86-20140702.zip
win64:
http://dl.google.com/android/adt/adt-bundle-windows-x86_64-20140702.zip
After opening eclipse IDE go to Help ->Install New Software->Add
Name = ADT plugin ,
location = link and select all Developer Tools . After installation completed please restart your ide and all the bugs get solved now.
I resolved this issue by running eclipse as root, and then installing the updates from Help>Install New Software and adding the latest update version to the download list (http://download.eclipse.org/eclipse/updates/4.4). Not sure if this is the best way, but it worked to go from Indigo (3.8) to Luna (4.4). I'm doing this on Ubuntu 14.04 x64
I've installed HgEclipse plugin from the update site: http://hge.javaforge.com/hgeclipse
From some reason, when I go to Window->Preferences, I can't find the category Mercurial under Team.
Someone knows how to solve this?
My eclipse version is 3.5 (Galileo).
My plugin version is 1.5.0
I have hg 1.4 installed on my machine.
I'm running on Fedora Core 11.
Thanks!
Asaf
It means the installation did not complete successfully.
Could you check your logs (Windows / Show Views / Error logs) to see what gone wrong?
It seams the problem is related to a (fedora?)eclipse bug, and issues with permissions to the plugin folder.
I solved it by uninstalling hgeclipse, starting eclipse as root, installing hgeclipse, and then restarting as my normal user again.
The project URL is http://javaforge.com/project/HGE, when you create an account and put your issue into the prokect's bug tracker, you will get help there.