I've asked this question on the Jenkins email list a week ago (where I think it belongs) and on StackOverflow, but I've gotten no results. I know this isn't a Maven issue per se' because a local build does show compiler syntax errors, but I'm at wits end and hoping someone on this list may have seen this issue before and offer some insight.
I've posted this question to StackOverflow here: http://stackoverflow.com/questions/9229020/jenkins-not-showing-maven-compiler-errors I'll summarize here, but to see full output I hope you wouldn't mind clicking that link - the output is long and better encapsulated there then in this email. When Jenkins 1.450 builds my maven 3 project, if there are compiler errors all I get is an exception from the maven-compiler-plugin (2.0.2) and not the actual syntax errors you usually see. When building locally, you _do_ get the syntax errors. Jenkins used to show the compiler syntax errors but stopped doing so about two weeks ago. What changed? We switched from maven 2.2.1 to maven 3.0.4, but I'm fairly certain we got compiler errors in the output just after the switch (but can't verify this). I found a similar (possibly the same) issue on Jenkins' Jira: https://issues.jenkins-ci.org/browse/JENKINS-10333 but no action had been taken. Has anyone else seen this? Is this a Jenkins issue or a Maven issue (or both)? -tim Tim Drury Architect SAP Manufacturing Execution (SAP ME) Supply Chain Management SAP Labs, LLC T +1 404 943 2088 F +1 610 492 2257 mailto:t.dr...@sap.com www.sap.com Please consider the impact on the environment before printing this e-mail.
