SoapUI not working without X since 5.1.0
Hi, i'm a SoapUI Pro user and already escalated this to support. Sadly there has been close to none useful response yet, other that a Bug has been filed (SOAP-2705). This issue is blocking our auto...
Forum Discussion
Thanks,
by the time i registered, i was not able to post at the "Pro" Forum yet. Indeed, 5.1.0 introduced several issues for unattended usage (e.g. as headless test-runner). One is the need to have a license file, i solved this by putting a license file to ~/.soapui before running the test. The dependency on X (resp. a non-headless JVM) however is a real issue which i cannot work-around easily without heavily modifying our test infrastructure.
Given that the data format also changed with 5.1.0 too, this is a major pain since i can't go back to an earlier version. I'd really appreciate if such core changes that influence operations would not be introduced from one minor update to the next. I understand that Smartbear wants to make money with software licenses, thats fine with me. Crippling the product in such a way that it loses most of its value to customers that heavily rely on test automation is a no-go.
Cheers,
Martin
by the time i registered, i was not able to post at the "Pro" Forum yet. Indeed, 5.1.0 introduced several issues for unattended usage (e.g. as headless test-runner). One is the need to have a license file, i solved this by putting a license file to ~/.soapui before running the test. The dependency on X (resp. a non-headless JVM) however is a real issue which i cannot work-around easily without heavily modifying our test infrastructure.
Given that the data format also changed with 5.1.0 too, this is a major pain since i can't go back to an earlier version. I'd really appreciate if such core changes that influence operations would not be introduced from one minor update to the next. I understand that Smartbear wants to make money with software licenses, thats fine with me. Crippling the product in such a way that it loses most of its value to customers that heavily rely on test automation is a no-go.
Cheers,
Martin
