maven-2: debug goal launches the gwt compilation also in version 2.0-RC1

[GoogleCodeExporter]

Environment:
I am using the com.totsp.gwt:maven-googlewebtoolkit2-plugin plugin to
manage my gwt project in Maven 2 build. I am using Maven 2.0.9 in Windows
XP under Java 5.

Problem described from the user point of view:
When I launch the gwt-mave:debug goal, the gwt compilation process is
launched again, which is quite annoying, as it is a time consuming process.

The reason of the problem:
The gwt-maven:debug goal executes the install lifecycle phase. This phase
execution has been introduced in the latest version (2.0-RC1). In the older
versions (up to 2.0-beta26) the gwt:debug goal was tied to the compile
lifecycle phase, which was a better case, as the gwt:compile is executed
just in the process-classes lifecycle phase.

Required fix:
Please use the compile "executePhase" instead of the current install phase
for the gwt-maven:debug goal.

Original issue reported on code.google.com by gabriel....@gmail.com on 8 Jun 2009 at 10:23

[GoogleCodeExporter]

Possible workaround:

Use a separate pom.xml file or a Maven profile, where the gwt-maven:compile 
goal is
not bind (not mentioned in the executions section of the plugin config), when 
you to
launch gwt-maven:debug

Original comment by gabriel....@gmail.com on 8 Jun 2009 at 10:31

[GoogleCodeExporter]

There have been several discussions about this in the group, the change in RC1 
was
intentional, but will be changed back (actually that will be changed back and 
new
goals that use the other phases will be created, again, intentionally).

Original comment by charlie....@gmail.com on 15 Jun 2009 at 7:34

• Changed state: Invalid