I verified Roger's fix works in our deployment. and I even have a fix on top of that to get it showing the jslint errors inside the code (the current plugin expects absolute paths reported by jslint, but jshint reports relative paths, and thus can't find the corresponding code).
It's been 2 years since there was a release of jenkins-violations-plugin, and it's starting to look abandoned. Roger are you going to request commit access? Or should I? I'm willing to work through the backlog of pull requests. On Sunday, March 2, 2014 11:58:57 AM UTC-8, Daniel Beck wrote: > > If nobody responds, you can just request commit access and merge it > yourself: > > http://jenkins-ci.org/pull-request-greeting > > On 02.03.2014, at 18:33, Roger Hu <roge...@gmail.com <javascript:>> > wrote: > > > Can someone review this PR and consider merging it into the branch? > > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
