-
Notifications
You must be signed in to change notification settings - Fork 562
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
springboot2 sample not building with maven #336
Comments
Thanks for the report. Looks like SAM is trying to run I'll reach out to the SAM team. |
Hi,
Yes that works - but then „sam deploy“, which works fine, does not lead to a solution for my problem.
After running the deployment and calling the lambda, I still get a classnotfoundexception on the StreamHandler class… I had already built a SpringBoot2 sample myself and ran into this error - also when running sam local.
I was hoping the sample would deliver the solution…
Thanks
Thomas
Am 20.04.2020 um 21:14 schrieb Stefano Buliani <notifications@github.com<mailto:notifications@github.com>>:
Thanks for the report. Looks like SAM is trying to run mvn install. These samples are not meant to be installed, simply packaged. If you run mvn clean package from the sample folder, does it succeed?
I'll reach out to the SAM team.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fawslabs%2Faws-serverless-java-container%2Fissues%2F336%23issuecomment-616753975&data=02%7C01%7C%7Ce338a6037ae940f84ede08d7e55efd0d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637230068433721913&sdata=YtxpK0KmR3Gst9IIVM1wzo60nvuu5kCkiW2CW1n%2BdOQ%3D&reserved=0>, or unsubscribe<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAG2LZYR7H4ZM67LRVA22C5DRNSNHTANCNFSM4MMWG7FA&data=02%7C01%7C%7Ce338a6037ae940f84ede08d7e55efd0d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637230068433731930&sdata=%2BqRn%2Bf9wYTXCsyZYIM3ZKQWadBWwH9tswIikqCha%2FVg%3D&reserved=0>.
|
…SAM CLI's sam build command with maven (clean install) can work to address (#336)
I've pushed a fix to the samples in the master branch that should make |
@thomashoef What are you trying to do? If you just want to unit test your application then you can replicate our tests without going through the CLI emulator |
Also the projects created using archetypes : com.amazonaws.serverless.archetypes and aws-serverless-springboot2-archetype do not work . I got "classnotfoundexception on the StreamHandler. " The part we need to delete from pom is :
Best Regards. |
Thanks @ggokce I'll move your report to a new issue and track it as a bug. Do you want to open it or want me to do it (you won't get notifications if I do it) |
You are welcome... you can do it
26 Eki 2020 Pzt 17:01 tarihinde Stefano Buliani <notifications@github.com>
şunu yazdı:
… Thanks @ggokce <https://github.com/ggokce> I'll move your report to a new
issue and track it as a bug. Do you want to open it or want me to do it
(you won't get notifications if I do it)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#336 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFOEOOM6RTGWX2HBGMXTNDDSMWMLZANCNFSM4MMWG7FA>
.
|
Just also hit this issue with 1.5.2 and added the following to fix it:
|
Currently you will face the same error ("The packaging for this project did not assign a file to the build artifact") if you use the latest aws-serverless-springboot2-archetype. How to reproduce:
|
This should no longer happen with the latest archetype versions >=1.6. Please reopen if you still have problems. |
Just noticed that 253910f only fixed the pet-store samples and not the archetypes. Will commit a different fix that covers both. |
Scenario
I cloned the springboot2 petstore sample.
Expected behavior
sam build builds the project correclty.
Actual behavior
Steps to reproduce
Clone the springboot2 petstore sample.
Run sam build (without having gradle installed / removing the gradle build file)
Full log output
see above.
The text was updated successfully, but these errors were encountered: