[jbosstools-issues] [JBoss JIRA] (JBIDE-16334) GWT WAR directory is not set properly in Eclipse Google (GWT) plug-in

[Slawa Giterman (JIRA)]

Slawa Giterman created JBIDE-16334:
--------------------------------------

             Summary: GWT WAR directory is not set properly in Eclipse Google (GWT) plug-in
                 Key: JBIDE-16334
                 URL: https://issues.jboss.org/browse/JBIDE-16334
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: gwt
    Affects Versions: 4.1.0.Final
         Environment: Eclipse Kepler
m2e 1.2
m2e-wtp 1.0.1
Google Plugin for Eclipse 3.4.2
JBoss Maven GWT Configurator 1.5.4
            Reporter: Slawa Giterman


Hello,

I use Eclipse Kepler, m2e 1.2, m2e-wtp 1.0.1, Google Plugin for Eclipse 3.4.2 and JBoss Maven GWT Configurator 1.5.4.

My project uses not default warSourceDirectory in Maven pom.xml (<warSourceDirectory>${basedir}/WebContent</warSourceDirectory>).

The problem is that after each Maven -> Update Project action, GWT WAR directory in Eclipse (Project -> context menu -> Google -> Web Toolkit Settings -> Web Application -> WAR directory) is set to default Maven value "src/main/webapp" and not to the value of warSourceDirectory from pom.xml.

It seems that WAR Directory value is read from file <ECLIPSE_PROJECT>/.settings/com.google.gdt.eclipse.core.prefs, property warSrcDir. This file has also another property, lastWarOutDir which tells Google GWT Plugin where to compile the GWT code (this issue was solved in JBIDE-11224)

Current content of com.google.gdt.eclipse.core.prefs after Maven -> Update Project: 
lastWarOutDir=/applicationserver/WebContent
warSrcDir=src/main/webapp

So, the question is, is it possible to set value of warSrcDir to the same value as lastWarOutDir so that Eclipse does not show error "WAR source directory /applicationserver/src/main/webapp is missing" after each update?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira