Re: UiBinder problem on WidgetBasedUi.ui.xml when building GWT from source

268 views
Skip to first unread message

Thomas Broyer

unread,
Jan 18, 2013, 2:05:53 PM1/18/13
to google-web-tool...@googlegroups.com
I believe this is a bug in the Google Plugin for Eclipse; you can simply ignore it (and/or report it in the GPE issue tracker).

Absolute paths weren't accepted in ui:style until recently in GWT: see http://code.google.com/p/google-web-toolkit/issues/detail?id=7230


On Friday, January 18, 2013 6:18:50 PM UTC+1, n.gia...@gmail.com wrote:
Title says it all. I've set up an Eclipse workspace as explained here. After building the workspace I get this error:

Description Resource Path Location Type
CSS file com/google/gwt/uibinder/test/client/Menu.css is missing WidgetBasedUi.ui.xml /gwt-user/core/test/com/google/gwt/uibinder/test/client line 110 Google Web Toolkit UiBinder Problem

And this is the corresponding snippet in WidgetBasedUi.ui.xml

<ui:style field='myStyle' src='WidgetBasedUi.css com/google/gwt/uibinder/test/client/Menu.css'
  type='com.google.gwt.uibinder.test.client.WidgetBasedUi.Style'>
  .menuBar {
    font-family: sans-serif;
  }
</ui:style>

When removing the package prefix from Menu.css, the problem goes away. Any ideas why this is happening?

n.gia...@gmail.com

unread,
Jan 19, 2013, 2:57:59 PM1/19/13
to google-web-tool...@googlegroups.com
Thanks for your reply Thomas. Preparing a bug report for GPE. Bit puzzled though cause according to 7230 absolute paths should start with a '/', whereas in this case it's 'com/google/gwt/uibinder/test/client/Menu.css' without the leading '/'.

Thomas Broyer

unread,
Jan 19, 2013, 5:19:54 PM1/19/13
to google-web-tool...@googlegroups.com


On Saturday, January 19, 2013 8:57:59 PM UTC+1, n.gia...@gmail.com wrote:
Thanks for your reply Thomas. Preparing a bug report for GPE. Bit puzzled though cause according to 7230 absolute paths should start with a '/', whereas in this case it's 'com/google/gwt/uibinder/test/client/Menu.css' without the leading '/'.

CssResource's @Source uses the value first as a relative path and then if necessary as an absolute path, the idea is to have the same behavior for ui:style (which does the same check before generating a @Source to have the error, if any, thrown closer to what the developer wrote: pointing at the <ui:style>, not the generated @Source)

Michael Prentice

unread,
Jun 6, 2014, 1:16:20 AM6/6/14
to google-web-tool...@googlegroups.com
It looks like this isn't fixed and there wasn't a bug report filed against the GWT or GPE issue tracker. I've opened up issue 286 to track this. I may also try to fix it ;)
Reply all
Reply to author
Forward
0 new messages