Important Notice - Forums is archived
To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.
does order matter in gwt descriptor?
If you use maven to perform operations on your project you may have used:
mvn vaadin:update-widgetset
It examines your classpath and updates your gwt descriptor file (e.g. MyWidgetSet.gwt.xml) with entries for the Add-ons it discovers. However, not sure if it guarantees the proper order of those entries.
For example:
If you have played with the awesome QuickTickets demo you may recall a file called "DashboardWidgetSet.gwt.xml". It comes with the proper entries in the proper order for the add-ons. But if you strip them out and run the vaadin:update-widgetset goal you may get some errors at runtime.
Bad Quicktickets:
<inherits name="com.vaadin.addon.timeline.gwt.TimelineWidgetSet" />
<inherits name="com.vaadin.addon.charts.Widgetset" />
Message:
Widgetset 'com.vaadin.demo.dashboard.DashboardWidgetSet' does not contain
implementation for com.vaadin.addon.timeline.Timeline. Check its component
connector's @Connect mapping, widgetsets GWT module description file and
re-compile your widgetset. In case you have downloaded a vaadin add-on package,
you might want to refer to...
The above "Message" was showing up in each panel on the 'Dashboard' of the QuickTickets demo. After re-ordering [see below] - and recompiling the widgetset all was fixed.
The odd part is that I was unable to reproduce the behavior.
It is unclear why.
Good Quicktickets:
<inherits name="com.vaadin.addon.charts.Widgetset" />
<inherits name="com.vaadin.addon.timeline.gwt.TimelineWidgetSet" />