Forum Discussion

azurion's avatar
azurion
New Contributor
12 years ago

Maven plugin not using project set in <projectFile>

Project file is set as follows:

  <configuration>    
<projectFile>${project.basedir}/test/soapui/scripts/IntegrationTest.xml</projectFile>
...
</configuration>


Yet the plugin always tries to use pom's <artifactId> for project file.

   <artifactId>IntegrationTest</artifactId>


So when I attempt to build:

mvn -X com.smartbear.soapui:soapui-maven-plugin:4.6.1:test

This gets thrown up:

[ERROR] Failed to execute goal com.smartbear.soapui:soapui-maven-plugin:4.6.1:test (default-cli) on project IntegrationTest: SoapUI Test(s) failed: SoapUI Test(s) failed:
[ERROR] Failed to load SoapUI project file [IntegrationTest-soapui-project.xml]

I've tried putting full path of the project (/Users/../../../../IntegrationTest.xml) but always get the same result. It's like the plugin completely ignores what I set in configuration.

1 Reply

  • redfish4ktc2's avatar
    redfish4ktc2
    Super Contributor
    hi,
    I am not aware of such an issue
    did you reproduce the issue with other version of the plugin?
    What you see is like if the projectFile parameter was not set then the default value (based on the pom artifactId) is used

    Check also this topic: viewtopic.php?f=1&t=23239