Assuming you're on jdk8, I might have had a similar issue in the past. It was specific to my local machine since our pipelines were running fine.  Then realized that a system update had reset some env variables and my java home was reset to jdk11 which was subsequently getting picked up by mvnThe te...