It seems that there are some inconsistency in the ways web apps are
created. There are primary two ways to create an application:
1) Running
./webAppCreator -out myProject -junit /path/to/junit-4.8.1.jar
com.foo.myproject.MyProject
This creates:
- build.xml
- a skeleton unittest
- a bunch of .launch files
- a certain kind of .project-file
However, when importing this project into eclipse, the gwt-
plugin's "compile" button does not work (the popup claims that my
project is not a GWT project). Also, when following the instructions
in README.txt, a separate GWT-development mode window is launched when
running in debug-mode, and the the compiler progress output is not
seen in any eclipse windows.
2) Create the app from eclipse with the google eclipse plugin.
This creates no build.xml, no skeleton unittest, no .launch-files
and another kind of .project-file than above. However, the red compile
button now works out-of-the-box and the compiler progress output can
be seen in eclipse.
This makes me wonder:
a) Why is there such a difference when creating new apps in these
ways? Aren't both methods handled by webAppCreator in the end?
b) How can I make the compile-button work if creating the app with
method 1)?
c) How do I prevent the GWT development mode window from spawning, and
get an in-eclipse developer mode instead as in case 2).
d) As the build.xml get non-trivial over time, how do I make eclipse
compile using a target in build.xml instead of calling the compiler
directly?
Thanks!
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
