What i've done for our company where we work with 3 people on one site is to divide the site into smaller component libraries, each library is a standalone JAR which on deployment get released in the WEB-INF\lib folder allowing the 'main' site to find this module and make use of it.
see: http://tapestry.apache.org/component-libraries.html This way developers can work independently on his/her library. Each library on its own is dependent on the 'main' core library that has some basic functionality exposed trough services like a logger, auditing and a DAO layer. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Managing-a-large-multi-team-project-with-Tapestry-5-tp4311656p4312638.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
