Possibly bind gwt:compile to the 'prepare-package' phase by default in 'war'
projects (maven 2.1)
-------------------------------------------------------------------------------------------------
Key: MGWT-62
URL: http://jira.codehaus.org/browse/MGWT-62
Project: Maven 2.x GWT Plugin
Issue Type: Improvement
Affects Versions: 1.1
Reporter: Mark Renouf
Priority: Minor
The gwt:compile goal used to be bound to the 'compile' phase, and it was
changed to the 'process-classes' phase. This allowed running mvn:compile to
compile java source without triggering the gwt compiler uneccessarily.
Maven 2.1 introduces the 'process-package' phase. This seems like a more ideal
default phase for gwt:compile within a WAR project. JS compilation is not
needed by any intermediate phases. GWTUnitTest does it's own compilation, as
well as HostedMode, etc. The only time GWT compiler should be automatically
invoked is just prior to packaging.
In a jar package project, it should remain unbound (as I beleive it is now?).
I'm not sure if this is possible to do conditionally for only 2.1.x, but it
would be nice.
Alternatively, this is easy to accomplish in your project manually, so if this
can't be changed it should be documented under best practices somewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
