Open GoogleCodeExporter opened 8 years ago
Hi,
Can we have any update on this issue ? Let us know , if we are missing out
something
while doing the upgrade.
Original comment by tapas4...@gmail.com
on 21 Feb 2010 at 3:21
Hello,
any Update on this ?
Original comment by tapas4...@gmail.com
on 27 Feb 2010 at 7:14
Any solution for it?
Original comment by yx1984yx@gmail.com
on 1 Apr 2010 at 6:20
Hi,
I am seeing this issue even with GWT 2.0.3 and latest incubator
[gwt-incubator-20100204-r1747.jar].
We are going production with GWT2.0.3 but these compile time warnings are
annoying the build process.
Is there a working around/fix for suppressing these warnings?
GWT moderators can you comment?
Thanks
Sekhar
Is there any work around for this?
Original comment by yempara...@gmail.com
on 10 Jun 2010 at 12:54
i have the same problems... why this is deprecated? and with wich class
replaced? or with wich library?
Original comment by Mkutil@gmail.com
on 24 Jun 2010 at 1:15
Is there any work around to get rid of this problem ?
Original comment by tapas4...@gmail.com
on 25 Jun 2010 at 8:39
I looked at
http://code.google.com/p/google-web-toolkit/source/browse/branches/2.1/user/src/
com/google/gwt/user/client/impl/DocumentRootImpl.java?r=8209
Apparently DocumentRootImpl is deprecated and one should "use the direct
methods provided in {@link Document} instead".
Original comment by jeroen.j...@gmail.com
on 27 Jun 2010 at 3:04
Another programmer with concern for warnings. Is there a way to suppress the
com.google.gwt.user.client.impl.DocumentRootImpl warning perhaps?
(I don't like having to ignore warnings because it causes misses of new
warnings).
Original comment by lynx...@gmail.com
on 28 Sep 2010 at 12:22
Also concerned by this issue. We have been using GlassPanel for some time, it's
always a bit worrying to see a warning like that - but - the GlassPanel is in
the incubator not in the main body of the GWT codebase and as such is subject
to change as needs be.
Original comment by chillysp...@gmail.com
on 27 Oct 2010 at 10:44
Original issue reported on code.google.com by
Tapas.Ad...@gmail.com
on 16 Feb 2010 at 10:04