Answering off the general list as they probably don't want to hear this bit:
I was thinking more of a generated version. So a projects.xml which defines a group of project.xml. It would create a unified xref'd source, one big javadoc [although the projects would have small ones still]. It would suck developers up from the project.xml and list them with the projects they work on. I think it's something I can get going quite easily, basically I would write a projects.xml structure which linked to project.xml's, then I would generate out a large project.xml and run Maven over it. It would not build or unit test or worry about any of the reports. Let me know if you think it has distance... It seems to me that the Turbine one is done by hand, but hard to tell. If you already have it then let me know. On Thu, 27 Jun 2002, Jon Scott Stevens wrote: > on 6/27/02 12:15 PM, "Henri Yandell" <[EMAIL PROTECTED]> wrote: > > > I'm hoping that an aspect of maven will focus on dealing with collections > > of projects at some point. creating a top level site for them, grouping > > documentation. > > http://jakarta.apache.org/turbine/ > > I see a list of 9 subprojects in the grey bar under the logo's... > > > If it can be nice and recursive, then it could create a nice automated > > system with a common look and feel. I guess a lot of that is really xdoc > > and not maven. > > That would be nice. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
