Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reasons are not displayed for jslint issues #23

Open
sbrandwoo opened this issue Dec 17, 2012 · 5 comments
Open

Reasons are not displayed for jslint issues #23

sbrandwoo opened this issue Dec 17, 2012 · 5 comments

Comments

@sbrandwoo
Copy link

When the I view the violations report for my jslint issues, the reasons are not shown anywhere in the UI.

I see a full list of files that are in error, but upon clicking through I see only a blank page with a warning icon on it - the reasons are not put on the screen.

My jslint.xml is of this form:

<?xml version="1.0" encoding="UTF-8"?>
<jslint>    
    <file name="path/to/file.js">
        <issue line="8" char="1" reason="The reason for failure" />
    </file>
    ....
</jslint>
@hashar
Copy link

hashar commented Jan 22, 2013

I believe this is a duplicate of #17 and or https://issues.jenkins-ci.org/browse/JENKINS-14291

The violations plugin basically can not find the files in the per file detailed report.

@rogerhu
Copy link
Contributor

rogerhu commented Mar 19, 2013

Will someone merge #13? :) If someone has an explanation too about why it's necessary to subclass just to get it to work, would be happy to hear!

@gregwym
Copy link

gregwym commented Jul 14, 2014

Seems like this will never be fixed.

@rogerhu
Copy link
Contributor

rogerhu commented Jul 14, 2014

It was merged 3 months ago. :)

@gregwym
Copy link

gregwym commented Jul 15, 2014

Thanks @rogerhu, but has it been published yet? I installed the latest from plugin manager and still couldn't see report for jslint file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants