-
Notifications
You must be signed in to change notification settings - Fork 27
No "import Swagger" option available 2.5.1 plugin - SOAP UI 5.2.1 #51
Comments
Thanks - unfortunately SoapUI is currently incompatible with the latest Swagger plugin - perhaps you can try to build the https://github.com/SmartBear/soapui/tree/add-sampleContent-to-restrepresentation branch to get it working with the 2.2 version for now? |
That did it, thank you sir |
welcome - thanks for confirming! |
Hi @olensmar, probably not the best place to ask, but it is worth it: how are you guys seeing the support of SoapUI for Swagger (and other) plugins? I took a look on SoapUI Next branch and there's not much happening there. I understand that w/out Package Manager and no Swagger 2.0 plugin, SoapUI OS is not a mock option anymore. Am I loosing anything here? Thank you! |
Hi! We definitely wan't SoapUI to have up-to-date Swagger support - the recent 5.3.0 release updated the bundled Swagger plugin - so it should be much better now. Are you missing something specific that we need to make sure makes it into next? Thanks for reaching out! |
Are we both talking about SoapUI Open Source, right?
Installed 5.3.0 yesterday and got no swagger bundled plugin. But I'm on
Linux 64 bits, and the tarball doesn't include plugins, so I tried getting
the latest swagger plugin from GitHub and dropping it on plugins folder,
but got a message saying that only SmartBear signed plugins can be used.
Am I confusing anything here? Probably yes, so any help is greatly
appreciated. :)
Tks!
|
hm... let us follow up on this - sorry about the confusion - will get back to you! |
Thank you in advance! We always used SoapUI as a mock for development and with our API being defined in Swagger looked like the perfect fit. The "only SmartBear plugins" policy deployed in 5.2 broke everything though. I understand the money behind the decision, but got little bit disappointed as SoapUI always had an open source mindset. Hope you guys can figure it out a way to keep things going. |
Hi, we added support for Swagger 2.0 in SoapUI OS 5.3.0 as a bundled plugin, but apparently it is missing in the tarball. We're trying to solve the issue as fast as possible. Maybe you could try installing the linux version using the installer and then copy the plugin from that installation, as a temporary solution. |
Hey @mattihjelm, sorry for the delay, I just could give it a try yesterday. Tried installing SoapUI 5.2 and 5.3 (both Linux x64) but couldn't find a plugins folder. Where is the plugin located in the installation folder? |
I do observe the same with 5.3 windows x64 bit installation that I did today. I couldn't find any plugin folder in the installation location. However when I downloaded itand copied the plugin to bin folder I got the import swagger definition option. |
Was this issue ever resolved? Being able to import my Swagger definitions would make SoapUI a lot more attractive. |
I haven't checked newer versions of SoapUI since then but, at the time, I wasn't able to make it work. I understand it as a commercial decision (it will only be supported in paid version). |
After downloading and unzipping https://github.com/SmartBear/readyapi-swagger-plugin/releases/download/2.5.1/soapui-swagger-plugin-2.5.1-dist.jar to the ..\SoapUi\bin folder as per the readme, and moving the soapui-swagger-plugin-2.2-dist.jar out of the SoapUi plugins folder, the Import Swagger option fails to appear on the REST project. Replacing the 2.2 jar with soapui-swagger-plugin-2.5.1-dist.jar results in the same issue.
Leaving the soapui-swagger-plugin-2.2-dist.jar in plugins shows the import option, but I can't verify which version is being used.
The reason I'm trying to upgrade the plugin is due to the following error when trying to import a .json spec verified as valid by the Swagger editor.
The text was updated successfully, but these errors were encountered: