[
https://issues.jenkins-ci.org/browse/JENKINS-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161619#comment-161619
]
Jacob Larfors commented on JENKINS-13411:
-----------------------------------------
Hi Krzysztof,
The response from Gwyn is as follows:
"This is indeed by design. Frankly, if you want to explore a defect, you should
be doing it in the native environment, using the provided URL (from the Web
API) to access Review at the right place, from where you can interact with the
source, x-ref, all the nice functionality that you get there. And yes, before
the question arises, reserving the line number was done specifically to avoid
people trying to explore defects in environments that don't provide a rich
enough infrastructure and therefore encourage developers to dismiss defects
without truly understanding them (or cite them as noise, which amounts to the
same thing)."
Also, when you say "marking source with Klocwork findings", what exactly do you
mean? If you would like an xml/txt report with line numbers then this can be
gained from Review on the "Issues" page.
> Klocwork XML output is deprecated
> ---------------------------------
>
> Key: JENKINS-13411
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13411
> Project: Jenkins
> Issue Type: New Feature
> Components: klocwork
> Reporter: Krzysztof Malinowski
> Assignee: gbois
>
> As http://www.klocwork.com/products/documentation/current/Kwinspectreport
> states: XML report is deprecated in KW 9.5 and will no longer be available. I
> recommend that plugin uses some other parser for the issues (csv maybe) or
> use web api to get the issues.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
