-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: No message from the Maven's stderr in the sam output logs #502
Labels
Comments
usmanovbf
added
the
stage/needs-triage
Automatically applied to new issues and PRs, indicating they haven't been looked at.
label
May 12, 2023
usmanovbf
changed the title
Bug: No stderr info from maven in the sam output logs
Bug: No message from the Maven's stderr in the sam output logs
May 12, 2023
Thanks for raising this issue! I think we need to log the stderr from Maven in here https:/aws/aws-lambda-builders/blob/develop/aws_lambda_builders/workflows/java_maven/maven.py#LL31C67-L31C67 We are happy to review the change if you would like to raise a PR. |
mndeveci
added
area/workflow/java_maven
area/build
and removed
stage/needs-triage
Automatically applied to new issues and PRs, indicating they haven't been looked at.
labels
May 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description:
I am trying to execute
MAVEN_OPTS="-DskipTests=true" sam build --debug --cached
and getting the error with no maven error message - it is empty but appears in the depths of the aws-lambda-builders librarySteps to reproduce:
Execute the
$ MAVEN_OPTS="-DskipTests=true" sam build --debug --cached
Observed result:
Expected result:
Get the non-empty error message from Maven which should be retrieved from the stderr variable on the aws_lambda_builders/workflows/java_maven/maven.py:49 line
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: SAM CLI, version 1.82.0The text was updated successfully, but these errors were encountered: