When i import my own project i get dependency error
I developed a project and it is successful in talend studio
then i build it to deploy it in server environment
but to test if my build is working correctly i import it again in to my project and i get a dependency error while i import and run. how to fix this, can someone help if you are aware about this.
org.talend.commons.exception.LoginException: Cannot complete the install because one or more required items could not be found.
Status ERROR: org.eclipse.equinox.p2.director code=0 Software being installed: Databricks 7.3 LTS 8.0.2.20240111_0921 (org.talend.lite.bd.dbr.73x.feature.feature.group 8.0.2.20240111_0921)
Status ERROR: org.eclipse.equinox.p2.director code=0 Missing requirement for filter properties ~= $0: BigData Core Feature of Talend Studio 8.0.2.20240411_0913 (org.talend.lite.bd.core.feature.feature.group 8.0.2.20240411_0913) requires 'org.eclipse.equinox.p2.iu; org.talend.themes.bigdata 0.0.0' but it could not be found
Status ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency: children=[Status ERROR: org.eclipse.equinox.p2.director code=0 From: Databricks 7.3 LTS 8.0.2.20240111_0921 (org.talend.lite.bd.dbr.73x.feature.feature.group 8.0.2.20240111_0921) Status ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.equinox.p2.iu; org.talend.lite.bd.core.feature.feature.group 0.0.0]
at org.talend.repository.localprovider.model.LocalRepositoryFactory.beforeLogon(LocalRepositoryFactory.java:3434)
at org.talend.core.repository.model.ProxyRepositoryFactory.logOnProject(ProxyRepositoryFactory.java:2180)
at org.talend.repository.RepositoryService$1.run(RepositoryService.java:553)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
Caused by: java.lang.Exception: Cannot complete the install because one or more required items could not be found.
Status ERROR: org.eclipse.equinox.p2.director code=0 Software being installed: Databricks 7.3 LTS 8.0.2.20240111_0921 (org.talend.lite.bd.dbr.73x.feature.feature.group 8.0.2.20240111_0921)
Status ERROR: org.eclipse.equinox.p2.director code=0 Missing requirement for filter properties ~= $0: BigData Core Feature of Talend Studio 8.0.2.20240411_0913 (org.talend.lite.bd.core.feature.feature.group 8.0.2.20240411_0913) requires 'org.eclipse.equinox.p2.iu; org.talend.themes.bigdata 0.0.0' but it could not be found
Status ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency: children=[Status ERROR: org.eclipse.equinox.p2.director code=0 From: Databricks 7.3 LTS 8.0.2.20240111_0921 (org.talend.lite.bd.dbr.73x.feature.feature.group 8.0.2.20240111_0921) Status ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.equinox.p2.iu; org.talend.lite.bd.core.feature.feature.group 0.0.0]
When importing a Talend project, a dependency error typically means that the project references items (jobs, routines, metadata, contexts, libraries) that are not present in the target workspace.
Why this happens
The export archive does not include all referenced items.
The target workspace already has items with the same names but different definitions.
The project was exported from a different Talend version and contains components or dependencies not available in the importing Studio.
Custom routines or external JARs used by the project are not present in the import target.
Recommended resolution
1. Re-export the project including all dependencies When exporting from the source Talend Studio:
Use Export Items
Include all related items (jobs, contexts, routines, metadata, tests)
Make sure to check dependent items in the export wizard
2. Import into a clean workspace
Before import, ensure the target workspace does not contain conflicting items
If necessary, create a fresh workspace and import there first
3. Verify mandatory libraries
If your project uses custom JARs or routines:
Verify they are present in the target Studio via Modules view
Re-add the missing libraries if required
4. Check version compatibility
Projects exported from older/newer versions may require migration
If the source project was from a different Talend version, import may trigger migration steps
After import
Review the Import report to identify unresolved dependencies
Manually add any missing metadata or routines as needed
Clean and rebuild the jobs after import
Note: Talend does not automatically create missing referenced items during import; they must be included or manually recreated.
This is expected behavior when not all dependencies are present in the import archive or workspace.
