Good stuff! I was fiddling around with trying to generate the site with Maven a while ago, but I think I was trying to kill too many birds with the same stone, so to speak. Tackling it as you have seems like a more expedient approach.
I do have the same question as James, though: Can we still generate the TLDs from the same XML as the taglib docs? This is one place that I got bogged down, since it seemed that Maven wouldn't take the extra XML elements, and I would absolutely hate to lose the guaranteed synchronisation we get from using the same source. The best I could come up with was keeping the XML format we have, and using XSLT in a a pre-goal to morph it into what Maven likes. However, if what you've got works already, that would be excellent! Another thing I was trying to tackle - which, in retrospect, was much too big to do in one chunk, let alone with everything else too - was creating a completely generic "main site" that hands off to the sub-project sites, where the main site doesn't get into the details of 'classic' or 'core' or anything like that. Finally, I'd like to see us make a conscious separation between documentation and web site, and have the documentation be separate downloads (_not_ as a war file) available in a number of formats - minimally HTML and PDF. Lots of lofty goals, I know, but that's what I'd ultimately like to see. That's not to lessen at all the great start you've got us off to, Wendy. Thanks! -- Martin Cooper On 8/9/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > In keeping with the Maven-or-Ant thread, it's time to think about switching > to the Maven-generated multi-project website. James has had the "basic" > Maven-generated site available for a while now with the nightly builds. > > I made a start on integrating the existing site with Maven's, and posted the > first draft here (also beside the nightly builds): > > http://svn.apache.org/builds/struts/maven/trunk/site-test/index.html > > For now all the menus are expanded so you can see what's there. The menu > structure and navigation are still under construction. :) > > This involved copying the existing xml files from > /current/core/doc/ into /current/build/xdocs/, renaming the project.xml > files to navigation.xml, and doing some cleanup. So, other than it being in > a different location in the repository, nothing changes about the way you > modify the documentation, and none of the links from other sites to ours > will be broken. > > The main motivation for this was the realization that even if I update the > existing site, I have no idea what to do about the half-dozen sets of > JavaDoc. Maintaining an index page and copying the JavaDoc out of each > sub-project isn't appealing, especially not when Maven will take care of it > for you. > > The 'multiproject' part of the site is towards the bottom of the menu, under > 'Projects'. For example, here is the Project Reports section for Struts > Core: > > http://svn.apache.org/builds/struts/maven/trunk/site-test/multiproject/struts-core/maven-reports.html > (And yes, I realize there's currently no way to get back to the main site > from here.) > > What do you think? Should this eventually become the "official" Struts > site? > > -- > Wendy Smoak > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
