On 11/21/05, Craig McClanahan <[EMAIL PROTECTED]> wrote: > I use the "current" svn:externals thing as well, and run "maven site" from > the top-level Shale directory (the one containing the global > build.xmlfile). For me, that's at: > > /home/craigmcc/Apache/struts/current/shale > > However, I see the broken copyright from here,
That's what I would expect. With no Maven build files in current/shale I'm surprised you get anything at all. All the maven commands need to be run from current/shale/build or somewhere beneath it. > or from the "build" directory below it: > > /home/craigmcc/Apache/struts/current/shale/build > > Same problem if you run "maven multiproject:site" from here ... just takes > longer to see it :-). And you're looking at the results underneath 'build', in /home/craigmcc/Apache/struts/current/shale/build/target/docs ? Is the missing inception year the only thing that's wrong? At this point I usually start checking plugin versions. I have maven-site-plugin-1.6.1 and maven-xdoc-plugin-1.9.2, both of which are the latest. (I'm looking in 'cache' under my m1 repository... I've moved mine, but I think the default is: ~/.m2/repository/ .) Or just download them with: maven plugin:download -DgroupId=maven -DartifactId=maven-site-plugin -Dversion=1.6.1 maven plugin:download -DgroupId=maven -DartifactId=maven-xdoc-plugin -Dversion=1.9.2 This is strange, though. Maybe redirect the output and send me the log? If you do that, I'd like to see 'maven site' and 'maven site -X' separately. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
