We encounter the same problem. We use maven as the only build step and at the end of an failing build, nothing is stated about the error:

27.08.2013 04:31:27 org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: 
27.08.2013 04:31:27 org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: --- maven-clean-plugin:2.4.1:clean (default-clean) @ JLand-Variant10000-Deployment ---
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: 
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: --- maven-resources-plugin:2.4.3:resources (default-resources) @ JLand-Variant10000-Deployment ---
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger logResult
INFO: ------------------------------------------------------------------------
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger logResult
INFO: BUILD FAILURE
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: ------------------------------------------------------------------------
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Total time: 2.797s
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Finished at: Tue Aug 27 04:31:28 CEST 2013
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Final Memory: 6M/123M
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger sessionEnded
INFO: ------------------------------------------------------------------------
[JENKINS] Archiving [...]
Warte bis Jenkins die Datensammlung abgeschlossen hat
channel stopped
Finished: FAILURE

The behavior appears on compile errors as well as on other goals, i.e. cargo:deploy.

Environment:

• Microsoft Windows Server 2003 R2 SP2
• Maven 3.0.3

If you use a freestyle project the logging is as expected.

I looked at the difference in the way Maven is started between the Maven project and a freestyle project, and it looks like for a Maven project Maven is started in a forked java process, like below:

/u01/appl/jenkins/tools/hudson.model.JDK/Sun_JDK_1.6u45/bin/java -Dorg.slf4j.simpleLogger.showThreadName=false -Dorg.slf4j.simpleLogger.showDateTime=false -Dorg.slf4j.simpleLogger.levelInBrackets=true -Dorg.slf4j.simpleLogger.showLogName=false -Djava.awt.headless=true -cp /u01/appl/jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.4.jar:/u01/appl/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.0/boot/plexus-classworlds-2.4.2.jar:/u01/appl/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.0/conf/logging jenkins.maven3.agent.Maven31Main /u01/appl/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.0 /var/cache/jenkins/war/WEB-INF/lib/remoting-2.32.jar /u01/appl/jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.4.jar /u01/appl/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar 40757
11:10:18 <===[JENKINS REMOTING CAPACITY]===>channel started
11:10:19 log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter).
11:10:19 log4j:WARN Please initialize the log4j system properly.
11:10:20 Executing Maven: -B -f /u01/appl/jenkins/jobs/upc-generic/workspace/pom.xml -e clean install

The maven error is probably written to stderr, and probably this is not redirected to jenkins.

What changed in 1.526 to cause this and can it be reverted? Kind of makes Maven builds useless if you can't see why they failed. I tried the freestyle project and would consider switching, but the Sonar plugin fails to launch because the mvn command is not in the default path and it doesn't seem to honor the path used for the main build. I don't want to jump through hoops for 70 Maven jobs...sigh.

Hi. Having exactly the same problem on Windows 7 and Jenkins 1.530. Maven (3.0.4) build fails with no output in Jenkins (even if using -X). (Standalone Maven build works fine from command line)

Started seeing this after upgrade to 1.531 (from 1.521?) in a CentOS6 Linux environment.

Before, I have the full traceback

message : Failed to execute goal on project example-project: Could not resolve dependencies for project ... etc ...

After, I only have this one line cluing me in to which module failed:

INFO: example-project ...................... FAILURE [3.910s]

FWIW, I've managed to get back to a working setup with Jenkins 1.531 and Maven Project Plugin at 1.522 (haven't tried other plugin versions, this just happened to be what was available to me).

Possibly related to JENKINS-15935. At least there were a lot of changes to the maven plugin in 1.526 due to that issue

I'm also seeing this issue with version 1.532 on RHEL 6 in a master-slave configuration.

Reproducible on Ubuntu 12.04 x64 Jenkins version 1.5.32 and Maven plugin version 1.533

This is really a critical bug. Please fix.

Reproducible on RHEL6 using Jenkins 1.533 with Maven Integration Plugin 1.533. Without being about to see what caused the build failure, one is forced to build the project in a non-Jenkins environment adding to the delay in fixing the build.

I have the same issue on W2012 server using Jenkins v 1.533. Will make revert back to a previous < 1.52x version until they fix it

Not related to JENKINS-15935, because JENKINS-15935 is in the LTS branch, but I cannot see this bug in it.

Code changed in jenkins
User: Christoph Kutzinski
Path:
src/main/java/hudson/maven/Maven3Builder.java
http://jenkins-ci.org/commit/maven-plugin/53987d1c00d14dee7ab726b2eb7500f4f8b27599
Log:
JENKINS-19352: partial revert of JENKINS-15025, so that Maven exceptions are
visible in the console log, again

Compare: https://github.com/jenkinsci/maven-plugin/compare/c87013d3f82b...53987d1c00d1

Reverted the changes for JENKINS-15025 partially, so that exception messages are visible again.

I'm leaving this issue open, so someone (preferrably Nikolas) can look for a proper fix which fixes JENKINS-15025 and doesn't introduce this issue again.

@kutzi if your commit fixes this reported bug, then this issue should be closed; leaving JENKINS-15025 reopened suffices.

I post a pull request to https://github.com/jenkinsci/maven-plugin/pull/2

Would be great if someone could try the fixed maven-plugin before I cut a release from it:
https://www.dropbox.com/sh/kjkh5g3r68kmlj7/JvgKJnf7gp

I installed the maven-plugin from the dropbox by copying the .hpi file to the $JENKINS_HOME/plugin folder, removing the existing maven-plugin folder and the maven-plugin.jpi file, then restarting Jenkins.

I forced a build by creating an error in one of our projects and allowed SVN polling to start the build.

I expected to see something along these lines:

[INFO]
[INFO] — exec-maven-plugin:1.1:exec (concat-license-files) @ jagwire-license —
[INFO]
[INFO] — exec-maven-plugin:1.1:exec (resolve-jagwire-aliases) @ jagwire-license —
[INFO]
[INFO] — exec-maven-plugin:1.1:exec (sort-license-files) @ jagwire-license —
[INFO]
[INFO] — exec-maven-plugin:1.1:exec (organize-jagwire-dependencies) @ jagwire-license —
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3:53.079s
[INFO] Finished at: Mon Oct 14 11:54:58 EDT 2013
[INFO] Final Memory: 23M/1000M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.1:exec (organize-jagwire-dependencies) on project jagwire-license: Result of /bin/sh -c cd /Users/davis/EclipseWorkspace/jagwire-license && /Users/davis/EclipseWorkspace/jagwire-license/src/license/scripts/licenses.pl -v 3.0-SNAPSHOT -f /Users/davis/EclipseWorkspace/jagwire-license/target/temp/sorted-license-file.txt -l /Users/davis/EclipseWorkspace/jagwire-license/src/license/license-files -c /Users/davis/EclipseWorkspace/jagwire-license/target/third-party-projects.csv execution is: '30'. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

but the output from Jenkins was:

Oct 14, 2013 11:59:53 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:
Oct 14, 2013 11:59:53 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — exec-maven-plugin:1.1:exec (concat-license-files) @ jagwire-license —
Oct 14, 2013 11:59:53 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:
Oct 14, 2013 11:59:53 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — exec-maven-plugin:1.1:exec (resolve-jagwire-aliases) @ jagwire-license —
Oct 14, 2013 11:59:53 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:
Oct 14, 2013 11:59:53 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — exec-maven-plugin:1.1:exec (sort-license-files) @ jagwire-license —
Oct 14, 2013 11:59:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:
Oct 14, 2013 11:59:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — exec-maven-plugin:1.1:exec (organize-jagwire-dependencies) @ jagwire-license —
Notifying upstream projects of job completion
Join notifier requires a CauseAction
Oct 14, 2013 11:59:54 AM org.apache.maven.cli.event.ExecutionEventLogger logResult
INFO: ------------------------------------------------------------------------
Oct 14, 2013 11:59:54 AM org.apache.maven.cli.event.ExecutionEventLogger logResult
INFO: BUILD FAILURE
Oct 14, 2013 11:59:54 AM org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: ------------------------------------------------------------------------
Oct 14, 2013 11:59:54 AM org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Total time: 2:18.228s
Oct 14, 2013 11:59:54 AM org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Finished at: Mon Oct 14 11:59:54 EDT 2013
Oct 14, 2013 11:59:54 AM org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Final Memory: 27M/981M
Oct 14, 2013 11:59:54 AM org.apache.maven.cli.event.ExecutionEventLogger sessionEnded
INFO: ------------------------------------------------------------------------
Waiting for Jenkins to finish collecting data
[JENKINS] Archiving /var/lib/jenkins/workspace/JagwireLicense/pom.xml to com.exelis.jagwire/jagwire-license/3.0-SNAPSHOT/jagwire-license-3.0-SNAPSHOT.pom
An attempt to send an e-mail to empty list of recipients, ignored.
channel stopped
An attempt to send an e-mail to empty list of recipients, ignored.
Email was triggered for: Failure
Sending email for trigger: Failure
Sending email to: john.s.davis@exelisinc.com
Notifying upstream projects of job completion
Finished: FAILURE

This was done under RHEL 6 using Jenkins 1.534 where the maven-plugin was unpinned. The version of the maven-plugin under "Manage Plugins" is 1.534. Should it have shown a different version or did I install the plugin from the drop box incorrectly?

JOn, please use the 'advanced' tab in the Jenkins Plugin Manager GUI to make sure the plugin is correctly 'pinned' - so not recreated from the bundled one on startup.
The version should be something like 2.0-beta-2

I work so danged much at the command line, I often forget there are web and other interfaces. Sigh.

I uploaded the plugin using the advanced tab and after restarting jenkins noted the plugin version is now "2.0-beta-2-SNAPSHOT (private-10/12/2013 21:45-kutz1". Looking better.

After forcing the same error in the project, the Jenkins output ismore like I would expect to see:

INFO:
INFO: — exec-maven-plugin:1.1:exec (concat-license-files) @ jagwire-license —
INFO:
INFO: — exec-maven-plugin:1.1:exec (resolve-jagwire-aliases) @ jagwire-license —
INFO:
INFO: — exec-maven-plugin:1.1:exec (sort-license-files) @ jagwire-license —
INFO:
INFO: — exec-maven-plugin:1.1:exec (organize-jagwire-dependencies) @ jagwire-license —
Notifying upstream projects of job completion
Join notifier requires a CauseAction
INFO: ------------------------------------------------------------------------
INFO: BUILD FAILURE
INFO: ------------------------------------------------------------------------
INFO: Total time: 1:40.724s
INFO: Finished at: Mon Oct 14 12:37:58 EDT 2013
INFO: Final Memory: 23M/981M
INFO: ------------------------------------------------------------------------
Waiting for Jenkins to finish collecting data
SEVERE: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.1:exec (organize-jagwire-dependencies) on project jagwire-license: Result of /bin/sh -c cd /var/lib/jenkins/workspace/JagwireLicense && /var/lib/jenkins/workspace/JagwireLicense/src/license/scripts/licenses.pl -v 3.0-SNAPSHOT -f /var/lib/jenkins/workspace/JagwireLicense/target/temp/sorted-license-file.txt -l /var/lib/jenkins/workspace/JagwireLicense/src/license/license-files -c /var/lib/jenkins/workspace/JagwireLicense/target/third-party-projects.csv execution is: '30'. -> [Help 1]
SEVERE:
SEVERE: To see the full stack trace of the errors, re-run Maven with the -e switch.
SEVERE: Re-run Maven using the -X switch to enable full debug logging.
SEVERE:
SEVERE: For more information about the errors and possible solutions, please read the following articles:
SEVERE: [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[JENKINS] Archiving /var/lib/jenkins/workspace/JagwireLicense/pom.xml to com.exelis.jagwire/jagwire-license/3.0-SNAPSHOT/jagwire-license-3.0-SNAPSHOT.pom

which points out why the project's build failed.

I'm going to leave this version of the plugin in place and continue to monitor our jobs.

Thanks to all who worked on this change.

Also the output when the project builds successfully is what I'd expect to see:

Previously, the section where the build failed looked like:

INFO:
Oct 14, 2013 12:17:09 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — exec-maven-plugin:1.1:exec (concat-license-files) @ jagwire-license —
Oct 14, 2013 12:17:09 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:
Oct 14, 2013 12:17:09 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — exec-maven-plugin:1.1:exec (resolve-jagwire-aliases) @ jagwire-license —
Oct 14, 2013 12:17:09 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:
Oct 14, 2013 12:17:09 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — exec-maven-plugin:1.1:exec (sort-license-files) @ jagwire-license —
Oct 14, 2013 12:17:09 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:
Oct 14, 2013 12:17:09 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — exec-maven-plugin:1.1:exec (organize-jagwire-dependencies) @ jagwire-license —
Oct 14, 2013 12:17:09 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:
Oct 14, 2013 12:17:09 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — exec-maven-plugin:1.1:exec (create-license) @ jagwire-license —
Oct 14, 2013 12:17:09 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:
Oct 14, 2013 12:17:09 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — maven-resources-plugin:2.5:resources (default-resources) @ jagwire-license —
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /var/lib/jenkins/workspace/JagwireLicense/src/main/resources
Oct 14, 2013 12:17:09 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:
Oct 14, 2013 12:17:09 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — maven-compiler-plugin:2.3.2:compile (default-compile) @ jagwire-license —
[INFO] No sources to compile
Oct 14, 2013 12:17:10 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:
Oct 14, 2013 12:17:10 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — maven-resources-plugin:2.5:testResources (default-testResources) @ jagwire-license —
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /var/lib/jenkins/workspace/JagwireLicense/src/test/resources
Oct 14, 2013 12:17:10 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:
Oct 14, 2013 12:17:10 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jagwire-license —
[INFO] No sources to compile
Oct 14, 2013 12:17:10 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:
Oct 14, 2013 12:17:10 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: — maven-surefire-plugin:2.10:test (default-test) @ jagwire-license —
[INFO] No tests to run.
[INFO] Surefire report directory: /var/lib/jenkins/workspace/JagwireLicense/target/surefire-reports

-------------------------------------------------------
T E S T S
-------------------------------------------------------

where is was difficult to pick out the build steps that were executing ( in this case exec-maven-plugin executions).

With the revised plugin, this section looks like:

INFO:
INFO: — exec-maven-plugin:1.1:exec (concat-license-files) @ jagwire-license —
INFO:
INFO: — exec-maven-plugin:1.1:exec (resolve-jagwire-aliases) @ jagwire-license —
INFO:
INFO: — exec-maven-plugin:1.1:exec (sort-license-files) @ jagwire-license —
INFO:
INFO: — exec-maven-plugin:1.1:exec (organize-jagwire-dependencies) @ jagwire-license —
INFO:
INFO: — exec-maven-plugin:1.1:exec (create-license) @ jagwire-license —
INFO:
INFO: — maven-resources-plugin:2.5:resources (default-resources) @ jagwire-license —
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /var/lib/jenkins/workspace/JagwireLicense/src/main/resources
INFO:
INFO: — maven-compiler-plugin:2.3.2:compile (default-compile) @ jagwire-license —
[INFO] No sources to compile
INFO:
INFO: — maven-resources-plugin:2.5:testResources (default-testResources) @ jagwire-license —
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /var/lib/jenkins/workspace/JagwireLicense/src/test/resources
INFO:
INFO: — maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jagwire-license —
[INFO] No sources to compile
INFO:
INFO: — maven-surefire-plugin:2.10:test (default-test) @ jagwire-license —
[INFO] No tests to run.
[INFO] Surefire report directory: /var/lib/jenkins/workspace/JagwireLicense/target/surefire-reports

-------------------------------------------------------
T E S T S
-------------------------------------------------------

Where I can easily see the exec-maven-plugin steps.

Thanks again for all the work.

I cannot get to dropbox through my company's proxy. How can I get this update to test?

Tried it as well. Works great! Thank you very much

I have to revert my verdict a little bit. While the logging now works fine and Maven reports a successful build, every build on my Jenkins is failed with the following Exception at the very end of the log:
FATAL: hudson.maven.MavenBuild.pickArtifactManager()Ljenkins/model/ArtifactManager;
java.lang.NoSuchMethodError: hudson.maven.MavenBuild.pickArtifactManager()Ljenkins/model/ArtifactManager;
at hudson.maven.MavenBuild$ProxyImpl.performArchiving(MavenBuild.java:455)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:838)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:567)
at hudson.model.Run.execute(Run.java:1604)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:508)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)

I had the very same error as Sabine has in her tests.
But I did not write about it, because I tested the patch on a 1.526 versioned Jenkins and thought that was the reason.

Since now I could not test it on a current version, so I did not write about it here.

Did you use the most recent version of Jenkins?

The fixed plugin needs Jenkins 1.533+
It might run on earlier version, but obviously 1.526 is too early

Oh, sorry for that. I was using 1.531.

Seems like the 2.0 plugin (which only required 1.532+) has been released—thanks kutzi!

If it has been released, I don't see it listed in any of the changelogs. Has it been bundled w/ any recent Jenkins release?

> If it has been released, I don't see it listed in any of the changelogs.

As of 2.0 the maven-plugin is no longer released alongside Jenkins core. I'll create a changelog on the Wiki page of the plugin at a later point in time.

> Has it been bundled w/ any recent Jenkins release?
No. Will eventually be, but there's no timeline

FYI, I already committed a change to Jenkins trunk to bundle 2.0.

This fix adds a bug to email notification for jobs. When doing a new build for your job and the build fails and you have configured it to send a email notification, the email will be sent to the address(es) you specified and also to null, e.i "Sending e-mails to: andreas.nacken@gmail.com null". Resulting in a mailer-daemon-mail on every build. It is kind of annoying.

I downgraded to 2.0-beta1 and that version don't have this bug.

Andreas, how do you know that it was added by this fix?
For me it sounds much mire likely that it was added by https://issues.jenkins-ci.org/browse/JENKINS-1201 resp. https://github.com/jenkinsci/maven-plugin/commit/2f924d838f4ad49334531950cb3e7187ed147b69

Anyway, since we don't know for sure: can you please create a new JIRA issue for this?

The bug appeared when I installed your fix from dropbox that you linked earlier in this thread. So I'm quite sure it has to do with what ever you changed in that fix. But is JENKINS-1201 included in Maven-plugin 2.0-beta1?

But of course I can create a new JIRA issue for this, it is always nice to have the bugs down on paper.

I created a JIRA issue now, JENKINS-20209. Didn't now who to assign it to though.

Same Here. Discusting.

@cforce:
What are you referring to?

I've just built and installed 2.1-SNAPSHOT (last commit id: 3380985e5584d40f6988f3d7cf6fcc587f4246bb) and the errors are now correctly reported and mail are sent to all recipients with no problem.
Thanks for the fix.

Hi everyone,

we are currently running Jenkins ver. 1.535 and experiencing this issue as well. Now that LTS 1.532.1 has been released on 25th of Nov, I am wondering if this fix has been integrated. The issue JENKINS-19352 is not mentioned in the changelog (http://jenkins-ci.org/changelog-stable).

Maybe I am missing the information for some reason so I'd be grateful if someone could point out if LTS 1.532.1 includes this fix. Or, if not, if there will be a LTS release in the foreseeable future.

Thanks for all the efforts

Sorry if the answer is buried in all the comments and metadata (I've read through everything twice), but I can't determine if this fix is in any release of Jenkins other than the LTS 1.532.1 and later. Can anyone confirm precisely which releases I can get that include this fix?

You will need the Maven Project Plugin in at least version 2.0 (latest version is 2.8). This plugin needs Jenkins 1.532+ (1.538+ for latest version).

This problem has recently re-appeared. This is what I get locally

...
[INFO] ------------------------------------------------------------------------ 
[INFO] BUILD FAILURE 
[INFO] ------------------------------------------------------------------------ 
[INFO] Total time:  02:11 min 
[INFO] Finished at: 2022-07-04T16:05:44+02:00 
[INFO] ------------------------------------------------------------------------ 
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1-knime:sonar (default-cli) on project knime-hub-execution-shared: "2.4.0-alpha-todo-HUB-2847-remove-manual-health-checks-that-are-automatically-handled-by-quarkus-000001-3ee42ca" is not
a valid project version. The maximum length is 100 characters. -> [Help 1]
                 
[ERROR]  
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. 
[ERROR] Re-run Maven using the -X switch to enable full debug logging. 
[ERROR]  
[ERROR] For more information about the errors and possible solutions, please read the following articles: 
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

But the Jenkins console log only shows

...
15:23:47.259  [INFO] --- sonar-maven-plugin:3.9.1-knime:sonar (default-cli) @ knime-hub-execution-shared ---
15:23:47.359  [INFO] User cache: /home/****/.sonar/cache
15:23:48.974  [Pipeline] }
15:23:49.191  [withMaven] artifactsPublisher - Archive artifact .flattened-pom.xml under com/knime/enterprise/cloud/services/execution/knime-hub-execution-shared/2.4.0-alpha-todo-HUB-2847-remove-manual-health-checks-that-are-automatically-handled-by-quarkus-000001-3ee42ca/knime-hub-execution-shared-2.4.0-alpha-todo-HUB-2847-remove-manual-health-checks-that-are-automatically-handled-by-quarkus-000001-3ee42ca.pom

I'm using Jenkins LTS 2.332.3 with

• Maven integration plug-in 3.18
• Pipeline Maven Integration 3.10.0

Fill a new bug with updated environment and description please. This bug is very old and closed with success. Rework the same issue does not make sense.