Review pom.xml, .project and .classpath in order to support Eclipse Indigo

[Richard Gomes]

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.

[Richard Gomes (frgomes)]

jquantlib-parent/pom.xml was thoroughly reviewed.
Now it has configurations for Maven2 and Maven3.
We are also employing maven-enforce-plugin in order to adopt best practices.

[Richard Gomes (frgomes)]

Plugins which were causing troubles in Eclipse were moved to profiles which are disabled by default.

This scenario is not ideal: we should disable certain profiles only when running inside Eclipse, actually, instead of disabling these profiles and having to 'remember' to activate them when building from the command line.

The trouble is due to a bug in m2eclipse:
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=337353

[Jimmy Wong (jimmysyss)]

I am using Indigo with m2e with a Maven 3 runtime, it is running fine.

The key is to removing the .project and .classpath file. I suggest to remove it from SVN and let m2e to resolve the dependencies on its own.