[
https://issues.apache.org/jira/browse/GROOVY-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522924#comment-16522924
]
Matt Nelson commented on GROOVY-8644:
-
Thanks for updating the release notes.
To add some additional perspective on why this may not be such a strait forward
uplift. There are about 3000[1,2] projects that depend on groovy-all. Some of
those usages are through transitive dependencies such as is the case with
zuul[3,4]. For those consumers who are using groovy transitively, it will
require some additional work to determine the new dependency tree, either with
dependency management in the consuming project or with a PR to the downstream
project.
It is called out that groovy[5] uses semver and I think this is a middle ground
that isn't well defined. The API wasn't changed, so from a compile only
perspective it is passive. But from a dependency resolution perspective it is
non-passive since it will require more work than a version bump. I am not
advocating for the reintroduction of the groovy-all dependency, because I agree
with the preparation for java 9+, just wanted to provide some additional
context from a transitive groovy consumer.
[1] http://mvnrepository.com/artifact/org.codehaus.groovy/groovy-all/usages
[2] https://javalibs.com/artifact/org.codehaus.groovy/groovy-all
[3] https://github.com/Netflix/zuul/blob/v1.3.1/zuul-core/build.gradle
[4] https://github.com/Netflix/zuul/blob/v2.1.2/zuul-core/build.gradle#L9
[5] http://groovy-lang.org/versioning.html
> Groovy 2.5 binary JARs not available at Maven Central
> -
>
> Key: GROOVY-8644
> URL: https://issues.apache.org/jira/browse/GROOVY-8644
> Project: Groovy
> Issue Type: Bug
> Components: release
>Affects Versions: 2.5.0
>Reporter: Alexander Veit
>Priority: Critical
>
> See [http://central.maven.org/maven2/org/codehaus/groovy/groovy-all/2.5.0/]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
