Contributions
Re: https://java.net/projects/maven-repository): hostname in certificate didn't match: during mvn run
We tried withhttps://rapi.tools.ops.smartbear.io/nexus/content/groups/public as URL and also with<url>http://smartbearsoftware.com/repository/maven2</url> however it resolved down tohttps://java.net/projects/maven-repository😞 hostname in certificate didn't match: during mvn run It used you work before.. However for sometime now.. it is not working3 years agoPlace ReadyAPI QuestionsReadyAPI Questions1KViews0likes1Commenthttps://java.net/projects/maven-repository): hostname in certificate didn't match: during mvn run
[ERROR] Failed to execute goal com.smartbear:ready-api-maven-plugin:3.1.0:test (default) on project cm: Execution default of goal com.smartbear:ready-api-maven-plugin:3.1.0:test failed: Plugin com.smartbear:ready-api-maven-plugin:3.1.0 or one of its dependencies could not be resolved: Could not transfer artifact com.smartbear:ready-api:jar:3.1.0 from/to SmartBearPluginRepository (https://java.net/projects/maven-repository): hostname in certificate didn't match: <java.net> != <*.java.net> OR <*.java.net> -> [Help 1] <pluginRepositories> <pluginRepository> <id>SmartBearPluginRepository</id> <url>https://java.net/projects/maven-repository</url> </pluginRepository> </pluginRepositories> The above repo is used for <plugin> <!--Plugin groupID used to uniquely identify the project with the plugin.--> <groupId>com.smartbear</groupId> <!--Plugin artifactId used to find the plugin in the project.--> <artifactId>ready-api-maven-plugin</artifactId> <!--Specifies your Ready! API version. Maven will use the appropriate plugin version.--> <!-- IMPORTANT: Must be the same as your Ready! API version.--> <version>3.1.0</version> <dependencies> <dependency> <groupId>com.smartbear</groupId> <artifactId>ready-api-soapui</artifactId> <version>3.1.0</version> </dependency> <dependency> <groupId>com.smartbear</groupId> <artifactId>ready-api-soapui-pro</artifactId> <version>3.1.0</version> </dependency> <dependency> <groupId>com.smartbear</groupId> <artifactId>ready-api</artifactId> <version>3.1.0</version> </dependency>Solved3 years agoPlace ReadyAPI QuestionsReadyAPI Questions1KViews0likes3CommentsRe: OAUTH2.0 Implementation is not working in Jenkins
Have attached the Logs.. I have created a OAUTH Profile and added Automation Scripts in the Scripts tab to have it accessed everytime the token needs to be refreshed. I have a REST steps which demands OAUTH I have added the below code inRequestFilter.filterRequest Event // Import the required classes import com.eviware.soapui.impl.rest.actions.oauth.OltuOAuth2ClientFacade; import com.eviware.soapui.support.editor.inspectors.auth.TokenType; import com.eviware.soapui.model.support.ModelSupport; import com.teamdev.jxbrowser.*; // Get a project def project = ModelSupport.getModelItemProject(context.getModelItem()); // Get the needed authorization profile def authProfile = project.getAuthRepository().getEntry("My Profile"); //Create a facade object def tokenType = TokenType.ACCESS; def oAuthFacade = new OltuOAuth2ClientFacade(tokenType); // Request an access token in headless mode and assign it to the authorization profile we got earlier oAuthFacade.requestAccessToken(authProfile, true, true); // Access token retrieval may take time, so we need to pause the execution for 3 seconds to finish it. You may increase this value if needed. sleep(3000); // Posts a new token to the script log log.info("Set new token: " + authProfile.getAccessToken()); I have tried the same withSubmitListener.beforeSubmit Event as well Both works perfectly in Local windows machine. However when I trigger the job in jenkins (linux) it throws the error that chromium is not intialised clean test -Djxbrowser.chromium.dir=/apps/jenkins-agent/.m2/repository/com/teamdev/.jxbrowser -Djava.awt.headless=false is my MVN command in Jenkins3 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes0CommentsOAUTH2.0 Implementation is not working in Jenkins
I have created the OAUTH2.0 profile as specified in ReadyAPI support page and also included a Groovy Script to get the fresh token always. It all works perfectly in local but in Jenkins it is throwing the error3 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.7KViews0likes2CommentsCan I pass the floating license as an Maven Argument??
Can I pass the floating license as an Maven Argument?? Executing Maven: -B -f /apps/jenkins-agent/workspace...../pom.xml clean test -e -DSuiteName=ITRN3-SmokeTest-Cycle1 -e LICENSE_SERVER=xx.xx.xxx.xxx:xxxx did not workSolved1.2KViews0likes1CommentRe: Failed to parse plugin descriptor for com.smartbear:ready-api-soapui-pro:3.3.0
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.smartbear:ready-api-maven-plugin:3.2.0:test (default) on project kpifoff: Execution default of goal com.smartbear:ready-api-maven-plugin:3.2.0:test failed: Unable to load the mojo 'test' in the plugin 'com.smartbear:ready-api-maven-plugin:3.2.0' due to an API incompatibility: org.codehaus.plexus.component.repository.exception.ComponentLookupException: com/eviware/soapui/maven2/TestMojo has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 I'm still facing the issue.. I tried it by downgrading the ReadyAPI versions too4 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.6KViews0likes2CommentsFailed to parse plugin descriptor for com.smartbear:ready-api-soapui-pro:3.3.0
Error while building Ready API project using Maven POM Failed to parse plugin descriptor for com.smartbear:ready-api-soapui-pro:3.3.0 (/apps/jenkins-agent/.m2/repository/com/smartbear/ready-api-soapui-pro/3.3.0/ready-api-soapui-pro-3.3.0.jar): No plugin descriptor found at META-INF/maven/plugin.xml POM: <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com</groupId> <artifactId>cm</artifactId> <packaging>maven-plugin</packaging> <version>1.0-SNAPSHOT</version> <name>me</name> <url>http://maven.apache.org</url> <properties> <aspectj.version>1.8.10</aspectj.version> </properties> <pluginRepositories> <pluginRepository> <id>SmartBearPluginRepository</id> <url>http://www.soapui.org/repository/maven2/</url> </pluginRepository> </pluginRepositories> <build> <plugins> <plugin> <groupId>com.smartbear</groupId> <artifactId>ready-api-soapui-pro</artifactId> <version>3.3.0</version> <dependencies> <!-- dependency><groupId>mysql</groupId><artifactId>mysql-connector-java</artifactId><version>5.1.6</version></dependency--> <dependency> <groupId>mysql</groupId> <artifactId>mysql-connector-java</artifactId> <version>3.3.05</version> <scope>runtime</scope> </dependency> <!-- <dependency> <groupId>com.smartbear</groupId> <artifactId>ready-api-core</artifactId> <version>3.3.0</version> </dependency> <dependency> <groupId>com.smartbear</groupId> <artifactId>ready-api-soapui</artifactId> <version>3.3.0</version> </dependency> <dependency> <groupId>com.smartbear</groupId> <artifactId>ready-api-runners</artifactId> <version>3.3.0</version> </dependency> <dependency> <groupId>org.apache.maven</groupId> <artifactId>maven-plugin-api</artifactId> <version>2.0</version> </dependency> --> <dependency> <groupId>com.smartbear</groupId> <artifactId>ready-api-maven-plugin</artifactId> <version>3.3.0</version> <type>maven-plugin</type> <!-- </dependency> <dependency> <groupId>com.smartbear.soapui</groupId> <artifactId>soapui-pro-maven-plugin</artifactId> <version>3.3.0</version> --> <exclusions> <!-- These are mainly GUI artifacts not needed in the headless test runner --> <!-- TODO We might also want to remove: fife:rsyntaxtextarea. It's included in prior versions (< 4.5.2) though --> <!-- JGoodies --> <exclusion> <groupId>javafx</groupId> <artifactId>jfxrt</artifactId> </exclusion> <exclusion> <groupId>com.jgoodies</groupId> <artifactId>forms</artifactId> </exclusion> <exclusion> <groupId>com.jgoodies</groupId> <artifactId>looks</artifactId> </exclusion> <exclusion> <groupId>com.jgoodies</groupId> <artifactId>binding</artifactId> </exclusion> </exclusions> </dependency> <!-- https://mvnrepository.com/artifact/org.codehaus.groovy/groovy-all --> <dependency> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-all</artifactId> <version>2.4.17</version> </dependency> <!-- https://mvnrepository.com/artifact/org.ini4j/ini4j --> <dependency> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-all</artifactId> <version>2.4.17</version> </dependency> <!-- https://mvnrepository.com/artifact/org.apache.poi/poi --> <dependency> <groupId>org.apache.poi</groupId> <artifactId>poi</artifactId> <version>3.12</version> </dependency> <!-- https://mvnrepository.com/artifact/org.apache.poi/poi-ooxml --> <dependency> <groupId>org.apache.poi</groupId> <artifactId>poi-ooxml</artifactId> <version>3.12</version> </dependency> <!-- https://mvnrepository.com/artifact/org.apache.poi/poi-ooxml-schemas --> <dependency> <groupId>org.apache.poi</groupId> <artifactId>poi-ooxml-schemas</artifactId> <version>3.12</version> </dependency> <dependency> <groupId>org.ini4j</groupId> <artifactId>ini4j</artifactId> <version>0.5.4</version> </dependency> <dependency> <groupId>com.oracle.ojdbc</groupId> <artifactId>ojdbc8</artifactId> <version>19.3.0.0</version> </dependency> <!-- https://mvnrepository.com/artifact/net.sf.jasperreports/jasperreports --> <!-- dependency><groupId>com.oracle</groupId><artifactId>ojdbc</artifactId><version>8</version><scope>system</scope><systemPath>${basedir}/bin/ext/ojdbc8.jar</systemPath></dependency--> <!-- dependency><groupId>com.smartbear</groupId><artifactId>ready-api</artifactId><version>3.1.0</version><scope>system</scope><systemPath>${project.basedir}/lib/ready-api-maven-plugin-3.1.0.jar</systemPath></dependency--> <!-- https://mvnrepository.com/artifact/net.sf.jasperreports/jasperreports --> <dependency> <groupId>net.sf.jasperreports</groupId> <artifactId>jasperreports</artifactId> <version>6.4.0</version> </dependency> <dependency> <groupId>org.reflections</groupId> <artifactId>reflections</artifactId> <version>0.9.10</version> </dependency> <dependency> <groupId>com.jgoodies</groupId> <artifactId>forms</artifactId> <version>1.0.7</version> </dependency> <dependency> <groupId>io.qameta.allure</groupId> <artifactId>allure-junit4</artifactId> <version>2.13.5</version> </dependency> <!-- <dependency><groupId>io.qameta.allure</groupId><artifactId>allure-maven</artifactId><version>2.10.0</version></dependency> --> </dependencies> <configuration> <settingsFile>${basedir}/soapui-settings.xml</settingsFile> <junitReport>true</junitReport> <printReport>true</printReport> <coverage>${basedir}/reports</coverage> <testSuite>${SuiteName}</testSuite> <soapuiProperties> <property> <name>soapui.ext.libraries</name> <value>${basedir}/bin/ext</value> </property> <property> <name>soapui.home</name> <value>${basedir}/bin</value> </property> </soapuiProperties> </configuration> <executions> <execution> <phase>test</phase> <goals> <goal>test</goal> </goals> <configuration> <projectFile>${project.basedir}/SoapuiProject/CAMS/CAMS-API-Services-soapui-project.xml</projectFile> <!-- exportAll>true</exportAll--> <!-- reportFormat>HTML</reportFormat--> <!-- printReport>true</printReport--> <!-- junitReport>true</junitReport--> <!--coverage>true</coverage--> <!--exportAll>true</exportAll--> <reportFormat>PDF</reportFormat> <reportType>"Project Report"</reportType> <testFailIgnore>true</testFailIgnore> <reports>${basedir}/Report</reports> <reportName>"Project Report"</reportName> <!-- outputFolder>${basedir}/target/surefire-reports</outputFolder--> <outputFolder>${basedir}/SoapuiProject/CAMS/ReqRespPair</outputFolder> <projectProperties> <value>message=Hello World!</value> </projectProperties> </configuration> </execution> </executions> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.16</version> </plugin> </plugins> </build> <reporting> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-report-plugin</artifactId> <version>3.0.0-M4</version> <!-- ${shadedVersion}, but resolved due to https://issues.apache.org/jira/browse/MRELEASE-799 --> <reportSets> <reportSet> <reports> <report>report-only</report> </reports> </reportSet> </reportSets> <configuration> <outputName>Automation-Execution Report</outputName> <outputDirectory>${basedir}/report</outputDirectory> <reportsDirectory>${basedir}/report/soapui</reportsDirectory> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-site-plugin</artifactId> <version>3.7.1</version> <configuration> <outputDirectory>${basedir}/target/surefire-reports</outputDirectory> </configuration> </plugin> </plugins> </reporting> </project>Solved4 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.8KViews0likes6Comments