Forum Discussion

hduong_1's avatar
hduong_1
New Contributor
14 years ago

Missing dependencies in repository for maven-soapui-plugin

Hi,

I'm trying to use the maven-soapui-plugin but the tests are failing when executed via the maven plugin, although they pass when run inside SoapUI itself. When running the plugin, I get the following failed test due to a JUnit ComparisonFailure:

SoapUI 3.6 TestCaseRunner Summary
-----------------------------
Time Taken: 1236ms
Total TestSuites: 1
Total TestCases: 1 (1 failed)
Total TestSteps: 1
Total Request Assertions: 1
Total Failed Assertions: 1
Total Exported Results: 1
[ERROR] java.lang.Exception: XPath Match in [Warning if text # of char=0] failed;
[junit/framework/ComparisonFailure]
Status: FAILED
Time Taken: 85
Size: 218
Timestamp: Wed Feb 02 10:41:48 EST 2011
TestStep: Warning if text # of char=0


When running the Maven project, it seems that the plugin is trying to find libraries that do not exist inside the eviware repository. This is the warning message I receive when running the Maven project:

[WARNING] POM for 'junit:junit:pom:4.4:runtime' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for 'commons-jexl:commons-jexl:pom:1.0:runtime' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for 'xalan:xalan:pom:2.7.1:runtime' is invalid.
Its dependencies (if any) will NOT be available to the current build.


I checked in the repository at http://www.eviware.com/repository/maven2/, and indeed all those libraries do not exist in the repository. Can someone take a look and make sure the repository is up-to-date with soapui's dependencies. The problem exists for v3.5.1 and v3.6.1 of the soapui plugin.

Thanks,
-hd

11 Replies

Sort By
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    14 years ago
    Hi,

    I've updated these particular dependencies in the repository. Could you please try again and let us know if you still have problems.

    Regards,
    Dragica
    /www.eviware.com
  • hduong_1's avatar
    hduong_1
    New Contributor
    14 years ago
    Hi,

    It looks like it can't find commons-jexl. I think it is placed in the wrong path in the eviware repository.



    Downloading: http://www.eviware.com/repository/maven2/commons-jexl/commons-jexl/1.0/commons-jexl-1.0.pom
    [INFO] Unable to find resource 'commons-jexl:commons-jexl:pom:1.0' in repository eviwarePluginRepository (http://www.eviware.com/repository/maven2)
    Downloading: http://www.eviware.com/repository/maven2/commons-jexl/commons-jexl/1.0/commons-jexl-1.0.pom
    [INFO] Unable to find resource 'commons-jexl:commons-jexl:pom:1.0' in repository eviwareRepository (http://www.eviware.com/repository/maven2)
         
    Downloading: http://www.eviware.com/repository/maven2/commons-jexl/commons-jexl/1.0/commons-jexl-1.0.jar
    [INFO] Unable to find resource 'commons-jexl:commons-jexl:jar:1.0' in repository eviwarePluginRepository (http://www.eviware.com/repository/maven2)
    Downloading: http://www.eviware.com/repository/maven2/commons-jexl/commons-jexl/1.0/commons-jexl-1.0.jar
    [INFO] Unable to find resource 'commons-jexl:commons-jexl:jar:1.0' in repository eviwareRepository (http://www.eviware.com/repository/maven2)
  • pcornish's avatar
    pcornish
    New Contributor
    13 years ago
    Guys,

    I'm now seeing this behaviour for version 4 of the maven-soapui-plugin. Assertions pass in soapUI 4.0.0 but fail when the project is run via the Maven plugin.

    The XPath assertions pass fine using version 3.6.1 of the plugin, but fail with the following error when using 4.0.0 or 4.0.0-SNAPSHOT dependencies.


    Status: FAILED
    Time Taken: 2740
    Size: 1891
    Timestamp: Wed Jul 06 17:55:19 BST 2011
    TestStep: Request


    ----------------- Messages ------------------------------
    [Check status] junit/framework/ComparisonFailure


    I don't know if this affects the result or not, but here's some related Maven output when running the plugin:

    Downloading: http://dhav10:8180/artifactory/repo/bouncycastle/bcprov-jdk15/144/bcprov-jdk15-144.pom
    [INFO] Unable to find resource 'bouncycastle:bcprov-jdk15:pom:144' in repository central (http://dhav10:8180/artifactory/repo)
    Downloading: http://www.eviware.com/repository/maven2/bouncycastle/bcprov-jdk15/144/bcprov-jdk15-144.pom
    [INFO] Unable to find resource 'bouncycastle:bcprov-jdk15:pom:144' in repository eviwareRepository (http://www.eviware.com/repository/maven2)
    Downloading: http://dhav10:8180/artifactory/repo/bouncycastle/bcprov-jdk15/144/bcprov-jdk15-144.pom
    [INFO] Unable to find resource 'bouncycastle:bcprov-jdk15:pom:144' in repository central (http://dhav10:8180/artifactory/repo)
    [INFO] [soapui:test {execution: com.tescobank.tbsb.integrationtest.soapui}]


    Any ideas why?

    Pete
  • deeRavin's avatar
    deeRavin
    New Contributor
    13 years ago
    Is the comparison failure problem fixed by the adding the dependency with version 4 ?
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    13 years ago
    Hi,

    yes - we missed this dependency - admittedly very stupid of us - please try the 4.0.2-SNAPSHOT version of the plugin instead - does that work any better?

    regards!

    /Ole
    SmartBear Software
  • vascofigueira's avatar
    vascofigueira
    New Contributor
    13 years ago
    SmartBear Support wrote:

    yes - we missed this dependency - admittedly very stupid of us - please try the 4.0.2-SNAPSHOT version of the plugin instead - does that work any better?

    Yes it does. Seems resolved. Thank you.

    What about having other dependencies directly accessible as well? The ones that would go into ext/ in non-maven executions could be passed along to the classpath of SoapUI running process through the maven-soapui-plugin. In this way we would not need to setup an ext/ directory with extra jars and would just rely on maven dependencies (for the test scope).

    Especially in multi-module maven projects, it would help a lot.
  • vascofigueira's avatar
    vascofigueira
    New Contributor
    13 years ago
    redfish4ktc wrote:
    You can already avoid putting external dependencies in the ext/ folder.
    As for all maven plugins, you only need to add <dependencies> in the plugin declaration in the pom.xml file.

    Oh, yes. My bad. In trying to solve the previous issue I moved them all to general dependencies and added a maven-dependency-plugin:copy-dependencies goal to the ext folder.

    Thanks.
  • eddiewebb's avatar
    eddiewebb
    13 years ago
    I am using the 4.0.2 SNAPSHOT and still getting this error on xpath match assertions.

    Had to switch to "Contains" which are not nearly as accurate. What changed>?
  • twrwrtp's avatar
    twrwrtp
    New Contributor
    13 years ago
    Following all the hints, I added junit as a dependency for the plugin and my tests work now.

    <plugin>
     <groupId>eviware</groupId>
     <artifactId>maven-soapui-plugin</artifactId>
     <version>4.0.1</version>
     <configuration>
     ...
     </configuration>
     <dependencies>
      <dependency>
       <groupId>junit</groupId>
       <artifactId>junit</artifactId>
       <version>4.4</version>
      </dependency>
     </dependencies>
    </plugin>