Description
Arkadiusz Biczewski opened MNG-8652 and commented
When working in distributed teams with some of them using gradle build system for their artefacts, some pom(s) file published to repostiroy may contain prefix-style version ranges which results in build error when used with maven pom:
Could not find artifact groupId:artifactName:jar:2.0.0.+ in central
As gradle support maven version range syntax: https://docs.gradle.org/current/userguide/dependency_versions.html it would be nice and welcomed to also provide interoperatibility in second way, that means supporting gradle prefix syntax of version ranges in maven.
As stated in the sample, and as possible with bracket maven style version ranges, support should be not only for sematic versioning but also for more detailed versioning seperatd with dots.
Issue Links:
- MNG-8569 Deprecate and remove version ranges