[
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.
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