[JIRA] (JENKINS-15977) java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild

2012-12-10 Thread murr...@murrayc.com (JIRA)














































Murray Cumming
 commented on  JENKINS-15977


java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild















Yes, upgrading Jenkins seems to have fixed this. After upgrading to the jenkins.org .deb packages (1.493), there is no "Maven 2 Project plugin" available or installed, but the "Maven Integration plugin" seems to be installed by default.

And my "Copy artifacts from another project" build step now works.

Thanks.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-15977) java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild

2012-12-07 Thread murr...@murrayc.com (JIRA)














































Murray Cumming
 commented on  JENKINS-15977


java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild















 Do you have the Maven plugin installed/enabled?

No.

I see several maven plugins on our pluginManager/available page. Which one do you you mean?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-15977) java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild

2012-12-07 Thread murr...@murrayc.com (JIRA)














































Murray Cumming
 commented on  JENKINS-15977


java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild















Thanks. No, that's not installed.

I'll have to upgrade Jenkins to install that, because the pluginManager/available page says "Warning: This plugin is built for Jenkins 1.480.1 or newer. It may or may not work in your Jenkins."

I'm using the standard Ubuntu 12.10 (Quantal) package. I'll try the http://pkg.jenkins-ci.org/debian/ packages



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-15977) java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild

2012-11-29 Thread murr...@murrayc.com (JIRA)














































Murray Cumming
 created  JENKINS-15977


java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild















Issue Type:


Bug



Assignee:


Unassigned


Components:


copyartifact



Created:


29/Nov/12 11:06 AM



Description:


I'm using jenkins 1.466.2 via the regular Ubuntu packages on Ubuntu Quantla (12.10) with the copyArtifact plugin (version 1.25)

The console output for the build of one of my Jenkins projects consistently shows this:

Started by user Murray Cumming
Building in workspace /var/lib/jenkins/workspace/maliit-plugins
Checkout:maliit-plugins / /var/lib/jenkins/workspace/maliit-plugins - hudson.remoting.LocalChannel@35e47b48
Using strategy: Default
Last Built Revision: Revision 1004cc39badd17308a1fabfe0b72d1e762572b4b (origin/master)
Fetching changes from 1 remote Git repository
Fetching upstream changes from git://gitorious.org/maliit/maliit-plugins.git
Commencing build of Revision 1004cc39badd17308a1fabfe0b72d1e762572b4b (origin/master)
Checking out Revision 1004cc39badd17308a1fabfe0b72d1e762572b4b (origin/master)
FATAL: hudson/maven/MavenModuleSetBuild
java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild
	at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:198)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710)
	at hudson.model.Build$RunnerImpl.build(Build.java:178)
	at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480)
	at hudson.model.Run.run(Run.java:1438)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:239)
Caused by: java.lang.ClassNotFoundException: hudson.maven.MavenModuleSetBuild
	at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
	... 10 more




Project:


Jenkins



Priority:


Major



Reporter:


Murray Cumming

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-15896) Spaces in the path when the configuration axis values have spaces

2012-11-26 Thread murr...@murrayc.com (JIRA)














































Murray Cumming
 commented on  JENKINS-15896


Spaces in the path when the configuration axis values have spaces















The help hint (via the ? button) says:
"Values assigned to variables. Multiple values are separated by whitespace or newlines. Use shell quoting syntax for a value that contains whitespace."
so I tried using \ to escape the space, like so:
"--disable-calendar\ --disable-weather"
""

But after saving and reloading the configure page, the \ is gone. And the same path is used for the git checkout.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-15896) Spaces in the path when the configuration axis values have spaces

2012-11-22 Thread murr...@murrayc.com (JIRA)














































Murray Cumming
 created  JENKINS-15896


Spaces in the path when the configuration axis values have spaces















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git



Created:


22/Nov/12 9:21 AM



Description:


When using a multi-configuration job, with a Configuration Matrix, if the axis values have spaces then those spaces appear in the directory used for the source code checkout. Although most builds should be able to cope with it, it's fairly unusual and an obstacle when the build cannot handle it yet.

For instance, I have this axis name:
configureoptions
and these axis values:
"--disable-calendar --disable-weather"
""

(Which I pass to our ./autogen.sh in the "Execute Shell" build step.)


Then the spaces in the path cause our build to fail:


make4: Leaving directory `/var/lib/jenkins/workspace/evolution-data-server/configureoptions/--disable-calendar --disable-weather/camel'
Making all in providers
make4: Entering directory `/var/lib/jenkins/workspace/evolution-data-server/configureoptions/--disable-calendar --disable-weather/camel/providers'
Making all in pop3
make5: Entering directory `/var/lib/jenkins/workspace/evolution-data-server/configureoptions/--disable-calendar --disable-weather/camel/providers/pop3'
  CC libcamelpop3_la-camel-pop3-engine.lo
  CC libcamelpop3_la-camel-pop3-folder.lo
  CC libcamelpop3_la-camel-pop3-provider.lo
  CC libcamelpop3_la-camel-pop3-settings.lo
  CC libcamelpop3_la-camel-pop3-stream.lo
  CC libcamelpop3_la-camel-pop3-store.lo
  CCLD   libcamelpop3.la
/bin/sed: unrecognized option '--disable-weather/camel/libcamel-1.2.la'
Usage: /bin/sed OPTION... {script-only-if-no-other-script} input-file...




Environment:


Ubuntu Linux 12.10 (Quantal)

Official Ubuntu Jenkins packages (Jenkins ver. 1.466.2)




Project:


Jenkins



Priority:


Major



Reporter:


Murray Cumming

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira