From: Matti Tahvonen Date: Tue, 15 Dec 2009 15:04:23 +0000 (+0000) Subject: Added debug messages X-Git-Tag: 6.7.0.beta1~2143 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=0dc4aea6969d05184ffde4d88a3c5fa461ce334d;p=vaadin-framework.git Added debug messages svn changeset:10324/svn branch:6.2 --- diff --git a/src/com/vaadin/tools/WidgetsetCompiler.java b/src/com/vaadin/tools/WidgetsetCompiler.java index 4d809a470f..246a461e4b 100644 --- a/src/com/vaadin/tools/WidgetsetCompiler.java +++ b/src/com/vaadin/tools/WidgetsetCompiler.java @@ -6,22 +6,22 @@ import com.vaadin.terminal.gwt.widgetsetutils.WidgetSetBuilder; /** * A wrapper for the GWT 1.6 compiler that runs the compiler in a new thread. - * + * * This allows circumventing a J2SE 5.0 bug (6316197) that prevents setting the * stack size for the main thread. Thus, larger widgetsets can be compiled. - * + * * This class takes the same command line arguments as the * com.google.gwt.dev.GWTCompiler class. The old and deprecated compiler is used * for compatibility with GWT 1.5. - * + * * A typical invocation would use e.g. the following arguments - * + * * "-out WebContent/VAADIN/widgetsets com.vaadin.terminal.gwt.DefaultWidgetSet" - * + * * In addition, larger memory usage settings for the VM should be used, e.g. - * + * * "-Xms256M -Xmx512M -Xss8M" - * + * * The source directory containing widgetset and related classes must be * included in the classpath, as well as the gwt-dev-[platform].jar and other * relevant JARs. @@ -51,8 +51,12 @@ public class WidgetsetCompiler { // TODO expecting this is launched via eclipse WTP // project + System.out + .println("Updating GWT module description file..."); WidgetSetBuilder.updateWidgetSet(wsname); + System.out.println("Done."); + System.out.println("Starting GWT compiler"); System.setProperty("gwt.nowarn.legacy.tools", "true"); Class compilerClass = Class .forName("com.google.gwt.dev.GWTCompiler");