You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2025/03/26 14:59:00 UTC
[jira] [Updated] (MNG-8652) Support prefix version ranges for better interoperatibility
[ https://issues.apache.org/jira/browse/MNG-8652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated MNG-8652:
--------------------------------
Issue Type: New Feature (was: Improvement)
> Support prefix version ranges for better interoperatibility
> -----------------------------------------------------------
>
> Key: MNG-8652
> URL: https://issues.apache.org/jira/browse/MNG-8652
> Project: Maven
> Issue Type: New Feature
> Components: Artifacts and Repositories
> Reporter: Arkadiusz Biczewski
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)