Closed stbischof closed 3 years ago
Thank you, reproduced on github.com/vaadin/base-starter-gradle v14; simply run ./gradlew --debug
.
The bug is present in the ReflectionsClassFinder
: it doesn't configure the Reflections library properly to only process .class
files. That class comes from Vaadin 14 and so the bug is present upstream. However, the same bug can not be reproduced with Maven plugin even if running with -X
(probably slf4j is missing on classpath and thus the Reflections library logs nothing). That leads me to believe that upstream will not fix this issue.
The ReflectionsClassFinder
has been copied out of Vaadin for Gradle plugin 0.17+ anyways; proposed solution is to copy out the class for Gradle plugin 0.14 and patch it locally.
Thank you, the fix will now be present in a future release of both 14.x (0.14.4.4 or higher) and master (0.18.0.2 or higher).
The fix is to configure ConfigurationBuilder
to only consider *.class
files as follows:
setInputsFilter { it!!.endsWith(".class") && !it.endsWith("module-info.class") } // only scan .class files: https://github.com/vaadin/vaadin-gradle-plugin/issues/99
Reopening since the new Vaadin 20 plugin will have the same issue.
Reported upstream as https://github.com/vaadin/flow/issues/10304
Upstream bug has been fixed in Vaadin 20; however it has not been fixed in Vaadin 14. Therefore I'm leaving this ticket open.
This ticket/PR has been released with platform 21.0.0.alpha8. For prerelease versions, it will be included in its final version.
This ticket/PR has been released with platform 20.0.4. For prerelease versions, it will be included in its final version.
Desktop (please complete the following information):
Describe the bug ReflectionsClassFinder should only scan class files. at the moment there is to much useless log output
To Reproduce .gradle clean build --debug
Expected behavior just scan class files