It would be nice to be able to pass system properties to the plugin

[GoogleCodeExporter]

Majority of maven plugin intended to run integration test allow specifying 
system properties.

For example surefire plugin has following configuration:

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>2.8</version>
        <configuration>
          <systemPropertyVariables>
            <propertyName>propertyValue</propertyName>
            <buildDirectory>${project.build.directory}</buildDirectory>
            [...]
          </systemPropertyVariables>
        </configuration>

It would be great if maven robot plugin would allow also passing system 
properties.
Of course robot has --variable option, but it is not passed to java system 
property.

Original issue reported on code.google.com by bugg...@gmail.com on 6 Apr 2011 at 5:13

[GoogleCodeExporter]

This was intended to be an enhancement rather than defect

Original comment by bugg...@gmail.com on 6 Apr 2011 at 5:14

[GoogleCodeExporter]

Please explain where you want to access the system properties within your tests 
and why --variable is not sufficient for you.

Original comment by dietrich...@gmail.com on 9 Apr 2011 at 5:16

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

--variable approach is great for controlling user input, such as application 
information (for example, directing the robot test suite to a particular 
application url as a test target).
However, system properties seem to be conceptually more appropriate for 
application's global properties (such as tomcat, activeMq locations, etc) and 
can be invoked from java system property across multiple robot testsuite 
without having to explicitly pass it to all consumers.

Not having systemProperties is definitely not a show-stopper for us against 
using maven robot plugin, but it is a convenience adopted across the team 
already. 

Original comment by bugg...@gmail.com on 9 Apr 2011 at 11:59

[GoogleCodeExporter]

let's see if we can have this in by version 1.2

Original comment by mrmall...@gmail.com on 18 Apr 2011 at 10:09

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

as a workaround I'm using properties:set-system-properties

Original comment by TuomasKi...@gmail.com on 19 May 2011 at 12:43

[GoogleCodeExporter]

surefire was mentioned as example but it could be used to run robotframework 
altogether which would utilize all of the current and forthcoming maven 
features such as this system property issue. I think this project could 
function as surefire/failsafe provider as well.

http://maven.apache.org/plugins/maven-surefire-plugin/examples/providers.html

Original comment by TuomasKi...@gmail.com on 19 May 2011 at 1:09