| rchandia@google.com | 96dc36b | 2011-09-09 17:31:05 +0000 | [diff] [blame] | 1 | push-gwt.sh packages and deploys GWT to a local or remote Maven |
| 2 | repository |
| 3 | |
| 4 | To build GWT from trunk and deploy to your local repo: |
| 5 | |
| 6 | > cd trunk |
| 7 | > ant clean dist-dev |
| 8 | > maven/push-gwt.sh |
| 9 | |
| 10 | Follow the prompts to set the GWT version # and path to the |
| 11 | distribution ZIP (it will automatically find it in build/dist if |
| 12 | you've just built it). By default, the script deploys to your local |
| 13 | Maven repo. |
| 14 | |
| 15 | To deploy to a remote repo: |
| 16 | |
| 17 | Set GWT_MAVEN_REPO_URL and GWT_MAVEN_REPO_ID as noted in the |
| 18 | script. If the remote repo requires a username and password, define |
| 19 | the repo in your ~/.m2/settings.xml as below and set GWT_MAVEN_REPO_ID |
| 20 | = server id. In this example, GWT_MAVEN_REPO_ID would be "sonatype". |
| 21 | |
| 22 | > cd trunk |
| 23 | > ant clean dist # must be dist, not dist-dev, to generate Javadocs |
| 24 | > maven/push-gwt.sh |
| 25 | |
| 26 | ~/.m2/settings.xml: |
| 27 | <settings> |
| 28 | <localRepository>${env.M2_REPO}</localRepository> |
| 29 | <servers> |
| 30 | <server> |
| 31 | <id>sonatype</id> |
| 32 | <username>sonatype_username</username> |
| 33 | <password>sonatype_password</password> |
| 34 | </server> |
| 35 | </servers> |
| 36 | </settings> |
| 37 | |
| 38 | If the remote repo requires jar signing as does Sonatype (Maven |
| 39 | Central), set up GPG on your local machine then enter the passphrase |
| 40 | when prompted. When deploying locally, you can enter a passphrase to |
| 41 | sign the jars for testing or press Enter to skip signing altogether. |
