LGTM
http://gwt-code-reviews.appspot.com/1604804/diff/1/user/src/com/google/gwt/junit/FakeCssMaker.java
File user/src/com/google/gwt/junit/FakeCssMaker.java (right):
http://gwt-code-reviews.appspot.com/1604804/diff/1/user/src/com/google/gwt/junit/FakeCssMaker.java#newcode2
http://gwt-code-reviews.appspot.com/1604804/diff/1/user/src/com/google/gwt/junit/FakeCssMaker.java
File user/src/com/google/gwt/junit/FakeCssMaker.java (right):
http://gwt-code-reviews.appspot.com/1604804/diff/1/user/src/com/google/gwt/junit/FakeCssMaker.java#newcode44
Right now, it won't make much difference as GWT gets user classes from
the same classpath that GWT classes are loaded from. However, that
leads to conflict for shared code where you want to use a different
version of something than the version GWT itself needs to run. So, in
the future we may
Right now, it won't make much difference as GWT gets user classes from
the same classpath that GWT classes are loaded from. However, that
leads to conflict for shared code where you want to use a different
version of something than the version GWT itself needs to run. So, in
the future we may
On 2011/11/30 20:26:19, jat wrote:
http://gwt-code-reviews.appspot.com/1604804/diff/1/user/src/com/google/gwt/junit/FakeCssMaker.java
File user/src/com/google/gwt/junit/FakeCssMaker.java (right):
On 2011/11/30 21:05:17, jat wrote:
Right now, it won't make much difference as GWT gets user classes from
the same
classpath that GWT classes are loaded from. However, that leads to
conflict for
shared code where you want to use a different version of something
than the
version GWT itself
