You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Tran (JIRA)" <ji...@codehaus.org> on 2009/12/31 03:02:55 UTC
[jira] Closed: (MDEP-155) writing classpath into a file doesn't
work anymore
[ http://jira.codehaus.org/browse/MDEP-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Tran closed MDEP-155.
-------------------------
Resolution: Fixed
Fix Version/s: 2.2
Fixed at
Revision: 894760
Author: dantran
Date: 6:01:57 PM, Wednesday, December 30, 2009
Message:
MDEP-155: corrected build-classpath mojo usage
----
Modified : /maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt.vm
> writing classpath into a file doesn't work anymore
> --------------------------------------------------
>
> Key: MDEP-155
> URL: http://jira.codehaus.org/browse/MDEP-155
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.0
> Environment: Maven version: 2.0.8
> Java version: 1.5.0_13
> OS name: "mac os x" version: "10.4.11" arch: "i386" Family: "unix"
> Reporter: Marc Guenther
> Assignee: Brian Fox
> Priority: Minor
> Fix For: 2.2
>
>
> The following command from the Usage section (http://maven.apache.org/plugins/maven-dependency-plugin/usage.html) does not work anymore:
> mvn dependency:build-classpath -Dmaven.dep.cpFile=cp.txt
> It writes the classpath to the log, not to the specified file.
> This used to wirk in 2.0-alpha-4.
> Using outputFile doesn't work either.
> Another question: where does the "maven.dep." prefix come from? This isn't documented anywhere.
--
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