>> >>What I'm after is a single javadoc, changelog, checkstyle etc > > > Yes, I understand that but isn't it enough for you to have a master > javadoc page listing all subprojects for examples and when you click on > one you get the javadoc for that subproject? If you have divided them in > different projects, it must be because there is some differentiator > between them, no? > > Same for the other reports. >
I can think of situations where you would want both. From the top down, a project could be a whole application that is being delivered to a client. This project is being developed by a single dev team, management team, a single ear file. Tasks such as CVS labels etc are done across the whole project. However, structurally, it might make sense to split the project into a number of 'maven' sub projects, e.g. a few ejbs, a few webapps, util jars etc. From the top down you might want to see information like 'changes since the last release' across the whole project rather than in an individual ejb-jar. Similarly with Javadocs, you might prefer to see the whole doc bundle rather than having to navigate between different javadoc trees. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
