[
https://issues.apache.org/jira/browse/MDEP-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757603#comment-15757603
]
Hudson commented on MDEP-482:
-----------------------------
SUCCESS: Integrated in Jenkins build maven-plugins #7797 (See
[https://builds.apache.org/job/maven-plugins/7797/])
[MDEP-482] Can't use both outputProperty and outputFile in build-classpath mojo
Submitted by: Dagan Sandler
Make sure outputFile and outputProperty can both be used at the same time.
Applied patch after adding an IT. (gboue:
[http://svn.apache.org/viewvc/?view=rev&rev=1774803])
* (add)
maven-dependency-plugin/src/it/projects/build-classpath-output-file-and-property
* (add)
maven-dependency-plugin/src/it/projects/build-classpath-output-file-and-property/invoker.properties
* (add)
maven-dependency-plugin/src/it/projects/build-classpath-output-file-and-property/pom.xml
* (add)
maven-dependency-plugin/src/it/projects/build-classpath-output-file-and-property/test.properties
* (add)
maven-dependency-plugin/src/it/projects/build-classpath-output-file-and-property/verify.bsh
* (edit)
maven-dependency-plugin/src/main/java/org/apache/maven/plugins/dependency/fromDependencies/BuildClasspathMojo.java
> Can't use both outputProperty and outputFile in build-classpath mojo
> --------------------------------------------------------------------
>
> Key: MDEP-482
> URL: https://issues.apache.org/jira/browse/MDEP-482
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: build-classpath
> Affects Versions: 2.10
> Reporter: Dagan Sandler
> Priority: Minor
> Attachments: MDEP-482-maven-dependency-plugin.patch
>
>
> When defining the configuration for the dependency:build-classpath mojo, a
> user can use either <outputProperty> and <outputFile> to define the desired
> output of the classpath string. These both work as expected.
> However, if the user wishes to use both output methods in conjunction, the
> <outputFile> gets discarded and only <ouputProperty> is used.
> A current workaround that achieves the desired missing behavior involves
> defining two different executions for the mojo only differing by the output
> method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
