-
Notifications
You must be signed in to change notification settings - Fork 4
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
Gradle 4.4 issues #11
Comments
I will take a look. The thing about Gradle and plugins is that any plugin dependency gets put on your local class path while locally developing and tramples your compile and testCompile targets. I will likely need to shade the AWS sdk via the shadow plugin when I build this plugin so that there are no transitive dependency issues like the ones you are seeing. I will try to test things out and get the shadow plugin integrated as soon as I can. |
Just an update some things broke just from upgrading Gradle, I am still trying to find time to look into this more. The solution most likely is to get everything working with the latest Gradle, then use https://github.com/johnrengelman/shadow to shade the AWS deps. Feel free to make a PR if you are pressed for time, or else I will get to this when I can. When I say things broke I mean in this build from the gradle upgrade PR: https://travis-ci.org/fieldju/gradle-aws-sam-deployer-plugin/builds/376912344?utm_source=github_status&utm_medium=notification the source sets appear to be messed up and the integration tests are not running. |
Will not run when using gradle 4.4 -- various class-not-found issues at runtime wrt AWS STS module.
I attempted to build and run local copy -- needed to change groovy version and aws sdk verison and was able to build,
but get similar class/not/found error:
The text was updated successfully, but these errors were encountered: