Hey Scott, Actually, after some experimenting, this change will not be needed. Generally, it is not the case that the client of the API needs to specify both the entry point name and the project name. As such, it is sufficient to append the project name to the end of the module name, and have WebAppCreator do its thing.
Sorry about the unnecessary traffic, and thanks for your input. Rajeev On Wed, Jan 14, 2009 at 4:35 PM, Rajeev Dayal <rda...@google.com> wrote: > Hi Scott, > > I'd like to you do a code review. To apply this patch, navigate to the the > root of the GWT 1.6 releases branch, and perform the following steps: > > svn update -r4449 > patch -p0 < updatedWebAppCreatorWithProjectNameParam-r4449.patch > > Description: > > In the migration from ApplicationCreator to WebAppCreator, the parameter to > specify the Eclipse project name to the createApplication method was > removed. This is a useful argument, as there are other clients of this API > that wish to specify the Eclipse project name directly, instead of having it > inferred from the module name. > > Affected Files: > > M user/src/com/google/gwt/user/tools/.projectsrc > M user/src/com/google/gwt/user/tools/App.launchsrc > M user/src/com/google/gwt/user/tools/WebAppCreator.java > > > Thanks, > Rajeev > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
