[GitHub] [maven-artifact-transfer] rfscholte commented on pull request #20: [MSHARED-944] Drop support for Maven 3.0. Require 3.1.1

2020-12-30 Thread GitBox
rfscholte commented on pull request #20: URL: https://github.com/apache/maven-artifact-transfer/pull/20#issuecomment-752506877 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

[GitHub] [maven-artifact-transfer] rfscholte commented on pull request #20: [MSHARED-944] Drop support for Maven 3.0. Require 3.1.1

2020-12-30 Thread GitBox
rfscholte commented on pull request #20: URL: https://github.com/apache/maven-artifact-transfer/pull/20#issuecomment-752454346 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-trans

[GitHub] [maven-artifact-transfer] rfscholte commented on pull request #20: [MSHARED-944] Drop support for Maven 3.0. Require 3.1.1

2020-12-30 Thread GitBox
rfscholte commented on pull request #20: URL: https://github.com/apache/maven-artifact-transfer/pull/20#issuecomment-752440522 Please don't do this. The intention of maven-artifact-transfer is a bridge to any Aether implementation.