Contributions
Re: SoapUI-5.2.1 testrunner.sh is not handling option -t to load custom soapui-settings.xml
The problem is not limited to that option, but also to passing java system properties which are not properly interpreted. This has been reporting in a log4j configuration issue ticket.1.4KViews0likes0CommentsUse own Log4j configuration
I'm launching TestRunner from the command line with some system properties. Among them, "soapui.log4j.config" to override logging configuration for SOAPUI. E.g. testrunner.bat -Dsoapui.log4j.config="my_log4j.xml" ... -s MySuite project.xml Since migration to SOAPUI 5.2, my configuration is not taken into account. In SOAPUI 5.0, there wasan output as follows: Configuring log4j from [...\my_log4j.xml] This output is expected as perinitLog method inDefaultSoapUICore class: protected void initLog() { if( !logIsInitialized ) { String logFileName = System.getProperty( SoapUISystemProperties.SOAPUI_LOG4j_CONFIG_FILE, "soapui-log4j.xml" ); File log4jconfig = root == null ? new File( logFileName ) : new File( new File( getRoot() ), logFileName ); if( log4jconfig.exists() ) { System.out.println( "Configuring log4j from [" + log4jconfig.getAbsolutePath() + "]" ); DOMConfigurator.configureAndWatch( log4jconfig.getAbsolutePath(), 5000 ); } ... Any idea why such a regression? I need this to work as I wantto use JSONPath assertions.1.6KViews0likes0Comments