-
Bug
-
Resolution: Fixed
-
Critical
-
Windows 7, Linux
-
-
1.532.1
Since Jenkins version 1.526 my Console Logs do not log any Maven errors. Version 1.525 was still ok.
To reproduce this I tried deploying artifacts to a bogus repository, normally I would get something like this:
message : Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin...
But there is nothing now. Using Maven 3.0 or 3.1 makes no difference as well as calling Maven with -e or -X.
Jenkins and Maven plugin are at the same version (tried it with 1.526 and 1.528) only version 1.525 and lower gave me error messages in the log.
- depends on
-
JENKINS-15025 Maven-Tycho 0.15.0 build - no additional info in console log about compilation failure
-
- Resolved
-
- is blocking
-
JENKINS-19338 Cannot archive artifacts using Maven 3.1.0 on Windows slave
-
- Open
-
- is related to
-
JENKINS-20122 Maven 3.X build always marks as Failure
-
- Resolved
-
-
JENKINS-19396 Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger
-
- Closed
-
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-1201included 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.