Well, I created the Jenkins Job, so we both hat our share ;-)
sebb schrieb am Mo., 13. Juni 2016 um 16:03 Uhr:
> On 13 June 2016 at 12:43, Benedikt Ritter wrote:
> > Thank you for bringing this up and for fixing the Problem!
>
> I probably caused it ...
>
> > sebb schrieb am Mo., 13. Juni 2016
On 13 June 2016 at 12:43, Benedikt Ritter wrote:
> Thank you for bringing this up and for fixing the Problem!
I probably caused it ...
> sebb schrieb am Mo., 13. Juni 2016 um 12:32:
>
>> A Commons NET test was failing on Jenkins, but worked fine locally.
>> And previously had been working on Co
Thank you for bringing this up and for fixing the Problem!
sebb schrieb am Mo., 13. Juni 2016 um 12:32:
> A Commons NET test was failing on Jenkins, but worked fine locally.
> And previously had been working on Continuum.
>
> Turns out this was because Jenkins uses path names of the form
> .../c
A Commons NET test was failing on Jenkins, but worked fine locally.
And previously had been working on Continuum.
Turns out this was because Jenkins uses path names of the form
.../commons-net@n/.
The test code was using the following to get the source location:
java.security.CodeSource.getLocat
