You should not use m2e but rather the maven eclipse plugin Jeff
Le vendredi 6 avril 2012, Matthieu Vincent a écrit : > Hi, > > i've tried for 2 days to build Jenkins under Eclipse Indigo with no > success. > > I followed all informations on > https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins > But when i import the projects on Eclipse after running mvn > -DdownloadSources=true eclipse:eclipse, I get plenty of errors about some > plugins and their lifecycle. > > I also had a loog to > https://wiki.jenkins-ci.org/display/JENKINS/Setting+up+Eclipse+to+build+Jenkins, > and everything looks fine on my environment. > > Problem seems to be that m2eclipse cannot find m2e connectors > > Does anyone successfully build Jenkins (SNAPSHOT 1.460) on Eclipse Indigo > ?? > > here are some examples : > > Plugin execution not covered by lifecycle configuration: > com.cloudbees:maven-license-plugin:1.3:process (execution: default, phase: > compile) pom.xml /jenkins-war line 28 Maven Project Build Lifecycle > Mapping Problem > Plugin execution not covered by lifecycle configuration: > com.cloudbees:maven-license-plugin:1.3:process (execution: default, phase: > compile) pom.xml /maven-plugin line 29 Maven Project Build Lifecycle > Mapping Problem > Plugin execution not covered by lifecycle configuration: > org.apache.maven.plugins:maven-dependency-plugin:2.3:list (execution: > list-dependencies, phase: generate-resources) pom.xml /jenkins-war line > 180 Maven Project Build Lifecycle Mapping Problem > Plugin execution not covered by lifecycle configuration: > org.apache.maven.plugins:maven-dependency-plugin:2.3:unpack-dependencies > (execution: executable-war-header, phase: generate-resources) pom.xml > /jenkins-war line 190 Maven Project Build Lifecycle Mapping Problem > Plugin execution not covered by lifecycle configuration: > org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:display-info > (execution: default, phase: validate) pom.xml /notification-plugin line 3 > Maven > Project Build Lifecycle Mapping Problem > Plugin execution not covered by lifecycle configuration: > org.codehaus.groovy.maven:gmaven-plugin:1.0-rc-5:generateTestStubs > (execution: test-in-groovy, phase: generate-test-sources) pom.xml > /notification-plugin line 3 Maven Project Build Lifecycle Mapping Problem > Plugin execution not covered by lifecycle configuration: > org.codehaus.groovy.maven:gmaven-plugin:1.0-rc-5:testCompile (execution: > test-in-groovy, phase: test-compile) pom.xml /notification-plugin line 3 Maven > Project Build Lifecycle Mapping Problem > Plugin execution not covered by lifecycle configuration: > org.jenkins-ci.tools:maven-hpi-plugin:1.78:insert-test (execution: > default-insert-test, phase: generate-test-sources) pom.xml /maven-plugin line > 398 Maven Project Build Lifecycle Mapping Problem > Unknown pom.xml Unknown Unknown > org.eclipse.core.internal.resources.Marker@8ae6fb3 is not of a > displayable type > Plugin execution not covered by lifecycle configuration: > org.jenkins-ci.tools:maven-hpi-plugin:1.78:resolve-test-dependencies > (execution: default-resolve-test-dependencies, phase: test-compile) > pom.xml /maven-plugin line 398 Maven Project Build Lifecycle Mapping > Problem > Unknown pom.xml Unknown Unknown > org.eclipse.core.internal.resources.Marker@8ae6fb5 is not of a > displayable type > Plugin execution not covered by lifecycle configuration: > org.jenkins-ci.tools:maven-hpi-plugin:1.78:test-hpl (execution: > default-test-hpl, phase: test-compile) pom.xml /maven-plugin line 398 Maven > Project Build Lifecycle Mapping Problem > Unknown pom.xml Unknown Unknown > org.eclipse.core.internal.resources.Marker@8ae6fb4 is not of a > displayable type > Plugin execution not covered by lifecycle configuration: > org.jenkins-ci.tools:maven-hpi-plugin:1.78:validate (execution: > default-validate, phase: validate) pom.xml /maven-plugin line 398 Maven > Project Build Lifecycle Mapping Problem > Unknown pom.xml Unknown Unknown > org.eclipse.core.internal.resources.Marker@8ae6fb2 is not of a > displayable type > Plugin execution not covered by lifecycle configuration: > org.jvnet.hudson.tools:maven-hpi-plugin:1.57:apt-compile (execution: > default-apt-compile, phase: compile) pom.xml /notification-plugin line 3 Maven > Project Build Lifecycle Mapping Problem > Plugin execution not covered by lifecycle configuration: > org.jvnet.hudson.tools:maven-hpi-plugin:1.57:insert-test (execution: > default-insert-test, phase: generate-test-sources) pom.xml > /notification-plugin line 3 Maven Project Build Lifecycle Mapping Problem > Plugin execution not covered by lifecycle configuration: > org.jvnet.hudson.tools:maven-hpi-plugin:1.57:resolve-test-dependencies > (execution: default-resolve-test-dependencies, phase: test-compile) > pom.xml /notification-plugin line 3 Maven Project Build Lifecycle Mapping > Problem > Plugin execution not covered by lifecycle configuration: > org.jvnet.hudson.tools:maven-hpi-plugin:1.57:test-hpl (execution: > default-test-hpl, phase: test-compile) pom.xml /notification-plugin line 3 > Maven > Project Build Lifecycle Mapping Problem > Plugin execution not covered by lifecycle configuration: > org.jvnet.localizer:maven-localizer-plugin:1.8:generate (execution: > default, phase: generate-sources) pom.xml /notification-plugin line 3 Maven > Project Build Lifecycle Mapping Problem > Plugin execution not covered by lifecycle configuration: > org.kohsuke:access-modifier-checker:1.0:enforce (execution: > default-enforce, phase: process-classes) pom.xml /notification-plugin line > 12 Maven Project Build Lifecycle Mapping Problem > Plugin execution not covered by lifecycle configuration: > org.kohsuke.gmaven:gmaven-plugin:1.0-rc-5-patch-2:execute (execution: > preset-packager, phase: process-resources) pom.xml /jenkins-test-harness line > 184 Maven Project Build Lifecycle Mapping Problem > Plugin execution not covered by lifecycle configuration: > org.kohsuke.gmaven:gmaven-plugin:1.0-rc-5-patch-2:testCompile (execution: > test-in-groovy, phase: test-compile) pom.xml /jenkins-test-harness line > 194 Maven Project Build Lifecycle Mapping Problem > > > Thanks in advance !! > Matt > -- Jeff MAURY "Legacy code" often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
