I have installed Eclipse Neon Milestone 4, Java 8, and Apache Maven 3.3.3 on my windows system. I am trying to install plugin :: M2E - Maven Integration for Eclipse 1.6.2 in eclipse. I am getting error -
Cannot complete the request. See the error log for details.
"m2e - Maven Integration for Eclipse (includes Incubating components)" will be ignored because a newer version is already installed.
But When I look in "Installation detail" I can't see Maven plugin there. Also no Maven menu option is coming when I am right clicking the project.
Please help to proceed.
I just ran into this problem too. I'm using the same version of Eclipse, etc. It turns out that the "fix" was kind of subtle. When you go an install new software under the help option using "http://download.eclipse.org/technology/m2e/releases", then you select the maven option. On the next screen they say here's what your downloading...
I had to select the two items by highlighting them then press next and agree to the licenses for m2eclipse to install correctly. The first time when it didn't work I thought, okay great that's what I need, and then nothing happened. Hopefully that helps, I realize you're getting this answer about 10 months after you asked for help.
Related
I am new to Eclipse RCP and plugin development so please don't be cruel.
I am using Maven and I have a remote repository. Yesterday Eclipse was fine but today it got messed up and I imported all the projects again so I reconfigured all but I can't get out of this problem. We use e(fx)clipse 2.5 but I installed the 3.0 version of it because I didn't find the link to install it via Eclipse.
Could you please tell me how I add a dependency? There is something that I am missing there?
Thank you
Adding the location http://download.eclipse.org/releases/oxygen/ to your target platform should fix the errors.
I've been using Eclipse for programming and testing Storm just fine, however, I created an SVN account, where I commit the project, and for that, I needed the SVN plugin for Eclipse. It worked, but after that, i get this message on a popup error window when I try to launch:
Referenced classpath provider does not exist:
org.eclipse.m2e.launchconfig.classpathProvider
I realised that in the "configure" menu, the option "convert to maven project" (right click on project) disappeared. The "runAs" options for the java topology doesn't run with this error, and the "pom.xml" cannot be run as maven.
Possible fix tried:
I tried to reinstall all maven builders to Eclipse(it doesn't let me to unninstall).
I tried to rebuild config by:
mvn eclipse:clean eclipse:eclipse
None of this worked, my Eclipse version is:
Eclipse Java EE IDE for Web Developers.
Version: Mars.1 Release (4.5.1)
Build id: 20150924-1200Eclipse Java EE IDE for Web Developers.
On Ubuntu Gnome 14.04.
As I said, it was running perfect until I installed SVN plugin.
EDIT
I realised that I have installed two plugins of m2e:
Maven integration for Eclipse (Luna and newer)1.5
Maven integration for Eclipse (Luna)1.5.0
Both in marketplace, but I have no way to uninstall them, it says:
[plugin] cannot be fully uninstalled because other installed software requires it. The parts that are not required will be uninstalled.
EDIT 2
In the "Installation History" within the "Help>Installation details" menu, I saw that "Maven integration for Eclipse (Luna)1.5.0" was installed by (or with) SVN plugin, so I think the problem is there, nevertheless, I can't uninstall it as I said in my first "EDIT".
If anyone has a clue about what is happening, please, help me.
Thanks in advance!
We use Subclipse in Eclipse (Kepler and Mars) without problems (Did you install Subclipse or Subversive?).
To check out projects as Maven projects, you should install a m2e connector. Subversive has one in the "Discovery" catalog while for Subclipse there is a separate update site.
If your eclipse plugin configuration is somehow broken, I would start again with a virgin eclipse (Mars.1, Mars.2 or Neon) which already contains m2e in version 1.6 or 1.7. Then you can install Subclipse or Subversive and try again.
Workaround proposal: simply don't deal with SVN within eclipse!
Instead, you can use "git svn" on ubuntu.
Meaning: with git svn you can create a local git repository, that allows you to commit/fetch to a remote SVN server. But to your eclipse ... that repository looks a common of garden GIT repository.
In other words: using that tool, you can still connect to SVN (although I don't understand why anybody would want to do that in 2016); but you have all the features of git available to you as well (including full support within eclipse; without installing any additional plugins).
i am using checkStyle eclipse plugin ,but the labels of the plugin are not displayed correctly,
i am using the current version 5.7.0.201402131929
So i wonder if there is any suggestions ?
Thank you
I am using same version and labels are correctly displayed. I would suggest you to unstall all checkstyle plugin from eclipse from
Help > About Eclipse > Installation Details > Installed Software .
Select all checkstyle related softwares and uninstall them.
Then install Checkstyle plugin again from
Help > Eclipse Market Place
Issue should resolved.
NOTE:- steps may vary depending upon eclipse version
I had eclipse Juno running; I decided to upgrade to eclipse Kepler. I only had Java 1.6, so I downloaded and installed java 1.7, and changed my JAVA_HOME. I downloaded and unpacked Kepler and pointed it at my existing workspace.
I have two questions; First, when I click on "Window / Preferences", there is no entry for "Maven" on the left of the dialog. I shut down and rebooted the machine after I changed JAVA_HOME to ensure that didn't cause this.
I checked the list of installed plugins, and it lists m2e (v1.4).
Second, I am getting an error message "Plugin execution not covered by lifecycle configuration". There are a double-handful of sites indicating what to do about this, including the m2e's wiki pages, but over half the suggestions don't look reasonable, the wiki doesn't spell out what to do for its recommended solution, assuming you know, and the one that looked most promising to me involves using "Windows / Preferences / Maven".
So I'm most interested in the answer to the first question; if you have hints to offer on the second, I'm all ears...
Here are the things you can try:
Start Eclipse with the -clean switch
Uninstall / reinstall the plugin
Delete the plugin's files physically from the plugins folder and install it again from the Marketplace
If all else fails you can just get a fresh installation of Eclipse and reinstall your old plugins manually. There are some of them which won't work in a newer version of Eclipse (I remember for example that I had to install WindowBuilder all over again after an Eclipse version switch).
I believe this came about by installing a new version of eclipse but pointing it at a workspace for the previous version. I have been told that there is metadata attached to a workspace that has to do with plugins; this would be bound to cause problems for a version that didn't have the plugins. I eliminated the new install, installed it again, created a new workspace, and imported-with-copy the project I wanted, that has eliminated the error. I will pursue that further.
Thanks to Adam Arold who pointed out the metadata issue.
Is there any major change in p2 mechanism in Eclipse 3.8? I tried to install Eclipse 3.8 plugins via p2 dropins mechanism but its not working at all. It is not able to resolve the plugins. Plug-in perspective is also missing. Also the bundles.info is not coming up in org.eclipse.equinox.simpleconfigurator.
I suspect that your dropins are failing to install because they have dependencies that are not resolving in your new install. The standard behavior for dropins is to ignore plugins that cannot be installed. The user doesn't get any feedback on the problem. That's one of the reasons that dropins approach to installing plugins is not recommended.
To debug your current problem, try to install the plugins you are trying to install via dropins by using the plugin install dialog instead. You will see a report on why installation cannot proceed and will be able to proceed accordingly.
This section of the release notes should address your question.
API Contract Compatibility: Eclipse SDK 3.8 is upwards
contract-compatible with Eclipse SDK 3.7 except in those areas noted
in the Eclipse 3.8 Plug-in Migration Guide.
You should copy your installed plugins from user .eclipse/org.eclipse.platform_4.2.0_*/plugins and .eclipse/org.eclipse.platform_4.2.0_*/features to /usr/lib/eclipse-4.2/dropins/eclipse/plugins and /usr/lib/eclipse-4.2/dropins/eclipse/features. In win7 filesystem you should find C:/eclipse/dropins and your plugins and features directories in your User directory. It works with 4.3.0 juno build: I20120810-1300
See in Getting started Dropins paragraph