I downloaded Eclipse IDE for Java EE Developers 4.3.2 and than I installed the following plugins:
Spring Tool Suite - http://dist.springsource.com/release/TOOLS/update/e4.3/
GWT - http://dl.google.com/eclipse/plugin/4.3
After that I downloaded Spring Roo 1.2.5. Next, I created a new Spring Roo project with help of the wizard and in the Roo shell appears:
project --topLevelPackage sample.roo.flightapp --projectName flightapp-gwt --java 7 --packaging JAR
However, Eclipse showed the following problems in pom.xml.
Description Resource Path Location Type
Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:aspectj-maven-plugin:1.4:compile (execution: default, phase: process-sources) pom.xml /flightapp-gwt line 182 Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:aspectj-maven-plugin:1.4:test-compile (execution: default, phase: process-sources) pom.xml /flightapp-gwt line 182 Maven Project Build Lifecycle Mapping Problem
How is it possible to fix the problem with "Maven Project Build Lifecycle Mapping Problem"
This is not a Spring Roo bug: this just tell you that m2e eclipse plugin doesn't know how handle this maven plugins (when execute it on maven lifecycle).
The proof that is not Roo bug is simple: compile it using maven command-line version.
Check this post to try to solve your problem.
Good luck!
Related
How does Eclipse propagate Java 11 "Expose Package..." to the Maven target?
I am exposing a Java 11 module to ALL-UNNAMED using Eclipse: Properties -> Java Build Path -> Module Dependencies -> Expose Package...
Nothing is added to pom.xml with this configuration yet the project builds successfully.
Using Eclipse 2020-06, m2e's maven 3.6.3, maven-compiler-plugin 3.8.1 (this is the only explicit override in pom.xml). The rest is the "EMBEDDED" maven.
When I look at the Maven console and effective pom I do not see any compilerArgs (--add-exports...) added. When I run mvn from the command line I do get compiler failure as expected.
How does m2e propagate --add-exports to javac without it being visible to help:effective-pom target or Maven console?
In Eclipse when I click "Show JPMS Options..." it does display "--add-exports ...", but nowhere in the m2e debug output does this appear.
I am trying to build the JAVA sample apps provided for Google Cloud Platform at https://github.com/GoogleCloudPlatform/java-docs-samples/tree/master/storage/cloud-client
I have installed maven 3.5 and was able to build and run it from the command line with the steps mentioned in the README
However when I try to import and build the project in eclipse, I get the following error in the pom.xml :
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (execution: default-compile, phase: compile) pom.xml /datastore-google-cloud-samples line 23 Maven Project Build Lifecycle Mapping Problem
The details of eclipse I am using are:
Version:
Neon.3 Release (4.6.3)
Build id: 20170314-1500
I looked at the following answer:
How to solve "Plugin execution not covered by lifecycle configuration" for Spring Data Maven Builds
and added the pluginManagement tag in my pom.xml, however I still got the same error.
Is there any step which I am missing here?
Is there any particular setting which needs to be done in eclipse to use it with maven and/or google cloud?
I downloaded the entire project and import into Eclipse, but fails on this plugin:
Description Resource Path Location Type
Plugin execution not covered by lifecycle configuration: com.lewisd:lint-maven-plugin:0.0.11:check (execution: pom-lint, phase: validate) pom.xml /dl4j-examples line 8 Maven Project Build Lifecycle Mapping Problem
What's the problem and how to get it compiled?
You should only be using m2eclipse. You don't need to "import the whole project" It's actually 6 projects total. You are better off downloading our examples where it will be managed for you. We cover this in our quick start (granted it's with intellij but the ideas are similar):
http://deeplearning4j.org/quickstart
I'm trying to build the project of hadoop. I followed the official document as follows on how to do that.
http://wiki.apache.org/hadoop/HowToContribute
https://wiki.apache.org/hadoop/EclipseEnvironment
I've git clone the project, maven install it successfully, but when I import the project, or even a sub-project like 'hadoop-yarn-api', I got the following errors on maven:
Description Resource Path Location Type
Plugin execution not covered by lifecycle configuration: org.apache.hadoop:hadoop-maven-plugins:3.0.0-SNAPSHOT:protoc (execution: compile-protoc, phase: generate-sources) pom.xml /hadoop-yarn-api line 73 Maven Project Build Lifecycle Mapping Problem
Then I'm trying to mvn clean install the project via External Tools Configuration in eclipse, it also failed on:
[ERROR] Failed to execute goal org.apache.hadoop:hadoop-maven-plugins:3.0.0-SNAPSHOT:protoc (compile-protoc) on project hadoop-yarn-api: org.apache.maven.plugin.MojoExecutionException: 'protoc --version' did not return a version -> [Help 1]
But the curious part is that when I cd into the root directory of 'hadoop-yarn-api' and invoke mvn clean install, it can be built successfully.
I'm using m2ecipse in eclipse, and I'm sure that I've changed to the maven which is exactly the one that I'm used in command line, not the embedded one.
And I've installed protocol buffers 2.5.0:
$ protoc --version
libprotoc 2.5.0
Could anyone give me some idea? Many thanks!
P.S.
Eclipse Java EE IDE - Juno Service Release 2
m2e - 1.4.1.20140328-1905
Mac 1- 0.9.4
maven - 3.0.5
Hadoop - 2.2.0
When I create an ejb project through ejb-javaee6 archetype in Eclipse I get the following errors:
Description Resource Path Location Type
Endorsed directory '/home/hfluz/workspace/maven-test/web2/target/endorsed' is missing. You may need to a perform a Maven command line build in order to create it. pom.xml /web2 line 28 Maven Configuration Problem
Description Resource Path Location Type
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-dependency-plugin:2.1:copy (execution: default, phase: validate) pom.xml /web2 line 53 Maven Project Build Lifecycle Mapping Problem
There is already an /target/endorsed/javaee-endorsed-api-6.0.jar file.
IDE: JBoss Developer Studio 7 Beta 1 (tried with embedded 3.0.4 maven version and also with 3.0.5).
When I generate this same archetype through command line (maven 3.0.4) and import the project to eclipse, these errors are not displayed.
I just tried and the same happens with webapp-javaee6 archetype (also from org.codehaus.mojo.archetypes).
Anyone have any idea about what is causing this issue?
Try refreshing the target folder in eclipse (workspace seems out of sync).
Read http://docs.jboss.org/tools/whatsnew/maven/maven-news-3.3.0.CR1.html about endorsed library support in JBDS/JBT