2 Answers
- Newest
- Most votes
- Most comments
0
The following processes are performed in the PowerShell script.
- (If
root-CA.crt
file does not exist) Obtain root CA - (If
aws-iot-device-sdk-java
directory does not exist) Get aws-iot-device-sdk-java from GitHub and build it - connect to AWS IoT Core
In my environment, the tests performed in step 2 of the build procedure fail, so the required modules were not created.
I changed the PowerShell script so that the test is skipped.
mvn install --% -Dgpg.skip=true
to
mvn install --% -Dgpg.skip=true -Dmaven.test.skip=true
After removing the aws-iot-device-sdk-java directory, I re-ran the PowerShell script and the module was correctly generated and connected to AWS IoT Core.
answered 2 years ago
0
I faced the same issue today in ubuntu ec2 instance. The issue turns out that in start.sh, we have the following commands which did not get executed
# install AWS Device SDK for Java if not already installed
if [ ! -d ./aws-iot-device-sdk-java-v2 ]; then
printf "\nInstalling AWS SDK...\n"
git clone https://github.com/aws/aws-iot-device-sdk-java-v2.git --recursive
cd aws-iot-device-sdk-java-v2
mvn versions:use-latest-versions -Dincludes="software.amazon.awssdk.crt*"
mvn clean install -Dmaven.test.skip=true
cd ..
fi
I did these steps manually once and after that, it worked.
answered a year ago
Relevant content
- asked 2 years ago
- asked a year ago
- asked 3 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
Thanks for this tip. I saw the test errors but assumed they could safely be ignored. That is not the case. I added -Dmaven.test.skip=true to the mvn install line but it didn't immediately solve the issue. I had to delete the existing directory and rerun the script so it would download everything fresh and then it started working.