wsalembi
Occasional Contributor
Joined 15 years ago
User Profile
User Widgets
Contributions
Publish parent pom soapui-project 5.4.0 in SmartBear maven repository
This file is missing in the SmartBear maven repository http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui-project/5.4.0/soapui-project-5.4.0.pom It is referenced from http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui/5.4.0/soapui-5.4.0.pom Can someone please publish it?1.3KViews0likes0CommentsRe: SoapUI 5.3 released!
Great news! Can you please add com.smartbear.soapui:soapui-project:pom:5.3.0 to your maven repository. The link does not exist, but is referenced by com.smartbear.soapui:soapui:pom:5.3.0 http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui-project/5.3.0 http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui/5.3.0/soapui-5.3.0.pom8.2KViews3likes0CommentsRe: soapui-maven-plugin 5.2.0 not published to SmartBear repository
Maybe the maven plugin is not available, still the repo is broken for the soapui artifacts. We maintain a list of plugins that compile against the soapui extension classes. We can't build for version 5.2.0 and 5.2.1 because of the missing project pom files. http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui/5.2.0/soapui-5.2.0.pom references http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui-project/5.2.0/soapui-project-5.2.0.pom (404 Not Found) http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui/5.2.1/soapui-5.2.1.pom references http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui-project/5.2.1/soapui-project-5.2.1.pom (404 Not Found)9.5KViews0likes0CommentsRe: soapui-maven-plugin 5.2.0 not published to SmartBear repository
Please fix this. I have the exact same problem with the project pom file for soapui 5.2.1. http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui-project/5.2.1 does not exist <parent> <groupId>com.smartbear.soapui</groupId> <artifactId>soapui-project</artifactId> <version>5.2.1</version> </parent>9.6KViews0likes2CommentsPublish parent pom soapui-project 5.2.1 in SmartBear maven repository
This file is missing in the SmartBear maven repository http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui-project/5.2.1/soapui-project-5.2.1.pom It is referenced from http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui/5.2.1/soapui-5.2.1.pom3KViews0likes1CommentMaven pom file missing
A pom file is missing in the SmartBear maven repository: http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui-project/5.2.1/soapui-project-5.2.1.pom This pom file is referenced from this soapui 5.2.1 library: http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui/5.2.1/soapui-5.2.1.pom732Views0likes0CommentsSupport for custom signature tokens (eg SAML Token Profile)
Please add support for custom signature tokens, similar to what wss4j currently offers. This allows SoapUI to implement more complex outgoing security configurations, like descibed in the OASIS SAML Token Profile specifications (eg SAML Holder-of-Key authentication using STS tokens). A pull request to implement this feature is already being submitted: https://github.com/SmartBear/soapui/pull/96 in February Thank you.1.5KViews0likes0CommentsRe: SoapUI request to WCF service with MTOM encoding failing - charset problem?
We had a similar problem with a client. Using MTOM, the Content-Transfer-Encoding mode should be binary in my opinion. Please check out this pull request: https://github.com/SmartBear/soapui/pull/391.4KViews0likes0CommentsRe: Content-transfer-enconding for text/xml attachments
SoapUI uses the mail api. The behavior is described here: http://docs.oracle.com/javaee/6/api/jav ... DataSource) If the primary type of this datasource is "text" and if all the bytes in its input stream are US-ASCII, then the encoding is "7bit". If more than half of the bytes are non-US-ASCII, then the encoding is "base64". If less than half of the bytes are non-US-ASCII, then the encoding is "quoted-printable".1.9KViews0likes0Comments