[
https://issues.apache.org/jira/browse/MWRAPPER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456234#comment-17456234
]
Herve Boutemy commented on MWRAPPER-32:
---------------------------------------
bq. If you don't accept to remove maven-artifact-transfer in first release it
will be ok.
I was not clear: when it is available, I accept to remove dependency on
maven-artifact-transfer, hoping that it does not remove any compatibility or
have any drawback of any sort. It seems it is the target (I don't master that
aspect of things)
I just have a basic solution for provided scope just now, waiting MWRAPPER-31
(which is not any more a blocker)
any objection?
> Use Maven core component in provided scope
> ------------------------------------------
>
> Key: MWRAPPER-32
> URL: https://issues.apache.org/jira/browse/MWRAPPER-32
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Plugin
> Reporter: Slawomir Jaranowski
> Priority: Major
> Fix For: 3.1.0
>
>
> First dependency on {{maven-artifact-transfer}} should be removed because has
> many transitive dependency in compile scope to Maven core artifacts.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
