Jorg Heymans wrote:
Carsten Ziegeler wrote:
It seems that the problem is much worse than we imagined. I just found
out that our fix which corrects the url on macos has the problem that
it now creates a url which the jdk on macos can't understand anymore.
So the jdk seems to know the bug and expects this behaviour.
Note that the 'fixed' version breaks on all OS'es, whereas the
originally 'broken' version only broke the testcase on macos. This is
what i find very hard to grasp as the fix did not change anything for
the common 'non-macos' case right ?
Yepp.
>
Also, the fix did not break the
existing sourceresolver tests, so it must have done something right...
Strange, indeed - my own applications run with 2.2.2 without problems.
I'm posting the unittest here that triggered all of this, so others can
chime in.
Thanks!
> So, it seems that we should remove the url fix again and rely on the
> buggy implementation.
>
> WDYT?
I'm afraid yes, unless someone has a better idea :(
Ok, I have just committed another fix and Cocoon 2.1.x now runs on MacOS
again. I'll test windows tonight. Instead of adding one slash I add now
two...I think a long time ago we had (or still have) a similar handling
in Cocoon. Anyway with this fix, Cocoon runs and the new test case in
excalibur passes as well.
Only the ZipSourceTestCase in Cocoon fails, because it now gets a uri
with three slashes and expects two.
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
