[
https://issues.apache.org/jira/browse/GROOVY-8483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380102#comment-16380102
]
Henrik edited comment on GROOVY-8483 at 2/28/18 10:31 AM:
----------------------------------------------------------
Okay, I figured it out. The problem is when Gradle "upgrades" a version, like
this:
{code:java}
+--- com.github.tomjankes:wiremock-groovy:0.2.0
| +--- org.codehaus.groovy:groovy-all:2.4.3 -> 2.5.0-beta-3{code}
Gradle will then still use *@jar* from 2.4.3 instead of *@pom* from
2.5.0-beta-3.
So I have to exclude every transitive dependency to gradle-all <= 2.5.0-beta-2.
Not a big problem, but nice to know...
Now I can use the *org.codehaus.groovy:groovy-all:2.5.0-beta-3* dependency
without any other workarounds.
was (Author: monti):
Okay, I figured it out. The problem is when Gradle "upgrades" a version, like
this:
{code:java}
+--- com.github.tomjankes:wiremock-groovy:0.2.0
| +--- org.codehaus.groovy:groovy-all:2.4.3 -> 2.5.0-beta-3{code}
Gradle will then still use *@jar* from 2.4.3 instead of *@pom* from
2.5.0-beta-3.
So I have to exclude every transitive dependency to gradle-all <= 2.5.0-beta-2.
Not a big problem, but nice to know...
Now I can use the *org.codehaus.groovy:groovy-all:2.5.0-beta-3* without any
other workarounds.
> groovy-all v2.5.0-beta-3 is missing from bintray
> ------------------------------------------------
>
> Key: GROOVY-8483
> URL: https://issues.apache.org/jira/browse/GROOVY-8483
> Project: Groovy
> Issue Type: Bug
> Components: release
> Affects Versions: 2.5.0-beta-3
> Reporter: Henrik
> Priority: Blocker
>
> [https://dl.bintray.com/groovy/maven/org/codehaus/groovy/groovy-all/2.5.0-beta-3/]
> does not exist
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
