You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2020/09/27 18:48:00 UTC

[jira] [Comment Edited] (MSHARED-939) Remove Apache Ivy from dependency

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

Herve Boutemy edited comment on MSHARED-939 at 9/27/20, 6:47 PM:
-----------------------------------------------------------------

what could be done is to add some documentation on how to use Grapes in a Groovy script: MSHARED-960


was (Author: hboutemy):
what could be done is to add some documentation on how to use Grapes in a Groovy script

> Remove Apache Ivy from dependency
> ---------------------------------
>
>                 Key: MSHARED-939
>                 URL: https://issues.apache.org/jira/browse/MSHARED-939
>             Project: Maven Shared Components
>          Issue Type: Improvement
>          Components: maven-script-interpreter
>            Reporter: Slawomir Jaranowski
>            Assignee: Sylwester Lachiewicz
>            Priority: Major
>             Fix For: maven-script-interpreter-1.3
>
>
> This dependency allow using Groovy Grapes for all.
> But question if we really need it?
> All integration tests in project and in maven-invoker-plugin pass without it.
> Personally I prefer to have minimal list of dependency in projects
> It make easier to maintenance project and need less resource to run.
> When someone need it, can add dependency to plugin in self project.
> It was added in issue: MSHARED-794, but no test was not added which confirmed case of usage.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)