[
http://jira.codehaus.org/browse/MGWT-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224087#action_224087
]
nicolas de loof commented on MGWT-62:
-------------------------------------
2.1 is minimal release to support prepare-package
Many user don't use it, not because they don't want to upgrade, but because
they can't (entreprise rules, ...).
We have no reason to make the plugin unavailable to such users just to go on
with maven releases. If this was my goal I would have set maven 3 as
prerequisite :P
> 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
> Assignee: nicolas de loof
> Priority: Minor
> Fix For: 1.3
>
> Original Estimate: 10 minutes
> Remaining Estimate: 10 minutes
>
> 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
