On Jun 25, 2013, at 7:54 AM, Henri Yandell <flame...@gmail.com> wrote:
> Help much appreciated - but do we want all the content of all the modules > to be there? > > It feels to me that the website does not map directly to the codebase. We > want an overall site, and subsites for Standard and for RDC. We don't want > to have the 14 pom.xmls become a site structure, or the 4 pom.xmls > (tld-generator and extended). Three mini-sites sounds good: a top-level one holding things together and then sub-sites for standard and RDC. Is there a way to associate the top-level one with the parent POM and the others with the "root" poms in standard and rdc? That would match with the things that are likely to be released (being all "standard" packages together, or all "rdc" packages together, but not both at the same time). Do we still need an aggregator pom as well - how about setting up separate CI jobs for "standard" and "rdc"? From the "standard" side, how about killing the separate "doc" "examples" and "standard-test" modules, rolling the documentation and examples into the site and the test cases into unit or integration tests in the individual modules? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
