[mojo-dev] [jira] (MGWT-343) m2eclipse execute of gwt-maven-plugin:i18n causes continuous rebuilds

[Thomas Broyer (JIRA)]

Thomas Broyer commented on MGWT-343 m2eclipse execute of gwt-maven-plugin:i18n causes continuous rebuilds I just tried again. What I experience is that, indeed, each time I go to the generated Messages.java it tells me the file has changed on disk, and refreshes it. What probably happens is Eclipse is recompiling the class when refreshing it (seems logical), which triggers the generate-sources goal again, which generates the file again. I could then understand that if you have "Refresh using native hooks or polling" checked in Window → Preferences → General → Workspace then Eclipse would be continuously refreshing → recompiling → re-trigerring generate-sources. generateAsync checks the files staleness (using their last-modified date) before generating them, and i18n does not, which explains the difference. That being said, if you ask me, i18n is more a tool to help in migrating from or syncing with non-GWT UIs, or initializing a project from mocks from which an I18N team wrote the properties file(s), and shouldn't be used during the build. YMMV. In conclusion: I'm reopening this issue, but won't invest time fixing it personally. Patches are (more than) welcome though.

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

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email