Sorry guys, I made the jsl change, which was to make site builds work with versions 1.9+ of the xdoc plugin. I thought I had tested successfully with 1.8, but now see that I must have failed to clear the plugin cache or something. My bad. So...current state is that commons-site.jsl *requires* v. 1.9+ of the xdoc plugin. Use
maven plugin:download -DgroupId=maven -DartifactId=maven-xdoc-plugin -Dversion=1.9.2 to download 1.9.2 Unfortunately, without the change, the site build does not work correctly with 1.9+, so my inclination is to leave the change in for now. I will roll back the change, though, if others feel differently. i will also ask on the maven list if there is some way to patch the site.jsl to work with both versions. Phil On 9/9/05, Niall Pemberton <[EMAIL PROTECTED]> wrote: > > The problem is the update that was made to "commons-site.jsl" 9 days ago: > > http://tinyurl.com/dvab5 > > If you reverse out that change the problem goes away. > > Niall > > ----- Original Message ----- > From: "Don Brown" <[EMAIL PROTECTED]> > Sent: Friday, September 09, 2005 10:52 PM > > > It seems this maven problem affects all the commons projects that use the > commons-build. I'm seeing it on Linux and Windows, both running Maven > 1.0.2. > > Again, the problem is when running "maven site". When it gets to the > jdepend > report, I see: > > xdoc:jelly-transform: > [echo] Generating > /home/mrdon/dev/fileupload/target/docs/jdepend-report.htmlfrom > /home/mrdon/dev/fileupload/target/generated-xdocs/jdepend- > report.xml > Could not find the class: org.apache.commons.jelly.tags.fmt.FmtTagLibrary > java.lang.ClassNotFoundException: > org.apache.commons.jelly.tags.fmt.FmtTagLibrary > > > Is anyone else seeing this problem? I've tried removing ~/.maven but with > no > luck. > > Don > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
