not be written…
>
> Ulli
>
> Am 28.12.2012 um 12:24 schrieb Markus Schneider :
>
>> Hi Ulli,
>>
>> I have done some debugging and solved my issues:
>>
>> 1) Empty tmp source file, without any log statement why it is emtpy.
>>
>>
onding configuration option in the extended
section. Stupid me, not seeing it before.
Thanks,
Markus
Am 27.12.2012 um 16:07 schrieb Markus Schneider :
> Hi Ulli,
>
> i have changed the path to the file in the warning.
>
> It looks now like this: "src\test.c", line 19
012 um 22:10 schrieb Markus Schneider :
> 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\work
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 :
>
d console log? What is the corresponding warning result in
> warnings-[yourparsername].xml in the build folder? Is the path expanded
> there?
>
> Thanks, Ulli
>
> Am 13.12.2012 um 20:22 schrieb Markus Schneider :
>
>> Hello Ulli,
>>
>> Yes the relative p
I have tried it, but the parser throughs an error not knowing "$JenkinsHome"
string.
Am 13.12.2012 um 04:04 schrieb "Strausser, Barrett"
:
> You could probably do $JenkinsHome + "/jobs/" + $WorkSpace
>
>
>
>
> On Wed, Dec 12, 2012 at 5:58 PM, schneim wrote:
>> Hello,
>>
>>
>> I have cr
Hello Ulli,
Yes the relative path does not work for me. The tmp files are generated, but
are empty.
Do I need a special configuration?
Markus
Am 13.12.2012 um 16:02 schrieb Ulli Hafner :
> Actually, a relative path (starting from the workspace root) should be
> resolved automatically. Doe
