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
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.
The text was updated successfully, but these errors were encountered:
Currently the Gradle plugin hardcodes dependencies from
resolve
task toclasses
,compileJava
,compileTestJava
, andtestClasses
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'sclasspath
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.The text was updated successfully, but these errors were encountered: