Forum Discussion

lahter's avatar
lahter
New Contributor
15 years ago

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
 at com.eviware.soapui.maven2.TestMojo.execute(TestMojo.java:51)
 at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
 at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Layout


Before the error Maven is trying to download dependencies. And it seems that the repo in http://www.l2fprod.com is corrupted/missing. Since all dependencies downloaded from there are corrupted. 


Downloading: http://www.eviware.com/repository/maven2//log4j/log4j/1.2.14/log4j-1.2.14.pom
[INFO] Unable to find resource 'log4j:log4j:pom:1.2.14' in repository eviwarePluginRepository (http://www.eviware.com/repository/maven2/)
Downloading: http://www.eviware.com/repository/maven2/log4j/log4j/1.2.14/log4j-1.2.14.pom
[INFO] Unable to find resource 'log4j:log4j:pom:1.2.14' in repository eviwareRepository (http://www.eviware.com/repository/maven2)
Downloading: http://www.l2fprod.com/maven2/log4j/log4j/1.2.14/log4j-1.2.14.pom
1K downloaded  (log4j-1.2.14.pom)
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'a6aeb634c9793673feea9ffb235173a1a5267fe7'; remote = '<!DOCTYPE' - RETRYING
Downloading: http://www.l2fprod.com/maven2/log4j/log4j/1.2.14/log4j-1.2.14.pom
1K downloaded  (log4j-1.2.14.pom)
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'a6aeb634c9793673feea9ffb235173a1a5267fe7'; remote = '<!DOCTYPE' - IGNORING
[WARNING] POM for 'log4j:log4j:pom:1.2.14:runtime' is invalid.



The http://www.l2fprod.com is referenced in the pom of maven-soapui-plugin.

Same build last week was fine.

Any one having same problem ?

3 Replies

  • lahter's avatar
    lahter
    New Contributor
    15 years ago
    Just found a solution aroud it.

    I mirror the l2fprod maven repository (in .m2/settings.xml file) with maven central repository. It seems to contain all dependencies needed by the maven soapUI plugin. 


      <mirrors>
       <mirror>
       <id>L2fprodMaven2Repository.2</id>
       <name> Mirror of http://www.l2fprod.com/maven2 which has been lost</name>
       <url>http://repo1.maven.org/maven2/</url>
       <mirrorOf>L2fprodMaven2Repository</mirrorOf>
      </mirror>
      </mirrors>
  • walterRidderhof's avatar
    walterRidderhof
    15 years ago
    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?