maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MINVOKER-20) Make properties specified for invocations conform with standard properties syntax, and avoid 'test' specific configuration name
Date Sat, 15 Dec 2007 22:54:04 GMT

     [ http://jira.codehaus.org/browse/MINVOKER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Casey updated MINVOKER-20:
-------------------------------

    Fix Version/s: 1.1

> Make properties specified for invocations conform with standard properties syntax, and
avoid 'test' specific configuration name
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MINVOKER-20
>                 URL: http://jira.codehaus.org/browse/MINVOKER-20
>             Project: Maven 2.x Invoker Plugin
>          Issue Type: Improvement
>    Affects Versions: 1.0
>            Reporter: John Casey
>            Assignee: John Casey
>             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 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

        

Mime
View raw message