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
The idea behind this removal is to optimize build time when Gradle clean task is executed, and prevent unconditional execution of tasks installNode, resolvePackageManager, installPackageManager, installFrontend.
Projects using the cleanScript property would have to migrate to one of the following workaround:
Create a custom task to clean the project with a Node.js-based command:
tasks.register<Run[Node|Npm|Pnpm|Yarn]TaskType>("cleanFrontend") {
// Assuming package.json file contains a script named "clean".
args.set("run clean")
// Optionally
dependsOn("installFrontend")
}
Or configure Gradle clean task to remove additional files and/or directories:
tasks.named<Delete>("clean") {
delete(/* additional files or directories */)
}
Assumption is made that few projects actually used the cleanScript property, and would be impacted by such removal.
The text was updated successfully, but these errors were encountered:
The idea behind this removal is to optimize build time when Gradle
clean
task is executed, and prevent unconditional execution of tasksinstallNode
,resolvePackageManager
,installPackageManager
,installFrontend
.Projects using the
cleanScript
property would have to migrate to one of the following workaround:clean
task to remove additional files and/or directories:Assumption is made that few projects actually used the
cleanScript
property, and would be impacted by such removal.The text was updated successfully, but these errors were encountered: