We've been facing this issue for quite some months now, and we can't seem to find any solutions for it so far (not many relevant threads on the internet about people having the same issues).
My team is using Eclipse. For some of our Maven poms, we need to install a specific m2e connector. The error we get is :
Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:build-helper-maven-plugin:1.12:add-test-source (execution: add-source, phase: generate-sources)
Eclipse offers to install an additional connector to fix the issue. It can be installed, and indeed our Maven errors disappear after a restart of the application. The specific plugin to install is build-helper-maven-plugin.
However, this installations also has the interesting effect to completely remove the junit integration from eclipse. It becomes impossible to run tests, and all of the junit related context / views / perspectives / settings are gone for good.
When trying to install it again, the "Install new software" view indicates that the testing integration is already installed.
Existing junit views now show the following error :
Could not create the view: org.eclipse.jdt.junit.ResultView
So far our only solution has been to keep a backup of eclipse at all times, and simply replace the whole installation after maven has been run once.
Has this happened to anyone, or can someone point us in the direction on how to fix this?
The issue is reproducable on Neon 1 and 2, both for the default eclipse as well as the RCP developers flavor
We have tried to get help from the eclipse community but without success so far
Current eclipse installation :
Related
When I create a new Maven project in Eclipse Luna it gives this error as soon as the project is created:
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (execution: default-compile, phase: compile) pom.xml /intercept line 1 Maven Project Build Lifecycle Mapping Problem
There is nothing in the project except for the pom.xml, and I can't add a Java class because it thinks it is not a Java project. If I run mvn clean install from the command line it builds successfully. This looks like it is the Eclipse - Maven integration that is broken in Luna.
This doesn't happen with Kepler. What got broken in Luna? I am behind a firewall and a proxy server that prevent certain kinds of internet access.
Thanks.
From https://issuetracker.springsource.com/browse/STS-4236 and crediting the user on that site who provided the answer:
Martin Lippert (c) added a comment - 27/Oct/15 7:04 AM
I can reproduce this behavior, but can't find the root cause of it yet. It seems to happen after updating STS, but not updating the m2e components for whatever reason.
The way to solve this is to update the used m2e and m2e-wtp components in STS by installing those updates via "Install New Software" from:
http://download.eclipse.org/technology/m2e/releases
http://download.eclipse.org/m2e-wtp/releases/mars/
After that update, the lifecycle mapping should work fine again.
I am still getting an issue when running this on a JDK6, but that is a different story.
Eclipse can some times fail to load plugins. I have experienced this E3.7 with both ScalaIDE and GroovyEclipse.
In both cases some times the syntax highlighting fails. Also I have noticed some times plugin related menu items and popups do not appear. This is very much evident when you use the Pulse Eclipse distribution.
This is aggregated after using Eclipse of a while and going through a few updates. Some times a clean unzip and a download of the required plugin solve the issue.
Is there a way to get around these issues?
What are the problems with the plugins? Are they not found at all, or do they fail to load?
When you start up Eclipse, open the view "Plug-in Registry", find the plugin that causes problems and select to diagnose the plugin. This will determine if there are some dependencies that arent satisfied.
How have you installed the plugins? The correct way to do this is to use update sites. Just downloading and unzipping into the plugins catalog is not recommended.
There is also a trick to start up an OSGI console to diagnose plugins, see my answer here
This page can also provide some more help.
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)
I am new to Eclipse so I am having a hard time troubleshooting this problem. I have a new installation of Eclipse Java EE - Galileo on Windows, and I am unable to see any changes made in the IDE after installing plugins. I have verified that the plugins are installed via installation details, but see no changes made.
For example, after installing the maven integration plugin m2eclipse I go to File->New->Project ... and I have no option for maven. After installing the QuickRex plugin I have no view for it etc.
I have tried re-installing the plugins, re-installing Eclipse, and starting Eclipse with the -clean option, but nothing has resolved the issue.
Any ideas? Thanks!
Ok. This is just a wild guess but could you start over with a fresh install and make sure that you uncheck the option Contact all update sites during install to find required software as shown below:
alt text http://img717.imageshack.us/img717/8039/screenshot003ao.png
I faced a similar problem (on another platform than yours), some updates were "disabling" all my plugins. Not checking this option allowed me to work around this issue.
Follow-up: You'll need to install that Zest stuff manually from the GEF update site:
alt text http://img339.imageshack.us/img339/8003/screenshot003rl.png
If I start with a Eclipse IDE for Java Developers (85 MB) (Ganymede) installation. What plug ins do I need to install to be a able to:
See the Server tab and being able to add my Tomcat 6 installation.
Be able to create a Dynamic Web Project which I may connect to my server.
I want to be able to start and stop the server.
See the server Stdout-output in my Console tab.
Debug an application on the server.
I want to install as little as possible, as long as I can do the above things I am more than satisfied.
Especially since I have problems with the complete Web Tools Platform (WTP); according to me it's full of bugs related to validation. It sometimes says valid files are invalid, often it helps if you simply restart Eclipse. I have also found it to ignore exclusions as well as sometimes completely ignoring that I have disabled validation all together.
The problems I've experienced have made me uninterested in anything from the WTP project, except the plug ins enabling me to work more smoothly by fulfilling the above unordered list (because that part of WTP worked really well).
I have heard the some have had success with Sysdeo Eclipse Tomcat Launcher Plug-in together with Ganymede. But since it's officially not supported and there has not been a new release since May 2007 and running it with Ganymede involved changing the plug-in files to accept versions >=3.4 I don't see it as a long term solution.
Installing parts of the WTP but not it in its whole feels like a long term solution while at the same time skipping the error ridden parts of the WTP. But I need help with which parts I need to install, as the documentation on Eclipse.org does not explain. Of course, if there is another supported solution than using parts of WTP then that is of interest too!
When I display the "eclipse Plug-in Dependencies" view for org.eclipse.jst.server.tomcat.ui, I see:
org.eclipse.wst.common.emf
org.eclipse.wst.common.emfwrokben.integration
org.eclipse.wst.common.environment
org.eclipse.wst.common.frameworks
org.eclipse.wst.common.modulecore
org.eclipse.wst.common.project.facet.core
org.eclipse.wst.common.project.facet.ui
org.eclipse.wst.common.uriresolver
org.eclipse.wst.internet.monitor.core
org.eclipse.wst.server.core
org.eclipse.wst.server.ui
org.eclipse.wst.validation
So if you can select org.eclipse.jst.server.tomcat.ui through p2 and let that "update process" to pick the dependencies for you, you should end up with the minimal set of plugins needed for running/managing Tomcat on Eclipse (with WTP).