You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 2, 2021. It is now read-only.
The vaadinThemeCompile task will then incorrectly report that the task is up-to-date, which makes the bug more mysterious. The --rerun-tasks helps and makes the task execute and print Found 0 themes, which leads to this bug.
Workaround is to include the sub-project path in the themesDirectory itself, e.g. mythemeproject/src/main/resources/VAADIN/themes.
A fix would be to change rootDir to projectDir in the plugin's Util.groovy:577.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Util.getThemesDirectory() at https://github.com/johndevs/gradle-vaadin-plugin/blob/master/src/main/groovy/com/devsoap/plugin/Util.groovy#L577 roots the
themesDirectory
inproject.rootDir
if the path is relative. That doesn't work well if the theme is built in a sub-project rooted in, say,mythemeproject
dir.The
vaadinThemeCompile
task will then incorrectly report that the task is up-to-date, which makes the bug more mysterious. The--rerun-tasks
helps and makes the task execute and printFound 0 themes
, which leads to this bug.Workaround is to include the sub-project path in the
themesDirectory
itself, e.g.mythemeproject/src/main/resources/VAADIN/themes
.A fix would be to change
rootDir
toprojectDir
in the plugin's Util.groovy:577.The text was updated successfully, but these errors were encountered: