Just a data point for you, I do both of these (separate eclipse project and separate entry point within a project) for different reasons, and it works great. First, I have multiple distinct applications, but with some common generic code I'd like to share between them, like widgets and utility classes. So I have a "Common" eclipse project which has its own .gwt.xml, ant compile etc, but no entry points - it's basically a library.
But for the admin tool, there were so many common data-specific classes and widgets that it didn't make sense to try to break out a separate project and deal with sharing all the commonalities. So, I just created a new "admin" package in the project, and gave its own client, server, public directories, with new .gwt.xml, .html, and .launch files copy/modified from the main app and pointing to the admin entry point (no need for separate .project file). On deployment I just use a different ant target to build separate web apps for each. I think the decision to keep it in one project is one of convenience and maintainence, for two apps that will share a lot of data classes and widgets, it becomes tedious to maintain them across projects. jk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
