AWS Blu Age- Dependency problems when importing projects_Execution Backend

Question

when I tried to import the projects to eclipse, during the backend execution task, I got dependency errors for the following projects: 
carddemo-entities
carddemo-service
cerddemo-tools
Although the poms of the two projects carddemo-pom and carddemo-refactoring work very well.
I tried to check the access path of the settings.xml to which they point and it was the right path (same path of the two other projects; carddemo-refactorings and carddemo-pom)
also I tried to update maven but I did not succeed in solving the problem.
![Saisissez la description de l'image ici](/media/postImages/original/IMXQen8e2pTpWedtPURJ17sQ)

Rupesh · Accepted Answer

You have used 4.6.0 version for the code transformation and appstream image is 4.2.0 and that's a mismatch. Use 4.2.0 in blu insights and transform again.

re:Post Agent · Answer

The dependency problems you're experiencing when importing the AWS Blu Age projects into Eclipse are common issues that can occur due to version mismatches or missing dependencies. Here are some steps to address these problems:

1. Version compatibility: Ensure you're using the same version of AWS Blu Age for both generating the modernized code and executing it. The version in your development environment should match the one used to build the modernized code.

2. Access to Blu Age runtime jars: The dependency errors suggest that some required Blu Age runtime libraries are missing. You need to gain access to these runtime jars. Follow the AWS Mainframe Modernization documentation to set up and obtain access to these essential runtime libraries.

3. Maven configuration: Verify that your Maven settings are correctly configured to access the necessary repositories for Blu Age dependencies. While you've checked the settings.xml path, ensure it contains the correct repository information for Blu Age dependencies.

4. Project build path: In Eclipse, double-check the build path for each project (carddemo-entities, carddemo-service, carddemo-tools) and ensure all required Blu Age libraries are properly included.

5. Clean and rebuild: After making these changes, try cleaning your projects and rebuilding them in Eclipse. This can often resolve dependency issues.

6. Version alignment: If you're using AppStream, make sure the version of gapwalk and other Blu Age components in your project matches the version in the AppStream environment.

If these steps don't resolve your issues, you may need to consult the workshop documentation for specific instructions or reach out to the Blu Age support team for further assistance. Remember that having the correct dependencies and versions is crucial for the proper functioning of the Blu Age projects.  
**Sources**  
[Blu age L3 Execution/backend/import project | AWS re:Post](https://repost.aws/questions/QUYyTlsiO1RNqBKIT_dFp64A/blu-age-l3-execution-backend-import-project)  
[AWS BluAge L3 Workshop - IMPORT to Eclipse - Archive for required library not resolved | AWS re:Post](https://repost.aws/questions/QU9Ht8B6xpSuyynDoafodRmg/aws-bluage-l3-workshop-import-to-eclipse-archive-for-required-library-not-resolved)  
[Maven dependency error when importing Blu Age L3 Workshop modernized code | AWS re:Post](https://repost.aws/questions/QUY9Z7KlM_R_mpY8Hl7D5xsg/maven-dependency-error-when-importing-blu-age-l3-workshop-modernized-code)

AWS Blu Age- Dependency problems when importing projects_Execution Backend

Add your answer

Relevant content