Hi Andreas, Hm, not sure why you're seeing that error. Let me ask a few questions to see if we can get to the bottom of this.
1. You set the WAR directory to 'src/main/webapp' via the Google > Web Application project properties page, right? Did you also uncheck the box below that says 'Launch and deploy from this directory'? This is necessary because the 'src/main/webapp' directory is not a complete WAR directory (WEB-INF/lib and WEB-INF/classes are empty, etc.). 2. Are you launching the project using the regular Run/Debug As > Web Application shortcut? Did you make sure to first delete any other Web Application launch configurations associated with the project? 3. When you launch, you should be prompted to select the runtime WAR directory. Unless you're also using Eclipse for Java EE, you'll probably want to first do a 'mvn clean package' and then select the exploded WAR in '/target/<AppName>-<version>' as your runtime WAR. 4. When you launch, are you seeing the Development Mode view appear at the bottom of your workspace, with a URL to open in your browser? Does the URL have a ?gwt.codesvr=x.x.x.x:9997 at the end? Does your web browser have the GWT Development Mode plugin installed? (the browser should load a page to prompt you if it's not installed). 5. After you launch, what are the arguments in the generated launch configuration? One of the features of 1.3 is the ability to inspect/tweak the arguments via the regular Arguments tab in the launch configuration dialog. Let me know what your exact argument set is. Also: to see code changes reflected when you hit refresh, you'll need to get the class files into your runtime WAR directory. One simple way to do this is by changing your build output path (probably just for src/main/java and src/main/resources) to the WEB-INF/classes directory in your runtime WAR. This works, but it is a bit hacky. Alternatively, you can convert your project into a Dynamic Web Project in Eclipse for Java EE, which provides automatic refresh-on-change behavior out of the box. It also creates a staging WAR directory by default so you don't have to use the exploded WAR under /target. If you're interested in this approach, I can send you detailed instructions (which will also appear in our FAQs after 1.3 launch). Keith On Fri, Mar 12, 2010 at 8:19 AM, andreas <[email protected]>wrote: > Hi Keith, > > we are happy to test the preview version. > > We are using Maven and the gwt-maven-project layout for our projects. > We loved the dependency management and also clear code structure > coming along with Maven but ran in the same problem mentioned a lot > before: we could not get Google Eclipse Plugin run with our projects. > > The first workaround was to use the gwt:run goal, which actually works > fine and forget about GEP. > > Now I still wanted to find out if we can use that nice web application > run configuration of GEP again with the preview release. So I > installed it and set the "war/" folder to "src/main/webapp" and tried > to run our project as a web application. > > It did not work and we got the error "project may need to be > (re)compiled". I figured out that the launch configuration was missing > all the generated js-files. When they are located in "src/main/webapp" > it launches the web application, but apparently using the generated js- > files. No changes to the java code are reflected upon refresh. > > Am I missing something in the setup process of the GEP preview > version? > > On 4 Mrz., 01:25, Keith Platfoot <[email protected]> wrote: > > Hi everyone, > > > > Last month, I announced some of the changes we had planned for the 1.3 > > version of the Google Plugin for Eclipse. To recap, this release is > focused > > on making life easier for developers using GWT/App Engine alongside > > third-party tools, including Maven and Eclipse for Java EE. In my post, I > > promised we'd let you download a preview of 1.3 to get some hands-on > testing > > of the new features and provide us with your feedback before the official > > release. > > > > I'm happy to announce that the time has come. An early preview of 1.3 is > now > > available for download at the following URLs: > > > > http://dl.google.com/eclipse/plugin/3.5/zips/com.google.gdt.eclipse.s... > > > > http://dl.google.com/eclipse/plugin/3.4/zips/com.google.gdt.eclipse.s... > > > > http://dl.google.com/eclipse/plugin/3.3/zips/com.google.gdt.eclipse.s... > > > > Note: Ensure that your version of Eclipse has Eclipse's Web Standard > Tools > > (WST) installed before installing the plugin. WST can be installed by > > navigating to the Software Installation section, and selecting the the > > appropriate WST feature from the update site for your version of Eclipse. > > The update sites and feature names are provided below: > > > > - 3.5 (Galileo): Galileo > Web, XML, and Java EE Development > Eclipse > > Web Developer Tools > > - 3.4 (Ganymede): Ganymede Update Site > Web and Java EE Development > > > Web Developer Tools > > - 3.3 (Europa): Europa Discovery Site > Web and JEE Development > Web > > Standard Tools Project > > > > This is a preview build, so the usual caveats and warnings apply: it is > not > > officially supported, and we recommend using a clean installation of > Eclipse > > and a new workspace. Also, we're distributing this preview as a zip file > so > > be sure to follow the instructions on our Installing the Google Plugin > for > > Eclipse from zip files page ( > http://code.google.com/eclipse/docs/install-from-zip.html). > > > > *Known Issues* > > > > - If you change launch configuration settings in the Server or GWT > tab, > > you'll need to switch to the Arguments tab before clicking Apply or > > Run/Debug. This will be fixed in the final release. > > > > That being said, we are very interested in your experience with this new > > release, which we hope will allow the Google plugin to interoperate much > > better with alternative project structures and third-party tools. The > > tentative 1.3 release notes are as follows: > > > > Enhancements > > > > - Configurable WAR directory to allow better integration with Eclipse > for > > Java EE <http://www.eclipse.org/downloads/moreinfo/jee.php> and > projects > > built with Maven <http://maven.apache.org/> > > - 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< > http://code.google.com/p/google-web-toolkit/issues/detail?id=3583>: > > Google Eclipse Plugin configuration is too strict > > - GWT Issue 3592< > http://code.google.com/p/google-web-toolkit/issues/detail?id=3592>: > > Eclipse plugin to add 'cache forever' configuration for new 'GWT + App > > Engine' projects > > - GWT Issue 3902< > http://code.google.com/p/google-web-toolkit/issues/detail?id=3902>: > > Allow users to configure the severity of problems reported by the > eclipse > > plugin > > - App Engine Issue > > 1515<http://code.google.com/p/googleappengine/issues/detail?id=1515>: > > Eclipse plugin requires fixed location for war directory > > - App Engine Issue > > 2115<http://code.google.com/p/googleappengine/issues/detail?id=2115>: > > Using the @PersistenceAware annotation puts the Eclipse Enhancer in an > > Infinite Loop > > - App Engine Issue > > 1941<http://code.google.com/p/googleappengine/issues/detail?id=1941>: > > Plugin fails to enhance dependent classes on source level changes > > > > For a complete list of fixed issues, see the GWT issue > > tracker< > http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=label...> > > and App Engine issue > > tracker< > http://code.google.com/p/googleappengine/issues/list?can=1&q=label:GP...> > > . > > > > We encourage all interested developers to take the preview build for a > spin, > > and let us know what you think. We'll do everything possible to > incorporate > > your feedback before the final release, slated for later this month. > 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]<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.
