Hi ! I tried this new release and unfortunately I can't make it work, although the Preview release worked fine for me.
I'm using Maven to manage my projects and I prefer not to use WTP as I had bad XP with it. So I configured a project this way : - created a pom.xml - created the directories src/main/java, src/main/webapp - created a web.xml file in src/main/webap/WEB-INF directory - imported all that into Eclipse using "Import > Existing Maven Projects" - created a file application.html into src/main/webapp directory - created a GWT module <rootpackage>.Application.gwt.xml - created an Entry point <rootpackage>.client.ApplicationEntryPoint - added the GWT Nature to the project - checked the box 'This project has a WAR directory' - filled in the WAR directory input with src/main/webapp - unchecked the box 'Launch and deploy from this directory' Then I tried to launch the application with 'Run As > Web Application'. I chose the WAR directory target/<project>-<version>. No errors/warning appeared in the console and the 'Development Mode' contained the correct URL : http://127.0.0.1:8888/application.html?gwt.codesvr=127.0.0.1:9997 So far everything seems fine. I started my Firefox and entered the above URL and unfortunately the browser displayed a *404 NOT FOUND* page !!! I restarted the application with a debug level set to TRACE and I saw this in the CONSOLE : ----- Linking module 'application' Invoking Linker RPC policy file manifest Invoking Linker Standard Invoking Linker Export CompilationResult symbol maps Invoking Linker Emit compile report artifacts Linking compilation into <projectpath>\war\application ----- Why does it want to link in the /war directory instead of the target/ <project>-<version> ??? Did I miss something ? My plugin versions : Eclispe 3.5 M2Eclipse 0.10.0.20100209-0800 Google Plugin for Eclipse 1.3.0.v201003161223 Google Web Toolkit SDK 2.0.3 2.0.3.v201002191036 Thanks for any help ! :) On 17 mar, 02:34, Keith Platfoot <[email protected]> wrote: > Hi everyone, > > I'm happy to announce the release of version 1.3 of the Google Plugin for > Eclipse (http://code.google.com/eclipse). > > This release is designed to make life easier for developers using GWT and/or > App Engine alongside third-party tools. For example, we've taken the pain > out of using the plugin with projects built with the ever-popular Maven > build system: no more ugly hacks or workarounds, or polluted WEB-INF/lib > directories! We've even added a new FAQ dedicated to Maven > usage:http://code.google.com/eclipse/docs/faq.html#gwt_with_maven. > > We've also worked hard to make sure the plugin works well with Dynamic Web > projects in Eclipse for Java EE. See the following FAQ for details on this > scenario:http://code.google.com/eclipse/docs/faq.html#gwt_in_eclipse_for_java_ee. > > In addition to improving third-party interoperability, we've also made the > plugin more customizable and robust overall. Launch configurations now > allow direct editing of generated command line arguments, and a new > Errors/Warnings preference page lets you tweak the severity of any problem > marker we create. We've also fixed a number of bugs related to App Engine > ORM enhancement. > > To install the Google Plugin for Eclipse, you can find our update site URLs, > along with detailed instructions, > here:http://code.google.com/eclipse/docs/download.html > > If you're upgrading from a previous version of the plugin, you may want to > consult our Upgrading the Plugin > guide:http://code.google.com/eclipse/docs/updating_the_plugin.html > > *Note: If you installed the Google Plugin for Eclipse 1.3 Preview, be sure > to remove the relevant subfolders from your <eclipse>/dropins folder before > installing the official 1.3 release via the update site.* > > *Enhancements* > > - Configurable WAR directory to allow better integration with Eclipse for > Java EE and projects built with Maven > - Web Application launch configurations now display and allow editing of > generated Program and VM arguments > - Errors/Warnings preference page for customizing the severity of any > generated problem marker > - Projects can reference GWT/App Engine SDKs directly via JARs instead of > through SDK library > - GWT+App Engine projects automatically configured for optimal caching > > *Fixes* > > - GWT Issue 3583: Google Eclipse Plugin configuration is too strict > - GWT Issue 3592: Eclipse plugin to add 'cache forever' configuration for > new 'GWT + App Engine' projects > - GWT Issue 3902: Allow users to configure the severity of problems > reported by the eclipse plugin > - App Engine Issue 1515: Eclipse plugin requires fixed location for war > directory > - App Engine Issue 2115: Using the @PersistenceAware annotation puts the > Eclipse Enhancer in an Infinite Loop > - App Engine Issue 1941: Plugin fails to enhance dependent classes on > source level changes > > For a complete list of fixed issues, see the GWT issue tracker and App > Engine issue tracker. > > We hope you enjoy using this new version of the Google Plugin for Eclipse > for all your GWT/App Engine development needs! Let us know if you have > questions or run into any issues. Thanks! > > Keith, on behalf of the Google Plugin for Eclipse team -- 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.
