Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gradle project failed when the frontend folder is in the project root #18859

Closed
Tracked by #5012
ZheSun88 opened this issue Mar 1, 2024 · 0 comments · Fixed by #18862
Closed
Tracked by #5012

gradle project failed when the frontend folder is in the project root #18859

ZheSun88 opened this issue Mar 1, 2024 · 0 comments · Fixed by #18862

Comments

@ZheSun88
Copy link
Contributor

ZheSun88 commented Mar 1, 2024

Description of the bug

platform snapshot build failed with following error.

Execution failed for task ':vaadinBuildFrontend'. org.gradle.internal.UncheckedException: com.vaadin.flow.server.ExecutionFailedException: Discovered @Theme annotation with theme name 'gradle-test', but could not find the theme directory in the project or available as a jar dependency. Check if you forgot to create the folder under '/opt/agent/work/6776dee9e21843c0/vaadin-platform-gradle-test/./src/main/frontend/themes' or have mistyped the theme or folder name for 'gradle-test'.

based on the commit message, old project should still work after this change.

Expected behavior

project still work

Minimal reproducible example

https://bender.vaadin.com/buildConfiguration/VaadinPlatform_TestReleasePlatformSnapshotToMavenVaadinPrerelease/509911?expandBuildProblemsSection=true&hideProblemsFromDependencies=false&hideTestsFromDependencies=false

Versions

  • Vaadin / Flow version: 24.4-SNAPSHOT
  • Java version:
  • OS version:
  • Browser version (if applicable):
  • Application Server (if applicable):
  • IDE (if applicable):
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant