Hi again Pierre, In my experience, having to manage two or more separate GWT applications can be really cumbersome. I'd recommend it only in cases where you have explicitly two or more independent products. In cases where you allow the user to switch from one app to other, or you have a large shared codebase among the apps, I suggest to consider unifying the apps into a single one, and manage the pages and URLs by using a framework for that (Activities and Places <http://www.gwtproject.org/doc/latest/DevGuideMvpActivitiesAndPlaces.html>, GWTP <https://github.com/ArcBees/GWTP> and gwt-views <https://github.com/gilberto-torrezan/gwt-views> are some examples of such frameworks).
But of course all depends on your specific use cases. In my case I had three GWT applications that was part of a larger product. After years maintaining those three separate applications, I decided it was better to just unify them all and fix the user navigation problems (when you have more than one application, the state of the app is not shared among other applications - assuming a stateless server - so when the user switches over apps, the state is lost, and that can hurt the UX). About the maven stuff, it can really help you if you decide to split not only the GWT modules, but the Java projects as well. If you have, for instance, 3 GWT modules within 3 Java projetcs, maven can help you manage the dependency chain among the projects. But if you decide to use a single project (with or without multiple GWT modules), maven won't help as much. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
