http://gwt-code-reviews.appspot.com/1520810/diff/10020/maven/README.txt File maven/README.txt (right):
http://gwt-code-reviews.appspot.com/1520810/diff/10020/maven/README.txt#newcode10 maven/README.txt:10: build/dist if you've just built it). By default, the script deploys to your local Maven repo. On 2011/09/09 17:59:18, rjrjr wrote:
could you reflow this doc to fit in 100 or 80 chars?
Done. http://gwt-code-reviews.appspot.com/1520810/diff/10020/maven/lib-gwt.sh File maven/lib-gwt.sh (right): http://gwt-code-reviews.appspot.com/1520810/diff/10020/maven/lib-gwt.sh#newcode110 maven/lib-gwt.sh:110: curExpandDir=$jarExpandDir-${i} On 2011/09/09 17:59:18, rjrjr wrote:
So you're still processing files in midstream. I'm worried about
something
unexpected happening here when we're halfway through a canonical push,
leaving
us with a difficult mess to clean up. Seems like you'd be better off
with two
for loops, one for processing and one that does only deploy calls.
Done.
(Does maven give us no way to batch or set up a transaction?)
Not that I know, but the uploads can be restarted and retried as many times as necessary. drfibonacci can probably provide more details on the actual process to follow. http://gwt-code-reviews.appspot.com/1520810/diff/10020/maven/push-gwt.sh File maven/push-gwt.sh (right): http://gwt-code-reviews.appspot.com/1520810/diff/10020/maven/push-gwt.sh#newcode12 maven/push-gwt.sh:12: # GWT_MAVEN_REPO_URL=https://oss.sonatype.org/content/repositories/google-snapshots/ On 2011/09/09 17:59:18, rjrjr wrote:
What will happen if I run this script from the wrong directory?
Done. It now correctly changes to location of push-gwt.sh before sourcing the libs. http://gwt-code-reviews.appspot.com/1520810/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
