Improper POM in eviware:soapui:4.5.1
This bug has been reported several times before, it has been claimed to be fixed however I was unable to find any evidence of this.
The problem has to do with the POM that is published with the eviware:soapui:4.5.1 package. Here is that POM:
<?xml version="1.0" encoding="UTF-8"?>
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>eviware</groupId>
<artifactId>soapui</artifactId>
<version>4.5.1</version>
</project>
The POM itself declares no dependencies which would imply that the soapui.jar artifact could be invoked with no additional classpath. This is not the case.
This same issue has been reported in: viewtopic.php?f=13&t=11003&hilit=pom
Note that the final entry on this post makes note of the fact that the issue has NOT been fixed.
I have demonstrated the problem in the attached SoapUIBug.tar file. This is a Maven project with a simple test case that demonstrates the problem.
The problem has to do with the POM that is published with the eviware:soapui:4.5.1 package. Here is that POM:
<?xml version="1.0" encoding="UTF-8"?>
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>eviware</groupId>
<artifactId>soapui</artifactId>
<version>4.5.1</version>
</project>
The POM itself declares no dependencies which would imply that the soapui.jar artifact could be invoked with no additional classpath. This is not the case.
This same issue has been reported in: viewtopic.php?f=13&t=11003&hilit=pom
Note that the final entry on this post makes note of the fact that the issue has NOT been fixed.
I have demonstrated the problem in the attached SoapUIBug.tar file. This is a Maven project with a simple test case that demonstrates the problem.
