Matthew Langham wrote: > > Carsten, > > why don't you try it out on our Linux system????? ;-) > What, we have Linux system? Ups. So, you take over some of my duty? Thanks, I will check that out then.
Carsten > Matthew > > -- > Open Source Group sunShine - Lighting up e:Business > ================================================================= > Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn > Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de > ================================================================= > > > -----Ursprüngliche Nachricht----- > Von: Giacomo Pati [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 26. November 2001 14:09 > An: [EMAIL PROTECTED] > Betreff: RE: Showstoppers for 2.0 final was RE: [tale+rant] The 2.0 > syndrome and [Vote]: Final Release Date > > > Quoting Carsten Ziegeler <[EMAIL PROTECTED]>: > > > Giacomo Pati wrote: > > > > > > On Mon, 26 Nov 2001, Carsten Ziegeler wrote: > > > > > > > To really get the final release out asap, we should identify all > > > > showstoppers. > > > > Currently entered in bugzilla are two blockers (I fixed the > > > third one (5051) > > > > recently). > > > > > > > > Here is the list from bugzilla: > > > > ------------------------------ > > > > ID Sev Pri Plt Owner State Result Summary > > > > 5060 Blo Oth PC [EMAIL PROTECTED] NEW Poorly formed > > > filesystem URL > > > > with file:// issues > > > > 5063 Blo Oth Oth [EMAIL PROTECTED] NEW Distribution > > > .war broken in > > > > Tomcat 4 > > > > > > > > I think, at least, #5060 is a real blocker, #5063 should be > > > easily fixed by > > > > changing the build scripts or adding some comments etc. > > > > > > > > If we can't fix 5060 very quickly, what about disabling the resolver > > for > > > > the final release? This would make 2.0 "block bug free". We could > > work > > > > on that "new" feature and make a 2.0.1 (or whatever) with a working > > > > resolver. > > > > > > > > So, what do you all think about these blockers? Let's fix them > > > and get this > > > > great release out! > > > > > > Additionally I had some hours over the last weekend to find out why > > the > > > documentations aren't build anymore. So turning on DEBUG level in the > > docs > > > target where Cocoon is started to produce the docs shows that URL of > > the > > > form "mailto:...";, "news:..."; and "anything#somepart" gets rendered > > and > > > throws ResourceNotFoundExceptions which is wrong and I haven't figured > > > what change has caused this because IIRC they had been working > > recently. > > > > > > Also, on the Avalon project I think they had the same problem as they > > have > > > upgraded recently (Cocoon and Xalan jars). > > > > > > Has anybody changed the Commandline classes recently? > > > > > I haven't changed the cli (at least I think so) - it seems like you have > > an > > old version of the LinkSerializer as I added the handling of these > > "special cases" some months ago(!). But they weren't in the initial > > release. > > Strange! > > > > What I don't get is why it's working here. Everything is fine with > > building docs: no mailto:, no news: etc. > > > > I just did a fresh clean checkout, used my Windows 2k, jdk 1.3.0 and > > typed > > in "build docs" and voila after some time I got the whole docs without > > any > > problems. > > > > Is there something different with your configuration? > > Yes, the OS, it's Linux. I too made a clean checkout (and I've checked it > more > that once with a 'cvs diff') but 'build.sh docs' will not work. > So I'd like > to > ask if other here have the same problems (I know Avalon is having problems > with > their docs building system based on Cocoon). > > Giacomo > > > > > Carsten > > > Giacomo > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, email: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, email: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
