I know this is an open issue, see https://issues.gradle.org/browse/GRADLE-3213
Does any one know how a workaround could look like to be added to our build scripts?
Denis
Did no one have a similar problem?
We are working together with a team which is using Maven as build system. They cannot resolve our dependencies because our POM files contain ‘+’ version ranges and we use them quite extensively.
Is there any workaround for that to get it work?
I mean, at the end it should also a big issue for Maven Central when Maven projects are using Gradle based projects which apply the + as version range selector…
Denis