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 plugin should not hardcode task dependencies #4367

Open
erdi opened this issue Feb 21, 2023 · 1 comment
Open

Gradle plugin should not hardcode task dependencies #4367

erdi opened this issue Feb 21, 2023 · 1 comment

Comments

@erdi
Copy link

erdi commented Feb 21, 2023

Currently the Gradle plugin hardcodes dependencies from resolve task to classes, compileJava, compileTestJava, and testClasses tasks. There is no need to do any of that because the task dependencies will be inferred by Gradle based on the value of that task's classpath property. In my particular case this prevents me to be able to configure inclusion of the generated Open API specification as a resource of the main source set because it's causing circular task dependencies.

@nbrugger-tgm
Copy link

nbrugger-tgm commented Oct 17, 2024

here is a fix: #4761

disclaimer: i am not an author or maintainer so who knows if this will be merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants