You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Cedric Lavanchy (JIRA)" <ji...@apache.org> on 2016/07/08 06:02:11 UTC
[jira] [Commented] (MDEP-526) copy and copy-dependencies should
take latest release version from version range
[ https://issues.apache.org/jira/browse/MDEP-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367272#comment-15367272 ]
Cedric Lavanchy commented on MDEP-526:
--------------------------------------
It would be good to have that improvement for the goal "unpack" as well.
> copy and copy-dependencies should take latest release version from version range
> --------------------------------------------------------------------------------
>
> Key: MDEP-526
> URL: https://issues.apache.org/jira/browse/MDEP-526
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: copy, copy-dependencies
> Reporter: abhishek sinha
> Priority: Minor
> Labels: features, newbie
>
> In my pom, I have specified version range in properties like:
> <model.base.test.version>[1.3.16, 1.4.0-SNAPSHOT)</model.base.test.version>
> Currently copy and copy-dependency goals will copy latest SNAPSHOT jar to specified output directory.
> My requirement is to have have a configuration which allows to copy latest released jar from the specified version range.
> I checked out source code for maven-dependency-plugin and did some modification to make it work. So if this improvement is accepted then how can I contribute to the solution I have.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)