l2fprod.com maven repository down?
Trying to run soapUI tests with Maven using maven-soapui-plugin (Tried with versions 2.5.1, 3.5.1, 3.6.1). The build fails in [INFO] Trace java.lang.NoClassDefFoundError: org/apache/log4j/Layout...
Forum Discussion
I've just started using soap-ui in preperation of web service testing and I'm having similar problems to the one in this post, in my own test environment i get the following warnings:
[WARNING] POM for 'xom:xom:pom:1.1:runtime' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for 'org.codehaus.groovy:groovy-all:pom:1.7.5: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.
and some more.
In the end it looks like the plugin is running ok, but still the WARNINGS, can these be resolved in some way?.
BUT,
When i replicate the soap-ui setup to another environment, it's a story akin to the one posted here, the infamous NOCLASSDEFERRO on log4j. As we use Nexus to cache downloaded maven artefacts it It would be quite troublesome to selectively delete the offending jars and poms.
Does anybody know what the primary reason is for this error? I don't mind putting some time in a clean-up but I don't want the situation re-occuring. Any suggestions on how to configure soap-ui for maven without the ?corrupted? plugin problems?
[WARNING] POM for 'xom:xom:pom:1.1:runtime' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for 'org.codehaus.groovy:groovy-all:pom:1.7.5: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.
and some more.
In the end it looks like the plugin is running ok, but still the WARNINGS, can these be resolved in some way?.
BUT,
When i replicate the soap-ui setup to another environment, it's a story akin to the one posted here, the infamous NOCLASSDEFERRO on log4j. As we use Nexus to cache downloaded maven artefacts it It would be quite troublesome to selectively delete the offending jars and poms.
Does anybody know what the primary reason is for this error? I don't mind putting some time in a clean-up but I don't want the situation re-occuring. Any suggestions on how to configure soap-ui for maven without the ?corrupted? plugin problems?