You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2008/07/07 16:35:27 UTC

[jira] Created: (MDEPLOY-82) Enable resolution of dependency version ranges

Enable resolution of dependency version ranges
----------------------------------------------

                 Key: MDEPLOY-82
                 URL: http://jira.codehaus.org/browse/MDEPLOY-82
             Project: Maven 2.x Deploy Plugin
          Issue Type: New Feature
            Reporter: Paul Gier


It would be helpful when deploying to be have the option to change the dependency version ranges to the specific version used during that build.  This would allow a version range in the local pom, but the deployed pom in the repository (and in the tag when releasing) would collapse the range into the version that was used during the build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MDEPLOY-82) Enable resolution of dependency version ranges

Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MDEPLOY-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier updated MDEPLOY-82:
-----------------------------

    Description: It would be helpful when deploying to be have the option to change the dependency version ranges to the specific version used during that build.  This would allow the local pom to contain a version range for one or more dependencies, but the deployed pom in the repository (and in the tag when releasing) would collapse the range into the version that was used during the build.  (was: It would be helpful when deploying to be have the option to change the dependency version ranges to the specific version used during that build.  This would allow a version range in the local pom, but the deployed pom in the repository (and in the tag when releasing) would collapse the range into the version that was used during the build.)

> Enable resolution of dependency version ranges
> ----------------------------------------------
>
>                 Key: MDEPLOY-82
>                 URL: http://jira.codehaus.org/browse/MDEPLOY-82
>             Project: Maven 2.x Deploy Plugin
>          Issue Type: New Feature
>            Reporter: Paul Gier
>
> It would be helpful when deploying to be have the option to change the dependency version ranges to the specific version used during that build.  This would allow the local pom to contain a version range for one or more dependencies, but the deployed pom in the repository (and in the tag when releasing) would collapse the range into the version that was used during the build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira