Forum Discussion

torstenreinhard's avatar
torstenreinhard
Occasional Contributor
17 years ago

soapUI maven plugin and dependencies issue

Hi,

I use the soapUI (pro) maven plugin to test my soapUI project, using internal groovy scripts and classes.
The groovy scripts need external 3rd party dependencies, which could be deployed to the the \ext folder when running from the gui.
When running from the maven plugin, I need to define these 3rd party dependencies in my pom.xml - but for me, it seems that the plugin is only looking at the "plugin classpath" from maven - not the "project classpath" or "compile classpath".
Is there any other way than defining the dependencies as "plugin dependencies" within my pom.xml?

The exec-maven-plugin from codehaus for example hat 2 properties, called "includePluginDependencies" or "includeProjectDependencies".

Thanx

Torsten

2 Replies

  • xavier_sautejea's avatar
    xavier_sautejea
    New Contributor
    16 years ago
    I know this topic is somewhat old, but I have the same issue, so if someone has the answer for this, please reply.

    Thanks,

    Xavier
  • xavier_sautejea's avatar
    xavier_sautejea
    New Contributor
    16 years ago
    I found a workaround :

    When running the soapui maven plugin, the working directory is ${basedir} (i.e. the directory of the maven project/module).

    Create a "ext" directory under your maven ${basedir} directory and add the jar files you need there.