[Commented] (MRESOLVER-29) Move ant tasks into master as new module

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Commented] (MRESOLVER-29) Move ant tasks into master as new module

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/MRESOLVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248856#comment-16248856 ]

Hervé Boutemy commented on MRESOLVER-29:
----------------------------------------

as explained on dev list and MRESOLVER-29, I'm not convinced that we should move ant tasks into master since:
1. they need to be published to central as consumable artifact
2. there is a dependency on Maven core's Maven Resolver Provider that will in general cause strange dependency version subtle differences, and in incompatible change case even cause un-releasable ant tasks in some resolver release

> Move ant tasks into master as new module
> ----------------------------------------
>
>                 Key: MRESOLVER-29
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-29
>             Project: Maven Resolver
>          Issue Type: Task
>          Components: ant tasks
>            Reporter: Manfred Moser
>            Assignee: Manfred Moser
>
> The ant tasks of Maven Resolver are currently in a separate branch. This makes it hard to keep version consistent and is also harder to understand and locate for users in apache git and on github.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)