maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Boué (JIRA) <j...@apache.org>
Subject [jira] [Commented] (MDEP-482) Can't use both outputProperty and outputFile in build-classpath mojo
Date Sat, 17 Dec 2016 20:43:58 GMT

    [ https://issues.apache.org/jira/browse/MDEP-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757584#comment-15757584
] 

Guillaume Boué commented on MDEP-482:
-------------------------------------

Fixed in [r1774803|http://svn.apache.org/viewvc?rev=1774803&view=rev].

> 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)

Mime
View raw message