You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/03/18 18:43:00 UTC
[jira] [Commented] (MINVOKER-254) Upgrade Groovy
[ https://issues.apache.org/jira/browse/MINVOKER-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061988#comment-17061988 ]
Hudson commented on MINVOKER-254:
---------------------------------
Build succeeded in Jenkins: Maven TLP » maven-invoker-plugin » master #53
See https://builds.apache.org/job/maven-box/job/maven-invoker-plugin/job/master/53/
> Upgrade Groovy
> --------------
>
> Key: MINVOKER-254
> URL: https://issues.apache.org/jira/browse/MINVOKER-254
> Project: Maven Invoker Plugin
> Issue Type: Dependency upgrade
> Reporter: Piotr Zygielo
> Assignee: Olivier Lamy
> Priority: Minor
> Fix For: 3.2.2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I propose to upgrade groovy used by invoker.
> In groovy 2.5 the type of groovy-all artifact changed (jar -> pom).
> Using groovy 2.5.x could break existing projects that already override plugin's dependency but want to upgrade plugin to upcoming 3.2.x release.
> That's why I think groovy could be updated to the latest 2.4.x in current plugin, and using 2.5 could be considered in scope of future release.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)