Qlik Talend Studio environment flagged with spring-core-5.3.33.jar and how to use spring-core-6.1.14.jar instead

Lusemar_Oliveira — Tue, 10 Jun 2025 08:28:53 GMT

This article provides step-by-step instructions to ensure your Talend Studio environment no longer uses the flagged spring-core-5.3.33.jar file and instead uses the updated spring-core-6.1.14.jar. It also explains how to verify your job builds are free of the old JAR.

Steps to remove the flagged JAR and confirm the update

These steps are only necessary in cases where Qlik Talend Studio did not remove the old jar when applying the relevant patch (2025-02 or newer).

Verify the Updated JAR in Qlik Talend Studio:
1. Open Qlik Talend Studio
2. Go to the Modules view
3. Search for spring-core
4. Confirm that spring-core-6.1.14.jar is installed and marked as active
Remove the Old JAR from Your Studio Environment

Once you’ve confirmed the new version is active, you can remove the old JAR:
1. Navigate to the following example path (adjust accordingly if your installation directory differs):
  
  C:\TalendStudio8_install\studio\configuration\.m2\repository\org\springframework\spring-core\5.3.33.jar
2. Delete spring-core-5.3.33.jar from this location
  Create a backup copy of the JAR before deletion, in case you need to restore it later.
Check your Job Builds

When you build a job in Qlik Talend Studio, all required JAR files are packaged into a ZIP archive.
1. Locate the lib folder inside the archive
2. Check if spring-core-5.3.33.jar is present
  - If not present: No further action is needed
  - If present: Rebuild the job using your patched (2025-02) version or newer of Qlik Talend Studio to ensure only the updated JAR is included
Restart Qlik Talend Studio to ensure all updates take effect

Additional Notes

Qlik Talend Studio may re-download JARs from a shared repository (such as Nexus) if configured. If you use a shared repository, ensure the old JAR is also removed or blocked there to prevent re-import.
For projects using version control or shared resources, coordinate with your team to avoid accidental reintroduction of the old JAR.

Troubleshooting

If the old JAR reappears after deletion, check if your project is configured to pull dependencies from a shared repository. Remove or block the flagged JAR in that repository as well.
If you encounter errors after removing the JAR, confirm that no jobs or custom code still reference the old version.

Environment

Qlik Talend Studio

article Qlik Talend Studio environment flagged with spring-core-5.3.33.jar and how to use spring-core-6.1.14.jar instead in Official Support Articles

Qlik Talend Studio environment flagged with spring-core-5.3.33.jar and how to use spring-core-6.1.14.jar instead

Steps to remove the flagged JAR and confirm the update

Additional Notes

Troubleshooting

Environment