Wendy wrote:
But there are things in the common build file that are *not* common to all subprojects.
We needs a way to make sure that core/taglib/el/apps/plugins are all using the same versions of their dependencies, without imposing those dependencies on 'standalone' subprojects. How about: /current/build/project.xml ... has the list of committers, reports, etc. Only things that are common to *all* sub-projects /current/build/project-core.xml ... <extend>project.xml</extend> ... has the list of dependencies for struts-core Then each subproject chooses which build file to extend. - core, taglib, el, struts-tiles, apps, plugins can all extend build/project-core.xml in order to keep their dependencies on [mostly] commons libraries in sync. Even if the subproject doesn't necessarily need one of the dependencies that struts-core does, you can't use these subprojects without core, so you end up needing that dependency anyway. Subprojects can add additional dependencies, but can't remove the ones they inherit from core. - Faces, Standalone Tiles, etc., can extend from the generic 'project.xml' to pick up the list of committers, reports, etc., but are responsible for their own dependencies. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
