You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Guillaume Boué (JIRA)" <ji...@apache.org> on 2016/12/17 20:58:58 UTC
[jira] [Closed] (MDEP-482) Can't use both outputProperty and
outputFile in build-classpath mojo
[ https://issues.apache.org/jira/browse/MDEP-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Boué closed MDEP-482.
-------------------------------
Resolution: Fixed
Assignee: Guillaume Boué
Fix Version/s: 3.0.1
> 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
> Assignee: Guillaume Boué
> Priority: Minor
> Fix For: 3.0.1
>
> 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)