cstamas commented on PR #20: URL: https://github.com/apache/maven-artifact-transfer/pull/20#issuecomment-1164056204
Just FTR, now that https://github.com/apache/maven-artifact-transfer/pull/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" it's 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.... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
