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 kno
>Do you think that the m2 site stuff have the same functionnalities as m1
>(except for JSL)?
>
>
Mostly. We'd need to have a quick pass over it and add anything missing,
like maybe the classic stylesheet and a way to select it.
>How do you handle documents generated from the POM ?
>
>
They a
>
> 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
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
Hi,
I'm just trying to build sites with 1.1 and getting errors out of
checkstyle I wasn't before. Was the upgrade to 4.0 beta tested? Just
wondering if it is my environment, or if it was just upgraded without
looking into it. It looks like its got classloader issues.
Most of the core hinderances
