-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Task "jandex" up-to-date check passes as long as the jandex.idx exists (and will not rebuild for new source) #24
Comments
(Reproducer added) |
The reproducer is really helpful. 👍 . When I run it:
The I am not an expert, but I think that the problem is that when jandex-gradle-plugin/src/main/groovy/org/kordamp/gradle/plugin/jandex/tasks/JandexTask.groovy Lines 155 to 157 in 8b9f879
My current work-around is to add the folder as additional input for the jandex task:
|
Possible workaround for kordamp/jandex-gradle-plugin#24
🎉 This issue has been resolved in |
Description:
The "jandex" task will build the "jandex.idx" file once, and then appears to never build it again as long as it exists. At initial glance in the source, the "@InputFiles" field appears to be wired up to an empty file collection, which, if I understand Gradle correctly, implies that as long as the output exists, the task will pass the up-to-date check.
The "jandex" task ought to rebuild the "jandex.idx" when the class files that Jandex is indexing have changed.
Reproducer:
https://github.com/jskillin-idt/kordamp-jandex-gradle-plugin-issues-24
Steps to reproduce:
./gradlew build
and observe the "printMethods" task gives the list of methods present insrc/main/java/com/sample/Test.java
./gradlew build
again. Observe the "printMethods" task continues to give the old list of methods, despitesrc/main/java/com/sample/Test.java
having been rewritten with new methods.The text was updated successfully, but these errors were encountered: