Update pom.xml

3 jobs for !204 with smanjunath/resolve_governanceIssues in 1 minute and 41 seconds (queued for 2 seconds)
latest detached
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #635127
osdu-small allowed to fail

00:00:06

 
  Review
failed trigger-trusted-tests #635128
osdu-small

00:01:35

 
  Build
skipped osdu-gcp-helm-charts #635129
osdu-small
 
Name Stage Failure
failed
trigger-trusted-tests Review

Pipeline has been in state 'running' for 2 sec, waiting for completion
Pipeline has been in state 'running' for 13 sec, waiting for completion
Pipeline has been in state 'running' for 23 sec, waiting for completion
Pipeline has been in state 'failed' for 9 sec, waiting for completion
Pipeline completed in state failed in 19 sec
Pipeline status is not 'success', exiting with error status
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
deprecated-aws-include .Pre

Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:14119a10abf4669e8cdbdff324a9f9605d99697215a0d21c360fe8dfa8471bab for alpine:latest with digest alpine@sha256:e1c082e3d3c45cccac829840a25941e679c25d438cc8412c2fa221cf1a824e6a ...
$ echo "$DEPRECATED_MSG"
The AWS includes now support different build environments, which should be specified directly. Consider using: aws-global.yml, and either aws-maven.yml or aws-python.yml
$ /bin/false
Cleaning up file based variables
ERROR: Job failed: exit code 1