Maven Eclipse M2E 1.0 (and Eclipse Indigo 3.7)
----------------------------------------------
Key: MIFOS-5090
URL: http://mifosforge.jira.com/browse/MIFOS-5090
Project: mifos
Issue Type: Bug
Reporter: Michael Vorburger
Assignee: Michael Vorburger
Opening a Mifos workspace with Maven Eclipse M2E 1.0 (and Eclipse Indigo 3.7)
causes:
{noformat}Description Resource Path Location Type
Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-pmd-plugin:2.4:check (execution: default, phase:
compile) pom.xml /mifos-acceptanceTests line 287 Maven Project
Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-pmd-plugin:2.4:cpd-check (execution: default,
phase: compile) pom.xml /mifos-acceptanceTests line 287 Maven Project
Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.codehaus.groovy.maven:gmaven-plugin:1.0:execute (execution: default, phase:
generate-resources) pom.xml /mifos-webapp line 648 Maven Project
Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.codehaus.mojo:native2ascii-maven-plugin:1.0-alpha-1:native2ascii
(execution: native2ascii, phase: process-resources) pom.xml /mifos-webapp
line 676 Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.codehaus.mojo:properties-maven-plugin:1.0-alpha-1:read-project-properties
(execution: default, phase: initialize) pom.xml /mifos-acceptanceTests line
198 Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.codehaus.mojo:properties-maven-plugin:1.0-alpha-1:read-project-properties
(execution: default, phase: initialize) pom.xml /mifos-db line 203
Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.codehaus.mojo:properties-maven-plugin:1.0-alpha-1:read-project-properties
(execution: default, phase: process-test-resources) pom.xml
/mifos-cashflow line 133 Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.codehaus.mojo:properties-maven-plugin:1.0-alpha-1:read-project-properties
(execution: default, phase: process-test-resources) pom.xml
/mifos-questionnaire line 136 Maven Project Build Lifecycle Mapping
Problem
Plugin execution not covered by lifecycle configuration:
org.codehaus.mojo:properties-maven-plugin:1.0-alpha-1:read-project-properties
(execution: default, phase: process-test-resources) pom.xml /mifos-webapp
line 480 Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.mifos.maven:mifos-pseudoloc-gen:1.0:pseudolocalize (execution: default,
phase: validate) pom.xml /mifos-accounting line 79 Maven Project Build
Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.mifos.maven:mifos-pseudoloc-gen:1.0:pseudolocalize (execution: default,
phase: validate) pom.xml /mifos-cashflow line 252 Maven Project Build
Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.mifos.maven:mifos-pseudoloc-gen:1.0:pseudolocalize (execution: default,
phase: validate) pom.xml /mifos-questionnaire line 256 Maven
Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.mifos.maven:mifos-pseudoloc-gen:1.0:pseudolocalize (execution: default,
phase: validate) pom.xml /mifos-userInterface line 202 Maven
Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.mifos.maven:mifos-pseudoloc-gen:1.0:pseudolocalize (execution: default,
phase: validate) pom.xml /mifos-webapp line 615 Maven Project Build
Lifecycle Mapping Problem{noformat}
There is a Quick Fix available to "Permanently mark goal ... in pom.xml as
ignored in Eclipse build".
Maven Eclipse M2E 1.0 and/or Eclipse Indigo 3.7 also want to modify some
.classpath/.project files, and add a few more Eclipse files.
I will test if the changes it wants to make can co-exist with previous versions
Maven Eclipse M2E 0.12.1 and Eclipse Indigo 3.6. If yes, I'll go ahead and
commit the changes. If not, I'll reach out to the dev list to see when
everybody wants to switch.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
