[
http://jira.codehaus.org/browse/MDEP-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146312#action_146312
]
Dan Tran commented on MDEP-178:
-------------------------------
I prefer to run the in a pom and configure the localRepository to a string,
this way this plugin can contruct a new localrepo instance and write in there
:-)
btw dependency:copy pulls the artifact down to local repo and copy it to target
dir.
> Create a goal to download single artifact transitively
> ------------------------------------------------------
>
> Key: MDEP-178
> URL: http://jira.codehaus.org/browse/MDEP-178
> Project: Maven 2.x Dependency Plugin
> Issue Type: New Feature
> Reporter: Dan Fabulich
> Assignee: Dan Fabulich
> Fix For: 2.1
>
>
> I've always found it to be a hassle to test plugins that don't need to be
> wired up in POM files, e.g. the archetype, dependency, scm plugins. I find
> that to test them I have to create a dummy POM file with a
> <pluginRepositories> section, as described in our guide to testing staged
> releases.
> http://maven.apache.org/guides/development/guide-testing-releases.html
> I thought it would be cool to have a downloader goal that let you do this:
> mvn dependency:get
> -Dartifact=org.apache.maven.plugins:maven-scm-plugin:1.1
> -DrepoUrl=http://people.apache.org/~olamy/staging-repo
> That would retrieve the plugin into your local repository, so you could
> immediately start using it.
> mvn org.apache.maven.plugins:maven-scm-plugin:1.1:checkin -Dmessage=foo
--
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
