[
https://issues.apache.org/jira/browse/MDEP-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MDEP-390.
-------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still persists, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> org.apache.maven.plugins:maven-dependency-plugin:unpack to support
> remoteRepositories
> -------------------------------------------------------------------------------------
>
> Key: MDEP-390
> URL: https://issues.apache.org/jira/browse/MDEP-390
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: unpack
> Affects Versions: 2.5.1
> Reporter: Mickael Istria
>
> As a user, I'd like to download a Maven artifact from command-line and get it
> unzipped.
> In order to use the maven-depdenceny-plugin:goal as the ultimate command-line
> client to download a maven artifact (not necessarly in the context of a
> project), it would be useful to add to it an "unpack" parameter that would
> allow to unpack the just-downloaded stuff.
> When in comes to automating download+unzip of an artifact in CI:
> Currently, one has to add a Shell or Ant or Groovy script to unzip, after
> using "mvn org.apache.maven.plugins:maven-dependency-plugin:2.5.1:get
> -Dartifact=blah:blah:1.0 -DremoteRepositories=http://somewhere";. It's not
> very convenient as this requires usage of another Ant or Groovy file, or
> usage of a platform-specific interpreter.
> Also note that the unpack-mojo can't fit this use-case since it's not
> configurable via command-line (can't set artifactItems nor
> remoteRepositories).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
