[MSHARED-944] Drop support for Maven 3.0. Require 3.1.1

[slachiewicz]

No description provided.

[michael-o]

Massive, will need some time for this.

[slachiewicz]

there is nothing special - lots of removal of old maven 3.0 stuff + replacement of reflections to just us normal direct call to exposed API. No need to spent too much time here.
CI is green https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-artifact-transfer/job/MSHARED-944/

[slachiewicz]

With these changes, it should be easier to move forward with maven-dependency-tree and other plugins - to not fight with old dependencies.

[michael-o]

I think this should be moved to a property.

[slachiewicz]

Sure, will fix this next time

[rfscholte]

Please don't do this. The intention of maven-artifact-transfer is a bridge to any Aether implementation.

[rfscholte]

Sorry @slachiewicz if you've spend a lot of time on this, but I need to close this. Once everything is using Maven 3.1+ we can simply archive maven-artifact-transfer because it has become an unnecessary abstraction layer.

[slachiewicz]

Do we have anywhere documented this recommendation? I think we still have on wiki to use this artefact.
Also with this changes we can easily switch to new aether impl by dep update plus remove redundant code/simplify other projects.

[rfscholte]

I still consider adding the org.apache.maven.shared.transfer.project package a bad choice, because it introduces a dependency on Maven.
https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies does indeed talk about adding maven-artifact-transfer, but https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=155749857 should contain the removal of it.

[olamy]

was a good idea to get RID of old dependencies until we go away correctly from org.eclipse package.

[cstamas]

Just FTR, now that #24 has been merged, and MAT modularized, same effect can be now achieved by simply excluding the 3.0 module from dependencies.

But, my problem is not (only) this: MAT is half done (is unfinished) and if we stick with it, there will be probably someone who will try to "improve" its API, thus, we are again at doubling efforts as new Maven 4 API and MAT will become somewhat "competing" APIs.

This is why I think just detaching from MAT and leave it to oblivion is better, as for Maven 3.1-3.999 using eclipse resolver packages are completely okay, while in Maven 4 we will need to switch to new API anyway....