Hi Ulli,

i have changed the path to the file in the warning.

It looks now like this:  "src\test.c", line 199: warning #550-D: variable 
"test" was set but never used

However, the path is not expanded.

Any other suggestions, what I can try?

Thanks,
Markus


Am 15.12.2012 um 22:10 schrieb Markus Schneider <markus.schnei...@jemm.de>:

> Hi,
> 
> Actually this what I have done in the regex. 
> As you can see below, the groovy output has removed the relative path 
> section. 
> However, there is no concatenation with the workspace path:
>> C:\programme\Jenkins\test-ci\workspace
> 
> 
> Can I do some debugging? Which class is appending the complete path?
> 
> Markus
> 
> Am 15.12.2012 um 13:22 schrieb Ulli Hafner <ullrich.haf...@gmail.com>:
> 
>> I see, that can't work. 
>> 
>> Where is the src folder located? 
>> C:\programme\Jenkins\test-ci\workspace\src?
>> 
>> My plug-in concatenates the workspace path and the found path in the 
>> warning, which results in your case to 
>> C:\programme\Jenkins\test-ci\workspace\..\..\..\src\test.c
>> A simple solution would be to strip off the relative path section in your 
>> groovy parser so that the concatenation works.
>> 
>> Ulli
>> 
>> Am 15.12.2012 um 11:37 schrieb Markus Schneider <markus.schnei...@jemm.de>:
>> 
>>> Hi Ulli,
>>> 
>>> 
>>> thanks for your help. Here is some more information:
>>> 
>>> Jenkins: V1.493
>>> Warnings-Plugin: V4.18
>>> Static Analysis Utilities: V1.48
>>> OS: Windows XP
>>> 
>>> 
>>> Workspace Path: C:\programme\Jenkins\test-ci\workspace
>>> Example Warning:   "..\..\..\src\test.c", line 199: warning #550-D: 
>>> variable "test" was set but never used
>>> 
>>> Parsed result  in parser configuration page is:
>>> file name: src\test.c
>>> line number: 199
>>> category: #550-D
>>> 
>>> Project configuration uses "Scan workspace files"  with pattern **/*.log 
>>> 
>>> 
>>> From warnings.xml:
>>> 
>>> <fileName>src/test.c</fileName>
>>> <pathName>src</pathName>
>>> 
>>> 
>>> -> path is not expanded in xml
>>> 
>>> 
>>> Thanks,
>>> Markus 
>>> 
>>> 

--
Markus Schneider
markus.schnei...@jemm.de




Reply via email to