JavaMavenWorkflow fails Required target/classes directory was not produced from 'mvn package'
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 30/100
- Tipo di issue
- Bug
- Chiarezza
- Da chiarire
- Stato di attività
- Ferma
- Stack tecnologico
- aws, java
- Ambito
- build-system, cloud
Direzione di ricerca
Inizia riproducendo sam build --use-container --template-file template.yaml da aws-lambda/get-expenses, quindi esamina aws-lambda/get-expenses/template.yaml, il relativo pom.xml e la directory target/classes generata. Il lavoro è completato quando il workflow Java Maven produce la directory richiesta e la build SAM termina correttamente.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Description:
Steps to reproduce
- Clone repository: git@github.com:francis-pang/expense-tally.git
- Check out branch feature/aws-sam
- Navigate to ./aws-lambda/get-expenses
- Build application via command
sam build --use-container --template-file template.yaml
Observed result:
[INFO] Reactor Summary for expense-tally 49-SNAPSHOT:
[INFO]
[INFO] expense-tally ...................................... SUCCESS [01:40 min]
[INFO] expense-tally-model ................................ SUCCESS [01:03 min]
[INFO] csv-parser ......................................... SUCCESS [ 1.795 s]
[INFO] expense-manager .................................... SUCCESS [ 9.474 s]
[INFO] expense-reconciliator .............................. SUCCESS [ 2.932 s]
[INFO] expense-tally-cli .................................. SUCCESS [01:21 min]
[INFO] aws-lambda ......................................... SUCCESS [ 3.556 s]
[INFO] aws-lambda-get-expenses ............................ SUCCESS [ 0.373 s]
[INFO] aws-lambda-s3-db-file-update ....................... SUCCESS [01:10 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:34 min
[INFO] Finished at: 2020-10-18T06:37:37Z
[INFO] ------------------------------------------------------------------------
JavaMavenWorkflow:MavenBuild succeeded
Running JavaMavenWorkflow:MavenCopyDependency
JavaMavenWorkflow:MavenCopyDependency succeeded
Running JavaMavenWorkflow:MavenCopyArtifacts
JavaMavenWorkflow:MavenCopyArtifacts failed
Traceback (most recent call last):
File "/usr/local/opt/sam-cli/lib64/python3.7/site-packages/aws_lambda_builders/workflow.py", line 269, in run
action.execute()
File "/usr/local/opt/sam-cli/lib64/python3.7/site-packages/aws_lambda_builders/workflows/java_maven/actions.py", line 69, in execute
self._copy_artifacts()
File "/usr/local/opt/sam-cli/lib64/python3.7/site-packages/aws_lambda_builders/workflows/java_maven/actions.py", line 76, in _copy_artifacts
raise ActionFailedError("Required target/classes directory was not produced from 'mvn package'")
aws_lambda_builders.actions.ActionFailedError: Required target/classes directory was not produced from 'mvn package'
Builder workflow failed
Traceback (most recent call last):
File "/usr/local/opt/sam-cli/lib64/python3.7/site-packages/aws_lambda_builders/workflow.py", line 269, in run
action.execute()
File "/usr/local/opt/sam-cli/lib64/python3.7/site-packages/aws_lambda_builders/workflows/java_maven/actions.py", line 69, in execute
self._copy_artifacts()
File "/usr/local/opt/sam-cli/lib64/python3.7/site-packages/aws_lambda_builders/workflows/java_maven/actions.py", line 76, in _copy_artifacts
raise ActionFailedError("Required target/classes directory was not produced from 'mvn package'")
aws_lambda_builders.actions.ActionFailedError: Required target/classes directory was not produced from 'mvn package'
Expected result:
Build is successful after
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
Project directory is as below:
only showing the relevant one, full project directory is at aws-sam branch
.
├── LICENSE
├── README.md
├── aws-lambda
│ ├── get-expenses
│ │ ├── pom.xml
│ │ ├── src
│ │ │ └── main
│ │ │ └── java
│ │ │ └── expense_tally
│ │ │ └── views
│ │ │ └── aws
│ │ │ └── lambda
│ │ │ └── HttpGetExpensesHandler.java
│ │ └── template.yaml
│ ├── pom.xml
│ └── s3-db-file-update
│ ├── pom.xml
│ └── src
│ └── main
│ └── java
│ └── expense_tally
│ └── views
│ └── aws
│ └── lambda
│ └── NewSqlDbFileS3Handler.java
├── docs
│ ├── expenses.yaml
│ └── use-case.txt
├── expense-tally.iml
├── pom.xml
└── sonar-project.properties
Contents of template.yaml:
AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: >
expense-tally Get Discrepant Expenses Function
Globals:
Function:
Timeout: 15
MemorySize: 256
Runtime: java11
Resources:
GetDiscrepantExpensesFunction:
Type: AWS::Serverless::Function # More info about Function Resource: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#awsserverlessfunction
Properties:
Description: 'Retrieve all the mismatching transactions'
CodeUri: ../../
Handler: expense_tally.views.aws.lambda.HttpGetExpensesHandler::handleRequest
Events:
GetDiscrepantExpensesApi:
Type: Api
Properties:
Path: '/getDiscrepantExpenses'
Method: get
Outputs:
GetDiscrepantExpensesFunction:
Description: "Get Discrepant Expenses Function ARN"
Value: !GetAtt GetDiscrepantExpensesFunction.Arn
HelloWorldFunctionIamRole:
Description: "Implicit IAM Role created for Get Discrepant Expenses Function function"
Value: !GetAtt GetDiscrepantExpensesFunction.Arn
- Lingua principale
- Python
- Stelle
- 381
- Fork
- 162
- Merge medio
- 1g 1h
- PR unite (30g)
- 2
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di aws/aws-lambda-builders
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
aws/aws-lambda-builders#925 · 1 reazione ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 64/100
aws/aws-lambda-builders#924 · 1 commento · 1 reazione ·
-
Bug: PythonUvBuilder fails to build app with dependencies on editable installs in the workspace Apertastage/needs-triage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 25/100
aws/aws-lambda-builders#892 ·
-
stage/needs-triage type/feature
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
aws/aws-lambda-builders#839 · 2 commenti · 1 reazione ·
-
area/build contributors/good-first-issue contributors/welcome type/feature
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
aws/aws-lambda-builders#831 · 3 commenti ·
Tutte le issue di aws/aws-lambda-builders
Issue simili
-
agent-ready documentation needs-triage
Difficoltà 1/5 1-3 ore Idoneità per principianti 88/100
-
documentation
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
-
instance instance add
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
searxng/searx-instances#939 · 1 commento ·
-
area-deployment area-integrations triage:bot-seen
Difficoltà 2/5 Mezza giornata Idoneità per principianti 86/100