[
https://issues.apache.org/jira/browse/MSHARED-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17557863#comment-17557863
]
ASF GitHub Bot commented on MSHARED-944:
----------------------------------------
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....
> Set minimum Maven version to 3.1.1
> ----------------------------------
>
> Key: MSHARED-944
> URL: https://issues.apache.org/jira/browse/MSHARED-944
> Project: Maven Shared Components
> Issue Type: Dependency upgrade
> Components: file-management, maven-shared-io, maven-shared-jar
> Reporter: Elliotte Rusty Harold
> Priority: Major
> Fix For: maven-shared-io-3.0.1, maven-archiver-3.5.1,
> file-management-3.0.1
>
>
>
>
> Note: We have a conflict with asm:asm:3.3.1 in Maven 3.1.0, see MNG-5499
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
