java.lang.NoClassDefFoundError: org/apache/commons/lang/StringUtils about jasmine-maven-plugin

[searls]

The plugin does depend on commons-lang, yes.

I've seen this before. In both cases, nuking the commons-Lang artifact
folder from the (Jenkins) m2 repository directory resolved it.

On Jul 20, 2011, at 20:06, smithclay
[email protected]
wrote:

While I can get jasmine-maven-plugin to work just fine locally, I'm getting the following exception when running tests on my Jenkins server with the included POM.

Does jasmine require the StringUtils dependency to required in order to work in certain environments? I'm thinking this could just be a stupid configuration problem on my end (but it's really strange that it fails on Jenkins and works just fine locally). Thanks for you help!

       <profile>
           <id>jasmine-tests</id>
           <dependencies>
           </dependencies>
           <build>
               <plugins>
                   <plugin>
                       <groupId>com.github.searls</groupId>
                       <artifactId>jasmine-maven-plugin</artifactId>
                       <version>1.0.2-beta-5</version>
                       <executions>
                           <execution>
                               <goals>
                                   <goal>test</goal>
                               </goals>
                           </execution>
                       </executions>
                       <configuration>
                           <jsSrcDir>${project.basedir}/src/main/webapp/scripts</jsSrcDir>
                           <sourceIncludes>
                               <include>jquery/jquery-1.5.2.min.js</include>
                               <include>jquery/jquery-ui-1.8.12.custom.min.js</include>
                               <include>future/libs.js</include>
                               <include>future/studio-libs.js</include>
                               <include>future/metrics.js</include>
                           </sourceIncludes>
                           <jsTestSrcDir>${project.basedir}/src/test/javascript/spec</jsTestSrcDir>
                       </configuration>
                   </plugin>
               </plugins>
           </build>
       </profile>

[INFO] Trace
java.lang.NoClassDefFoundError: org/apache/commons/lang/StringUtils
   at com.github.searls.jasmine.io.scripts.RelativizesASetOfScripts.normalize(RelativizesASetOfScripts.java:31)
   at com.github.searls.jasmine.io.scripts.RelativizesASetOfScripts.relativize(RelativizesASetOfScripts.java:19)
   at com.github.searls.jasmine.CreatesManualRunner.scriptsForRunner(CreatesManualRunner.java:43)
   at com.github.searls.jasmine.CreatesManualRunner.create(CreatesManualRunner.java:34)
   at com.github.searls.jasmine.GenerateManualRunnerMojo.run(GenerateManualRunnerMojo.java:15)
   at com.github.searls.jasmine.AbstractJasmineMojo.execute(AbstractJasmineMojo.java:193)
   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.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1205)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1038)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:643)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
   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)

Reply to this email directly or view it on GitHub:
#27

[smithclay]

Thanks for replying so quickly. Somewhat strangely, that didn't do the trick
but rolling back to 1.0.2-beta4 did the trick.

On Wed, Jul 20, 2011 at 5:29 PM, searls <
[email protected]>wrote:

The plugin does depend on commons-lang, yes.

I've seen this before. In both cases, nuking the commons-Lang artifact
folder from the (Jenkins) m2 repository directory resolved it.

On Jul 20, 2011, at 20:06, smithclay
[email protected]
wrote:

While I can get jasmine-maven-plugin to work just fine locally, I'm
getting the following exception when running tests on my Jenkins server with
the included POM.

Does jasmine require the StringUtils dependency to required in order to
work in certain environments? I'm thinking this could just be a stupid
configuration problem on my end (but it's really strange that it fails on
Jenkins and works just fine locally). Thanks for you help!

       <profile>
           <id>jasmine-tests</id>
           <dependencies>
           </dependencies>
           <build>
               <plugins>
                   <plugin>
                       <groupId>com.github.searls</groupId>
                       <artifactId>jasmine-maven-plugin</artifactId>
                       <version>1.0.2-beta-5</version>
                       <executions>
                           <execution>
                               <goals>
                                   <goal>test</goal>
                               </goals>
                           </execution>
                       </executions>
                       <configuration>

 <jsSrcDir>${project.basedir}/src/main/webapp/scripts</jsSrcDir>
                           <sourceIncludes>

 <include>jquery/jquery-1.5.2.min.js</include>

 <include>jquery/jquery-ui-1.8.12.custom.min.js</include>
                               <include>future/libs.js</include>
                               <include>future/studio-libs.js</include>
                               <include>future/metrics.js</include>
                           </sourceIncludes>

 <jsTestSrcDir>${project.basedir}/src/test/javascript/spec</jsTestSrcDir>
                       </configuration>
                   </plugin>
               </plugins>
           </build>
       </profile>

[INFO] Trace
java.lang.NoClassDefFoundError: org/apache/commons/lang/StringUtils
   at
com.github.searls.jasmine.io.scripts.RelativizesASetOfScripts.normalize(RelativizesASetOfScripts.java:31)
   at
com.github.searls.jasmine.io.scripts.RelativizesASetOfScripts.relativize(RelativizesASetOfScripts.java:19)
   at
com.github.searls.jasmine.CreatesManualRunner.scriptsForRunner(CreatesManualRunner.java:43)
   at
com.github.searls.jasmine.CreatesManualRunner.create(CreatesManualRunner.java:34)
   at
com.github.searls.jasmine.GenerateManualRunnerMojo.run(GenerateManualRunnerMojo.java:15)
   at
com.github.searls.jasmine.AbstractJasmineMojo.execute(AbstractJasmineMojo.java:193)
   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.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1205)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1038)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:643)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
   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)

Reply to this email directly or view it on GitHub:
#27

Reply to this email directly or view it on GitHub:

#27 (comment)

[klieber]

Closing this issue because it is so old and was filed for a beta version of the plugin. If anyone is still seeing this issue with 1.2.0.0 or later let me know and I will reopen the issue.