Maven "doesn't have a 'lib' subdirectory"

971 views
Skip to first unread message

maloy...@gmail.com

unread,
Jan 14, 2015, 1:26:01 PM1/14/15
to jenkins...@googlegroups.com
Hi, I got this error message using Jenkins v1.596 and it told me to send it here:

===
ERROR: Processing failed due to a bug in the code. Please report this to jenkins...@googlegroups.com
java.lang.IllegalArgumentException: /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven32 doesn't have a 'lib' subdirectory - thus cannot be a valid maven installation!
    at hudson.maven.MavenEmbedderUtils.buildClassRealm(MavenEmbedderUtils.java:83)
    at hudson.maven.MavenEmbedderUtils.getMavenVersion(MavenEmbedderUtils.java:188)
    at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:70)
    at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:42)
    at hudson.FilePath.act(FilePath.java:1068)
    at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:627)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
    at hudson.model.Run.execute(Run.java:1759)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
    at hudson.model.ResourceController.execute(ResourceController.java:89)
    at hudson.model.Executor.run(Executor.java:240)
project=hudson.maven.MavenModuleSet@1254679[09002-trunk-test]
project.getModules()=[]
project.getRootModule()=null
FATAL: /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven32 doesn't have a 'lib' subdirectory - thus cannot be a valid maven installation!
java.lang.IllegalArgumentException: /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven32 doesn't have a 'lib' subdirectory - thus cannot be a valid maven installation!
    at hudson.maven.MavenEmbedderUtils.buildClassRealm(MavenEmbedderUtils.java:83)
    at hudson.maven.MavenEmbedderUtils.getMavenVersion(MavenEmbedderUtils.java:188)
    at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:70)
    at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:42)
    at hudson.FilePath.act(FilePath.java:1068)
    at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:627)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
    at hudson.model.Run.execute(Run.java:1759)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
    at hudson.model.ResourceController.execute(ResourceController.java:89)
    at hudson.model.Executor.run(Executor.java:240)
===

Directory tree looked like this:
[root@v20z-002 tools]# tree -di
.
hudson.tasks.Maven_MavenInstallation
Maven32
apache-maven-3.2.5
bin
boot
conf
logging
lib
ext

9 directories

My workaround looked like this:
[root@v20z-002 Maven32]# mv apache-maven-3.2.5/* .

I hope it's helpful.
Reply all
Reply to author
Forward
0 new messages