Bommels05/Modrinth
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(app-lib): do not softlock tauri dev when a Gradle build is invoked (#3847)

Browse Source 
An unforeseen consequence of PR #3833 landing was that `tauri dev`
stopped working reliably, getting softlocked when the `app-lib` crate
build script actually needed to build Java scripts: Gradle always
modifies a few files under the `.gradle` directory when run, which get
picked up by Tauri as source code changes that should trigger a rebuild,
but such rebuild triggers Gradle to run and modify those files again ad
infinitum.

This change fixes that by adding such a directory to a documented Tauri
exclusion file, restoring such functionality back.
This commit is contained in:
Alejandro González 2025-06-26 23:46:46 +02:00 committed by GitHub
parent 6f03fae233
commit 03192c1dfd
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
apps/app/.gitignore vendored
View File

@ -1,6 +1,2 @@
# Generated by Cargo
# will have compiled files and executables
/target/
# Generated by tauri, metadata generated at compile time # Generated by tauri, metadata generated at compile time
/gen/ /gen/

3
packages/app-lib/.taurignore Normal file
View File

@ -0,0 +1,3 @@
# State files generated by Gradle on build. If not ignored for Tauri,
# cargo tauri dev gets softlocked due to these files changing for every build
/java/.gradle