Templates with multiple @JsModule fails when they are in random order

[manolo]

When flow computes the template content using the stats.json file it gets the source of the first @JsModule annotation in the class

For instance this fails because @vaadin/vaadin-grid/src/vaadin-grid-column-group.js is taken:

@Tag("templated-columns")
@HtmlImport("frontend://bower_components/vaadin-grid/src/vaadin-grid-column-group.html")
@HtmlImport("src/templated-columns.html")
@JsModule("@vaadin/vaadin-grid/src/vaadin-grid-column-group.js")
@JsModule("src/templated-columns.js")
public class TemplatedColumnsPage extends PolymerTemplate<TemplateModel> {

Otherwise this works taking src/templated-columns.jscontent

@JsModule("src/templated-columns.js")
@Tag("templated-columns")
@HtmlImport("frontend://bower_components/vaadin-grid/src/vaadin-grid-column-group.html")
@HtmlImport("src/templated-columns.html")
@JsModule("src/templated-columns.js")
@JsModule("@vaadin/vaadin-grid/src/vaadin-grid-column-group.js")
public class TemplatedColumnsPage extends PolymerTemplate<TemplateModel> {

[ujoni]

Acceptance criteria

• Users can put @JsModule annotations in any order
• The annotation's file name needs to match the name provided by @Tag annotation
  • @JsModule("src/templated-columns.js") + @Tag("templated-columns")
  • If this is not a convention in P3, documentation needs to be updated to highlight this requirement