I don't really have time to bugger around with this any more, so I'm going to see if the dom4j 1.4 release will work as before. My main concern with sticking with 1.4-dev-8 is that there is no way to locate the sources.
We can live with the bugs in 1.4 (as we already are). If anyone with some knowledge of dom4j and jaxen wants to put their hand up to work through it and get up to dom4j 1.6/jaxen 1.1, please say so. - Brett Brett Porter wrote: >Ok, checkstyle fixed. Jelly leak fixed. > >The blockers at the moment: >- xdoc has somehow gotten back to not rendering links. Still has the >CDATA problems, and although so whitespace problems are fixed, others remain >- upgrading from jaxen 1.1 beta 4 to jaxen 1.1 beta 6 makes many jsls >fail - jdepend, checkstyle, changelog, etc. This might be a good thing >as it may be pointing to a dud JSL. >- these upgrades could well break existing JSLs, however. >- linkcheck is broken since the jaxen/dom4j upgrade too. > >I'm very much inclined to move straight into the process of replacing >the xdoc plugin with the Maven2 site stuff. This would get a lot of >testing early before being released. This should be backwards compatible >for everyone except those rolling their own JSLs, who are likely to be >broken whichever way we go, unless we rollback to dom4j 1.4-dev-8 which >has its own problems. > >Anyone have an opinion on this? > >Cheers, >Brett > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
