[
https://issues.apache.org/jira/browse/MINVOKER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958275#comment-17958275
]
Olivier Lamy commented on MINVOKER-20:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-invoker-plugin#343|https://github.com/apache/maven-invoker-plugin/issues/343].
> Make properties specified for invocations conform with standard properties
> syntax, and avoid 'test' specific configuration name
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: MINVOKER-20
> URL: https://issues.apache.org/jira/browse/MINVOKER-20
> Project: Maven Invoker Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 1.0
> Reporter: John Dennis Casey
> Assignee: John Dennis Casey
> Priority: Major
> Fix For: 1.1
>
>
> Currently, to pass parameters in via the command line of invoked builds, you
> must specify:
> {code}
> <testProperties>
> <property>
> <name>key</name>
> <value>someValue</value>
> </property>
> </testProperties>
> {code}
> This causes problems, mainly because it's inconsistent with other plugins'
> syntax for properties, and also because the invoker has a wider set of use
> cases than just for integration testing. This parameter should be deprecated
> in favor of a new parameter, simply called 'properties', that uses the
> standard {code}<key>value</key>{code} syntax.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
