[ https://issues.jboss.org/browse/JBIDE-11236?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-11236: ------------------------------- Attachment: gwt-kitchensink.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11236?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-11236: ---------------------------------------- Assignee: Fred Bricon (was: Max Rydahl Andersen) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11236?page=com.atlassian.jira.plugi... ] Jonathan Fuerth commented on JBIDE-11236: ----------------------------------------- Although it will be too slow to run the GWT compiler every time a java file is saved, I think it would be a really good idea to run the gwt:compile mojo automatically as part of the project import. This would allow new users to Run As -> Run On Server... and see the project working properly out-of-the-box. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11236?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-11236: --------------------------------------- The instructions in the README.md aren't complete. Besides the above mentioned five steps, it is also necessary to do the following: - call mvn package and refresh the project. This has to be repeated manually when the user changes GWT code - start JBoss AS server - update the war argument in the Run>Run Configurations>Arguments tab (remove maven version, 0.0.1-SNAPSHOT usually) The aplication starts in an external browser that requires the GWT plugin. In my opinion, starting the application this way is too complicated. It would be better to add the compile goal and run the project out-of-the-box. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11236?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-11236: --------------------------------------- I can't reproduce the OOME when using - Linux and Windows 32-bit - gwt 2.5.1/2.5.2, m2e 1.0.200 (the versions included in JBT 3.3.0.Beta/JBDS 5.0.0.Beta) - org.jboss.errai.archetypes:kitchesink-quickstart:2.0.Beta3 - the default JBDS JVM settings - incremental and full build - publishing to JBoss AS 7.1.1.GA There is not any memory leak either in m2e or in gwt when building the project with the compile goal. The JBDS memory usage always returns to around 130MB. Maybe you have some other problem in your environment that causes the OOME. BTW, In order the gwt.compile goal not to be called on every Save operation, it is enough to replace the following in the m2e plugin: {code} <action> <execute /> </action> {code} with {code} <action> <execute > <runOnIncremental>false</runOnIncremental> </execute > </action> {code} The gwt:compile operation will be called only when calling a full build (Project>Clean). The user will have to call full build (Project>Clean) whenever he changes the GWT code. Sometimes, he will also have to call Project Refresh. The complete m2e plugin declaration I have tested is the following: {code} <!-- m2e (Maven integration for Eclipse) requires the following configuration --> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId>org.codehaus.mojo</groupId> <artifactId>gwt-maven-plugin</artifactId> <versionRange>[2.3.0,)</versionRange> <goals> <goal>resources</goal> <goal>compile</goal> </goals> </pluginExecutionFilter> <action> <execute > <runOnIncremental>false</runOnIncremental> </execute > </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> </plugin> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11236?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11236: --------------------------------------------- note, even with that running its only one step that gets removed. its still complicated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11236?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-11236: ---------------------------------- Fix Version/s: 3.3.0.CR1 (was: 3.3.0.Beta1) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11236?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-11236. ------------------------------ Fix Version/s: 3.3.0.Beta3 Resolution: Done Verified in JBT 3.3.0.Beta3b -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira