[jbosstools-issues] [JBoss JIRA] (JBIDE-11236) gwt-kitchensink not working when deployed from within JBT
[
https://issues.jboss.org/browse/JBIDE-11236?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-11236:
---------------------------------------
OOME after 4 or 5 builds would have to be caused by a huge memory leak (>100MB) and, if
it would exist, it would be easily reproduced.
However, it can't be reproduced with or without
<runOnIncremental>false</runOnIncremental>.
note, even with that running its only one step that gets removed.
Using the workaround I described, this project example runs as any other project example
(Run As>Run On Server).
By adding '<runOnIncremental>false</runOnIncremental>', the
gwt.compile operation won't be executed on every Save operation.
gwt-kitchensink not working when deployed from within JBT
---------------------------------------------------------
Key: JBIDE-11236
URL: https://issues.jboss.org/browse/JBIDE-11236
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 3.3.0.Beta1
Environment: JBT 3.3.0.Beta1e on eclipseEE indigo SR2
Fedora 16
Oracle java 1.7.0_02-b13 64b
Reporter: Radim Hopp
Assignee: Fred Bricon
Fix For: 3.3.0.Beta1
Attachments: gwt-kitchensink.png
GWT Web Project is not working, when deployed from within JBDS or JBT (using steps
described in README.md).
When deployed, only header, footed and the right "Find out more" panel is
shown.
When deployed from command line using `mvn package` -> `mvn jboss-as:deploy`
everything is working as expected.
--
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