Description

We're trying to achieve the following workflow for the user inside Eclipse/ GPE / JBoss Tools:

create project

execute Google > GWT Compile

Run As > Run On Server

browse the application

When a gwt maven project is detected, GPE sets the GWT compilation output directory to target/<artifactId>-<version>/. So ultimately we could automatically mark that folder as deployable for WTP and pretty much achieve that ideal workflow.
Until this is done automatically, we can do it manually. Here's a slightly more complex workflow :

Create a new GWT Project from JBoss Central

Right-click on project > Google > GWT compile

Add the Kitchensink module

Click on Compile. Upon completion, a target/<artifactId>-<version> folder is created

Fred Bricon
added a comment - 14/Mar/12 6:44 PM Current manual adding of target folder in deployment assembly is brittle since the next "Maven > Update project configuration" will remove it. That's why we want to automate that part.
This issue may be an upstream issue, i.e. GPE issue, but again, needs to be investigated.