Generate Documentation for API output has minor (but important) HTML discrepancy
I am screen scraping HTML from the report created by "Generate Documentation". I am pulling the outer HTML for the <li> tag in the report for each entry point; the <li> tags have a class attribute of "operation"...except for the last entry point on the report. This makes it impossible to find the last entry point's doco as the <li> is not included in VBA getElementsByClassName("operation"). Example from inspect of the report (last highlighted <li> is missing "class=operation":Bug: soapui-maven-plugin:5.2.1 + IBM JDK 1.7: Could not find artifact javafx:jfxrt:jar:2.2
For some reasong soapui-maven-plugin:5.2.1 looks for JavaFX (why?). AFAIK, the IBM JDK does not ship JavaFX, however. I'm getting the error: Execution soapUI-tests of goal com.smartbear.soapui:soapui-maven-plugin:5.2.1:test failed: Plugin com.smartbear.soapui:soapui-maven-plugin:5.2.1 or one of its dependencies could not be resolved: Could not find artifact javafx:jfxrt:jar:2.2 at specified path [...] It works with version 4.6.1, but then I'm getting the following warning: Project 'application' is from a newer version (5.2.1) of SoapUI than this (4.6.1) and parts of it may be incompatible or incorrect. Saving this project with this version of SoapUI may cause it to function differently. Please also note that it's not very clear from the documentation which version we should use: https://www.soapui.org/test-automation/maven/maven-2-x.html
SoapUI 5.1.3 Bug: SoapUI.isCommandLine() not working as expected
Hi SmartBear team I am not sure if this is the right place to file a bug - please let me know if this post belongs elsewhere :) I developeda listener for SoapUI, and used the SoapUI.isCommandLine() command to detect when the tool is invoked from the command line. This was working fine with version 5.0.0 for which I developed the listener originally. I upgraded recently to 5.1.3 and noticed that this particular command is not working as expected. The command always returns False, regardless of whether I run the tool from the UI or the command line. Please let me know if you need further details.
