> 1) You have to maintain three projects (or a Maven multi-module project if > you're using Maven) instead of one. > 2) You'll have two different app servers to configure & maintain. > 3) You'll probably need to maintain database credentials in two different > places. > 4) You can't use Tapestry's Live Class Reloading on any class in the common > JAR (e.g. Tapestry IOC service implementation classes).
I think 4) is the biggest downside in a multi-module project. Do you think Tapestry can do a Live Class Reloading of the common JAR included with contributeCoreLibComponentClasses? > 5) If you use an automated build server like Jenkins then you'll have to > set up and maintain triple the number of jobs. > 6) Your build process will be slower and more error prone because you'll > often have to build the common JAR before building and deploying you'll > have different log files. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
