Planning 2.5.0 release

[Thomas Broyer]

Hi all,

GWT 2.5.0 has been released yesterday so it's time to plan the 2.5.0 release of the gwt-maven-plugin too.

I already updated the plugin to use it and deployed a snapshot at https://nexus.codehaus.org/content/groups/snapshots-group/org/codehaus/mojo/gwt-maven-plugin/2.5.0-SNAPSHOT/

There were 3 issues I was initially planning to fix by 2.5.0, but didn't find the time/motivation to do it.

There were a bunch of Pull Requests that needed to be rebased too, so now is the time to do it if you'd like them included in 2.5.0.

I'll look into http://jira.codehaus.org/browse/MGWT-326 this week-end but otherwise would like to release the plugin ASAP (even if it's a straight "copy" of 2.5.0-rc2 except for the updated dependency on GWT) and possibly plan a 2.5.0-1 soon after.

Any thought?

[Thomas Broyer]

On Friday, October 26, 2012 4:44:10 PM UTC+2, Thomas Broyer wrote:

I'll look into http://jira.codehaus.org/browse/MGWT-326 this week-end

Fixed by https://github.com/gwt-maven-plugin/gwt-maven-plugin/commit/29944758ba739f296955a477732acb8fd8e91aee

I specifically didn't include the {{i18n}} goal, because of MGWT-343 (and also because I believe it shouldn't be bound to a phase to begin with). People using {{i18n}} as part of their build will have to add the configuration to their POM, as before (this is better than configuring it as {{<ignore/>}} and have people complain that the files are not generated unless they explicitly run the {{generate-sources}} phase).

I don't know if {{mergewebxml}} and {{resources}} should have a lifecycle mapping metadata (they're bound to the {{process-resources}} phase).

I've deployed a snapshot so please test it and comment back on the issue / reopen it if it needs some more work. 

[Thomas Broyer]

After some testing, I've been forced to revert this change, because of http://jira.codehaus.org/browse/MGWT-315