Forum Discussion

cbyndr's avatar
cbyndr
Contributor
16 years ago

-Gsoapui.properties and/or -Dsoapui.properties

Been trying to set these options from the command line, as such:

sh soapui-pro.sh -Dsoapui.properties=bsftm.appdev02.properties

But soapui always throws this:

org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option: -D
at org.apache.commons.cli.Parser.processOption(Parser.java:253)
at org.apache.commons.cli.Parser.parse(Parser.java:170)
at org.apache.commons.cli.Parser.parse(Parser.java:114)
at com.eviware.soapui.SoapUI.startSoapUI(SoapUI.java:733)
at com.eviware.soapui.SoapUIPro.b(SourceFile:264)
at com.eviware.soapui.SoapUIPro.a(SourceFile:189)
at com.eviware.soapui.SoapUIPro$SoapUIProRunner.run(SourceFile:1137)
at com.eviware.soapui.SoapUIPro.main(SourceFile:230)

And fails to launch.

What am I missing? I have added bsftm.appdev02.properties to /bin.

7 Replies

  • cbyndr's avatar
    cbyndr
    Contributor
    16 years ago
    If it helps to know, I get hit with the same issue using Gsoapui.properties.
  • cbyndr's avatar
    cbyndr
    Contributor
    16 years ago
    OK, that appears to have straightened things out. Thank you!

    When it comes to using testrunner, we should set these properties from the command line though, correct?
  • cbyndr's avatar
    cbyndr
    Contributor
    16 years ago
    Thanks. So, here is my dilemma now. I have two properties files, with info for endpoint, etc., to be used by the builder for two different builds. And soapui testrunner command looks like this:

    bin/testrunner.sh -j -r -Dsoapui.properties=${soapui.properties} -f${basedir}/target/integrationTestOutput -t${soapui-location}/soapui-settings.xml -sintegrationtests ${basedir}/unittest/integrationtest/soapui_project

    When we build and testrunner launches, soapui logs this out:

    30-Jun-2010 15:30:17 [exec] 2010-06-30 15:30:17,951 [Main Thread] INFO com.eviware.soapui.SoapUIProTestCaseRunner - Setting global property [soapui.properties] to [bstfm.appdev02.properties]

    So based on that log, soapui could be using the correct properties, but it seems to be getting its global properties from soapui-settings.xml, instead of the properties file.