Review pom.xml, .project and .classpath in order to support Eclipse Indigo
Bug #1210009 reported by
Richard Gomes
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
JQuantLib |
Confirmed
|
Medium
|
Richard Gomes |
Bug Description
Eclipse Indigo has a new m2e (formerly m2eclipse) plugin which behaves differently in regards to contents of pom.xml files.
In a nutshell, now Eclipse complains that certain goals of certain plugins were not accepted. The effect is that Eclipse is not able to resolve dependencies anymore.
Notice that the pom.xml files are correct and are processed as expected using Maven2/3 from the command line.
Meanwhile, Maven3 is gaining acceptance and it is time to properly support Maven3 without breaking compatibility with Maven2.
To post a comment you must log in.
jquantlib- parent/ pom.xml was thoroughly reviewed. plugin in order to adopt best practices.
Now it has configurations for Maven2 and Maven3.
We are also employing maven-enforce-