Hi Ulli (or anybody else that might know!) I've done as you suggest and I've now got a decent graph of coding errors and it's related report :-)
There is just one issue. In the report screen If I click through on a coding bug I get the following error: 1 Copying the source file 'Scripts.js' f rom the workspace to the build folder '/d evel/.jenkins/jobs/TestProject/builds/2013-03-13_12-11-38 /workspace-files/a13c15a4.tmp' on the Hudson master failed. 2 Seems that the path is relative, however an absolute path is required when copying the sources. 3 Is the file 'Scripts.js' contained more than once in your workspace? 4 Is the file 'Scripts.js' a valid filename? 5 If you are building on a slave: please check *if * the file is accessible under '$JENKINS_HOME/[job-name]/Scripts.js' 6 If you are building on the master: please check *if * the file is accessible under '$JENKINS_HOME/[job-name]/workspace/Scripts.js' Any idea what the problem is? Thanks On Tue, Mar 12, 2013 at 5:02 PM, John Smith <[email protected]>wrote: > Thanks for getting back to me. > > I'll probably go with option 3 as the quickest option ;-) > > > On Tue, Mar 12, 2013 at 4:33 PM, Ulli Hafner <[email protected]>wrote: > >> I see, the format of javac using maven is slightly different: >> >> [WARNING] /home/hudson/hudson/data/jobs/Hudson main/workspace/remoting/ >> src/test/java/hudson/remoting/BinarySafeStreamTest.java:[3,54] >> com.sun.org.apache.xerces.internal.impl.dv.util.Base64 is Sun proprietary >> API and may be removed in a future release >> [WARNING] /home/hudson/hudson/data/jobs/Hudson main/workspace/remoting/ >> src/test/java/hudson/remoting/BinarySafeStreamTest.java:[36,24] >> com.sun.org.apache.xerces.internal.impl.dv.util.Base64 is Sun proprietary >> API and may be removed in a future release >> [WARNING] /home/hudson/hudson/data/jobs/Hudson main/workspace/remoting/ >> src/test/java/hudson/remoting/BinarySafeStreamTest.java:[47,24] >> com.sun.org.apache.xerces.internal.impl.dv.util.Base64 is Sun proprietary >> API and may be removed in a future release >> [WARNING] /home/hudson/hudson/data/jobs/Hudson main/workspace/remoting/ >> src/test/java/hudson/remoting/BinarySafeStreamTest.java:[69,24] >> com.sun.org.apache.xerces.internal.impl.dv.util.Base64 is Sun proprietary >> API and may be removed in a future release >> [WARNING] /home/hudson/hudson/data/jobs/Hudson main/workspace/remoting/ >> src/test/java/hudson/remoting/BinarySafeStreamTest.java:[105,25] >> com.sun.org.apache.xerces.internal.impl.dv.util.Base64 is Sun proprietary >> API and may be removed in a future release >> >> You can either >> 1) File a bug report for the maven plug-in to use the same format as the >> javac compiler >> 2) File a bug report for the warnings plug-in to add a new parser (or >> even better: provide a pull request ;-) >> 3) Create your own dynamic parser in Jerkins' global configuration screen >> >> Ulli >> >> >> Am 12.03.2013 um 14:58 schrieb John Smith <[email protected]>: >> >> Hi, >> >> I've done as you suggest and changed the parser to "java Compiler >> (javac)". The good news is that the builds all work, but unfortunately the >> graph on the project page is has got a 0 count. I wasn't expecting this >> because the console shows errors like: >> >> [WARNING] scripts.js:11:21:Expected '===' and instead saw '=='. >> [WARNING] scripts.js:13:13:Combine this with the previous 'var' statement. >> [WARNING] scripts.js:42:21:Expected '===' and instead saw '=='. >> [WARNING] scripts.js:45:13:Combine this with the previous 'var' statement. >> [WARNING] scripts.js:46:58:['classCode'] is better written in dot notation. >> >> My guess is that the warnings plug-in hasn't noticed the errors. >> >> >> >> On Fri, Mar 8, 2013 at 5:12 PM, Ulli Hafner <[email protected]>wrote: >> >>> Hmm, seems that the messages of the maven JSLint plug-in use a different >>> warnings format. You need to choose the parser "Javac". >>> >>> Ulli >>> >>> >>> Am 08.03.2013 um 16:32 schrieb John Smith <[email protected]>: >>> >>> Actually..... >>> >>> I've added the following to the parent POM >>> >>> <plugin> >>> <groupId>org.apache.maven.plugins</groupId> >>> <artifactId>maven-compiler-plugin</artifactId> >>> <configuration> >>> <showDeprecation>true</showDeprecation> >>> <showWarnings>true</showWarnings> >>> </configuration> >>> </plugin> >>> >>> but I keep getting the following exception at the end of my build: >>> >>> [WARNINGS] Parsing warnings in console log with parser JSLint ERROR: >>> Publisher hudson.plugins.warnings.WarningsPublisher aborted due to >>> exception org.kohsuke.stapler.framework.io.IOException2: >>> org.xml.sax.SAXParseException: Content is not allowed in prolog. at >>> hudson.plugins.warnings.parser.JSLintParser.parse(JSLintParser.java:61) at >>> hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:313) >>> at >>> hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:292) >>> at >>> hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:352) >>> >>> >>> Any ideas? >>> >>> >>> On Fri, Mar 8, 2013 at 12:12 PM, John Smith <[email protected] >>> > wrote: >>> >>>> <embarrassed> >>>> >>>> Sorry I completely missed your reply - something to do with the way >>>> I've set gmail to forwards message I think :-/ >>>> >>>> My fault >>>> >>>> </embarrassed> >>>> >>>> I this looks like a viable workaround. I *was *hoping to use the >>>> Violations plug in simply because I'm already using it for Java Code in the >>>> same project. That said, there is no particular reason why I have to use >>>> the Violations plugin .... >>>> >>>> Thanks for your advice - I'll give it a go. >>>> >>>> >>>> >>>> >>>> >>>> On Fri, Mar 8, 2013 at 10:10 AM, Ulli Hafner >>>> <[email protected]>wrote: >>>> >>>>> Didn't the answer to your previous thread help? >>>>> >>>>> >>>>> http://jenkins.361315.n4.nabble.com/Q-How-to-use-Maven-JSLint-plugin-with-Jenkins-Violation-Plugin-tp4658337p4658374.html >>>>> >>>>> Am 08.03.2013 um 10:57 schrieb John Smith <[email protected] >>>>> >: >>>>> >>>>> Hi, >>>>> >>>>> Does anybody know how to integrate the "jslint-maven-plugin" from >>>>> "org.codehaus.mojo" with the Jenkins Violations plug-in? >>>>> >>>>> My current situation is that I've configured jslint-maven-plugin as >>>>> part of my maven build. Errors are being written to standard output, so >>>>> that's the console. In Jenkins I'd going to need to tell the plugin which >>>>> file contains the list of violations. The trouble is errors are not in a >>>>> file. >>>>> >>>>> So how to I bridge the gap? >>>>> >>>>> Thanks >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Jenkins Users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Jenkins Users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>>> >>>>> >>>> >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
