To reproduce, run mvn package for vaadin-button-flow, and see that target/vaadin-button-flow-demo.jar doesn't contain the image vaadin-logo.svg that is used in the demo.

Because of this the demos that use static resources are broken in vaadin.com:
https://vaadin.com/components/vaadin-button/java-examples (missing image)
https://vaadin.com/components/vaadin-icons/java-examples (missing css-file)

Doclint is currently disabled in the flow-component-base and we thus end up with a lot of broken JavaDocs in our component documentation.

Don't know why it is disabled originally, might be because we automatically generate broken JavaDocs (see e.g. vaadin/vaadin-text-field-flow#123 ), apparently from our web component docs.

We should turn doclint on, disable it in projects that has broken docs and preferrably fix docs one by one.

• make a 1.0 branch of the stable release version
  • make branch protected
  • enable validation build, sonar, cla-assistant, etc. for the branch
• update master version to be 1.1-SNAPSHOT
  • the master branch should still have the validation build it has now (!)
  • make sure there is a 1.1-SNAPSHOT available for the component
• The readme should be updated (for both branches) with the branching scheme.

now we are having all the flow components as submodule to this project. it would be better to document the instructions on how to add, update, etc, when there are some changes on individual components.

Wait for #159 to be included.
Changes 2.0.0...master

As based on vaadin/vaadin-button-flow#92, make it happen for all the components:

• Checkbox
• ComboBox
• ContextMenu
• DatePicker
• Dialog
• FormLayout
• Grid
• Icons
• IronList
• ListBox
• Notification
• OrderedLayout
• ProgressBar
• RadioButton
• SplitLayout
• Tabs
• TextField
• TimePicker
• Upload

Select component will be already made with the new structure so don't bother with that.

We will decide based on button refactoring whether or not we will pick these changes to the V12 and V10 branches of the components too.

If you have an OSGi service which is registered declaratively (via @Component annotation) then to be able to properly registered in runtime OSGi related functionality generates OSGI-INF folder with xml descriptor inside it.
This descriptor is declared in META-INF .

But the resulting jar file for some reason doesn't include OSGI-INF folder at all.
As a result the manifest is broken and service is not registered at startup.

Taking this HTML Examples page as example:

The demo categories are shown in the side menu, under the HTML Examples item.

As for Java Examples, the categories are shown as a header for each page:

In order to Vaadin.com to show the categories as links in the side menu, a special demos.json file needs to be exported for each demo. Here is the file for the Grid demo, for example.

vaadin-element-mixin should be new major
Components webjars currently in beta version have stable versions released already