Theme compilation fails to detect Vaadin-Stylesheets definitions from manifests of open projects

[peterl1084]

When developing an add-on with contained SCSS style sheet it's customary to have a separate test UI project through which the add-on is used for testing purposes. It seems as if in case where an add-on project is open in Eclipse together with the test UI project, the Eclipse Vaadin integration fails to detect the MANIFEST.MF from the add-on and then fails adding the appropriate entries to addons.scss file of the test theme.

The above problem does not occur if CLI is used for compiling the project as with this approach a complete JAR is built containing proper manifest. The problem can be worked around also by closing the add-on project in IDE, leaving only the test UI project open. Then the theme compiler finds the appropriate MANIFEST correctly from the JAR within local .m2 repo.

The problem is simply that when a project defining an internal SCSS style sheet is OPEN in IDE, the theme compilation process fails to detect the MANIFEST from this open add-on project and then fails to include it's theme to the actual theme used in the test UI.

Another way to work around this is to completely disable the theme compilation from the plugin's maven targets and initially make it right through CLI.