Details
-
Type:
Bug
-
Status: Reopened (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: maven-plugin
-
Labels:None
-
Similar Issues:
Description
We have upgraded from Jenkins 1.399 to Jenkins 1.441. Our Maven jobs are now run by Maven 3.0.3 instead of Maven 2.2.1.
When a job is a Maven multi-module project, it is possible to run a single submodule (on the job page, click on "Modules", then start the build for a given submodule). It was working fine with our old instance but now the build fails with status "ABORTED".
See thread: http://jenkins.361315.n4.nabble.com/Build-Maven-submodule-gt-ABORTED-td4128116.html
Is it possible to reintroduce this feature?
Thanks
There was a bug (
JENKINS-10831) back in 1.427 that caused a failure but that had does not look like your issue. I just double checked on my system on 1.441 and that does build a single submodule correctly.However I just noticed that I was using maven 2.2.1 for builds (oops thought I had changed to 3.0.3!) and if I switch to 3.0.3 I get the same aborted error as you.
The jenkins logfile has the following error in it.