In regards to the different artifacts that are produced by the webAppCreator utility and the Eclipse plugin; at its core the webAppCreator simply creates a skeleton web app that is not tied to a particular IDE. We do offer build targets that will allow you to more easily import your project into Eclipse (ant eclipse.generate), but even then we generate the associated .project file in such a way as to let the developer choose how he/she wants to launch the app (Java launch config vs. Web App launch config).
On the flip side, when you create a project with the Eclipse plugin, we *are * able to make a few assumptions as to which IDE and launch config you would prefer based on the environment from which you created the project. - Chris On Fri, Dec 11, 2009 at 2:41 PM, jbdhl <[email protected]> wrote: > Thanks. I guess the answers to c) and d) are > > c) by making the project use "Google Web Toolkit" as explained > above. > > d) I guess I don't: If I make one initial compile using ant, the > jar's will already be placed in WEB-INF/lib and a conventional GWT- > button-compile will (probably) suffice. > > I still don't understand the inconsistency of the generated contents > by the two methods described in question a). > > -- > > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > > -- 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.
