This is expected behavior with the GenAI starter template.
GenAI auto-manages Java dependencies, so Studio Pro re-resolves JARs and regenerates vendorlib on every startup. That’s why JARs appear deleted and added again. Committing them does not stop this, and you should not manage vendorlib manually.
A practical fix is to close the project, delete local vendorlib (and userlib if needed), reopen the project, let Studio Pro re-download the JARs, and commit once. If the JARs are not re-downloaded, re-download or reinstall the related Marketplace modules directly so Studio Pro can restore the required libraries.
Bottom line: Studio Pro does this by design to keep dependencies consistent; these JAR changes are mostly noise.
hi,
This is expected behavior and it’s caused by the GenAI Starter template managing vendor libraries automatically.
The GenAI starter uses managed dependencies, and when you open the project, Studio Pro checks and re-aligns the vendored JAR versions (for example upgrading from 2.40.x to 2.41.x). Because these JARs are stored under vendorlib, Studio Pro treats the version alignment as file deletes/adds every time the project is opened.
That’s why:
This is not a Git issue and not something you’re doing wrong.
Option 1 (recommended):
Ignore vendorlib changes when reviewing commits. These files are effectively generated artifacts for this template.
Option 2 (if it really bothers you):
Remove the GenAI starter dependency and manage those JARs yourself — but you’ll lose the benefit of automatic dependency alignment.