Mercurial > dive4elements > river
comparison gwt-client/README.txt @ 5838:5aa05a7a34b7
Rename modules to more fitting names.
author | Sascha L. Teichmann <teichmann@intevation.de> |
---|---|
date | Thu, 25 Apr 2013 15:23:37 +0200 |
parents | flys-client/README.txt@4e8be5e7855f |
children |
comparison
equal
deleted
inserted
replaced
5837:d9901a08d0a6 | 5838:5aa05a7a34b7 |
---|---|
1 --- Generated by GWT WebAppCreator --- | |
2 | |
3 Congratulations, you've successfully generated a starter project! What next? | |
4 | |
5 -- Option A: Import your project into Eclipse (recommended) -- | |
6 | |
7 If you use Eclipse, you can simply import the generated project into Eclipse. | |
8 We've tested against Eclipse 3.4 and 3.5. Later versions will likely also | |
9 work, earlier versions may not. | |
10 | |
11 If the directory containing this file does not have a .classpath or .project | |
12 file, generate them by running 'ant eclipse.generate' | |
13 | |
14 In Eclipse, go to the File menu and choose: | |
15 | |
16 File -> Import... -> Existing Projects into Workspace | |
17 | |
18 Browse to the directory containing this file, | |
19 select "FLYS". | |
20 | |
21 Be sure to uncheck "Copy projects into workspace" if it is checked. | |
22 | |
23 Click Finish. | |
24 | |
25 You can now browse the project in Eclipse. | |
26 | |
27 To launch your web app in GWT development mode, go to the Run menu and choose: | |
28 | |
29 Run -> Open Debug Dialog... | |
30 | |
31 Under Java Application, you should find a launch configuration | |
32 named "FLYS". Select and click "Debug". | |
33 | |
34 You can now use the built-in debugger to debug your web app in development mode. | |
35 | |
36 If you supplied the junit path when invoking webAppCreator, you should see | |
37 launch configurations for running your tests in development and production | |
38 mode. | |
39 | |
40 -- Option B: Build from the command line with Ant -- | |
41 | |
42 If you prefer to work from the command line, you can use Ant to build your | |
43 project. (http://ant.apache.org/) Ant uses the generated 'build.xml' file | |
44 which describes exactly how to build your project. This file has been tested | |
45 to work against Ant 1.7.1. The following assumes 'ant' is on your command | |
46 line path. | |
47 | |
48 To run development mode, just type 'ant devmode'. | |
49 | |
50 To compile your project for deployment, just type 'ant'. | |
51 | |
52 To compile and also bundle into a .war file, type 'ant war'. | |
53 | |
54 If you supplied the junit path when invoking webAppCreator, you can type 'ant | |
55 test' to run tests in development and production mode. | |
56 | |
57 For a full listing of other targets, type 'ant -p'. | |
58 | |
59 -- Option C: Using another IDE -- | |
60 | |
61 GWT projects can be run in other IDEs as well, but will require some manual | |
62 setup. If you go this route, be sure to: | |
63 | |
64 * Have your IDE build .class files into 'war/WEB-INF/classes'. | |
65 * Add gwt-user.jar and gwt-dev.jar to your project build path. | |
66 * When creating a launch configuration, add a classpath entry for your 'src' | |
67 folder (this is somewhat unusual but GWT needs access to your source files). | |
68 | |
69 If you get stuck, try to mimic what the Ant 'build.xml' would do. | |
70 | |
71 -- Option D: Using Maven -- | |
72 | |
73 If you have generated your project with the option '-maven', you have a 'pom.xml' | |
74 file ready to use. Assuming you have 'maven2' installed in your system, 'mvn' is | |
75 in your path, and you have access to maven repositories, you should be able to run: | |
76 | |
77 mvn clean # delete temporary stuff | |
78 mvn test # run all the tests (gwt and junit) | |
79 mvn gwt:run # run development mode | |
80 mvn gwt:compile # compile to javascript | |
81 mvn package # generate a .war package ready to deploy | |
82 | |
83 For more information about other available goals, read maven and gwt-maven-plugin | |
84 documentation (http://maven.apache.org, http://mojo.codehaus.org/gwt-maven-plugin) |