|
||||||||
|
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 |
||||||||
- [mojo-dev] [jira] (MGWT-326) Add/Include m2e configur... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-326) Add/Include m2e con... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-326) Add/Include m2e con... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-326) Add/Include m2e con... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-326) Add/Include m2e con... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-326) Add/Include m2e con... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-326) Add/Include m2e con... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-326) Add/Include m2e con... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-326) Add/Include m2e con... Thomas Broyer (JIRA)

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 / reopen the issue if it needs some more work.