Ainsi parlait [EMAIL PROTECTED] : > Oh: while I'm here - make it 4 notes: > > - Love the little fix/add graphics in bin distro docs/releases.html! > > - The .jar packaging change thing: why not just have xerces.jar and > xmlParserAPIs.jar? Sure, it's a little more correct to call it an > '...Impl.jar', but this makes users make two classpath changes instead of > just one. Personal preference, I suppose: more precise naming or keeping > more backwards compatibility. The 'keeping more bacward compatibility' motto result in ever increasing naming nightmare and ambiguities :-(
A perfect exemple: why is xml-api code from xml-commons stored into a module named java/external ? Apart after careful examination of classes files found three directories later in src/javax/xml, how can someone deduce he has found was he was looking for ? And if it is a distinct subproject, why doesn't it have a clear version tag ? -- Guillaume Rousse <[EMAIL PROTECTED]> GPG key http://lis.snv.jussieu.fr/~rousse/gpgkey.html
