Skip to content

AWS Blu Age L3 Workshop - Error on Automation - Execute

0

Hi people.

I'm on the following workshop phase: https://catalog.workshops.aws/aws-blu-age-l3-certification-workshop/en-US/automation/execute

After check the tools installation, I tried to run the execute.xml as Ant, but I got the errors on Console: "Buildfile: D:\PhotonUser\Workshop\workspace\carddemo-automation\execute.xml [taskdef] Could not load definitions from resource net/sf/antcontrib/antcontrib.properties. It could not be found. [taskdef] Could not load definitions from resource net/sf/antcontrib/antlib.xml. It could not be found.

BUILD FAILED D:\PhotonUser\Workshop\workspace\carddemo-automation\execute.xml:10: typedef class aws.bluage.ant.utils.HttpReturn cannot be found using the classloader AntClassLoader[] "

I tried remove the line bellow from execute.xml: <typedef name="httpreturn" classname="aws.bluage.ant.utils.HttpReturn" />

And the error change to: "Buildfile: D:\PhotonUser\Workshop\workspace\carddemo-automation\execute.xml [taskdef] Could not load definitions from resource net/sf/antcontrib/antcontrib.properties. It could not be found. [taskdef] Could not load definitions from resource net/sf/antcontrib/antlib.xml. It could not be found. execute:

BUILD FAILED D:\PhotonUser\Workshop\workspace\carddemo-automation\execute.xml:24: Problem: failed to create task or type for Cause: The name is undefined. Action: Check the spelling. Action: Check that any custom tasks/types have been declared. Action: Check that any <presetdef>/<macrodef> declarations have taken place."

After looking for some information about the taskdef warnings, looks like could be a classpath problem, but I could find the ant-contrib-1.0b3.jar in C:\Work\Programs\ant\lib.

asked 2 years ago316 views

3 Answers
0
Accepted Answer

The errors you're encountering in the AWS Blu Age L3 Workshop during the Automation - Execute phase are likely related to missing dependencies or incorrect configurations. Here are some steps you can try to resolve the issues:

  1. Ensure you're using the correct version of Ant that's compatible with the workshop. The workshop may require a specific version of Ant to work properly.

  2. Verify that the ant-contrib-1.0b3.jar file is correctly placed in the Ant lib directory. While you've found it in C:\Work\Programs\ant\lib, make sure this is the Ant installation that Eclipse is using.

  3. Check your Eclipse configuration to ensure it's pointing to the correct Ant installation. Go to Window > Preferences > Ant > Runtime and verify the Ant Home directory.

  4. The error message suggests that some custom tasks are not being recognized. Make sure all required JAR files for the workshop, especially those containing custom Ant tasks, are present in your project's lib folder or added to the Ant classpath.

  5. Try cleaning and rebuilding your project in Eclipse. Sometimes, this can resolve classpath-related issues.

  6. If the problem persists, you might need to update your execute.xml file. Ensure that all necessary taskdef and typedef declarations are present and correctly configured at the beginning of the file.

  7. Double-check that you have all the required AWS Blu Age libraries and dependencies installed correctly. The error mentioning "aws.bluage.ant.utils.HttpReturn" suggests that some Blu Age-specific libraries might be missing.

If these steps don't resolve the issue, you may need to consult the workshop documentation for specific setup instructions or reach out to the AWS Blu Age support team for further assistance. They might be able to provide you with the exact configuration required for the automation step to work correctly.
Sources
AWS Blu Age L3 workshop - Automation step error | AWS re:Post
Unloading issue during automation process in L3 Workshop | AWS re:Post

answered 2 years ago

0

To answer your question, we require details that are non-public information. Please open a support case with AWS using the following [Link.https://console.aws.amazon.com/support/home#/case/create]

AWS
SUPPORT ENGINEER

answered 2 years ago

0

Fixed mine by checking the Eclipse configuration to ensure its pointing to the correct Ant installation. Go to Window > Preferences > Ant > Runtime and verify the Ant Home directory.

Enter image description here

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.