Closed jwhitlark closed 8 years ago
I don't see why it wouldn't work. Although I only see the full AWS SDK adding 35mb to the uberjar (if I just lein new foo
and add amazonica as a dep and uberjar it.)
"only 35mb" lol ....JVM developers.....
Oops. Thanks, though. It'll still help.
"Assumptions are like dogs. Mine just bit me."
On Nov 25, 2015, at 6:41 AM, Michael Cohen notifications@github.com wrote:
I don't see why it wouldn't work. Although I only see the full AWS SDK adding 35mb to the uberjar (if I just lein new foo and add amazonica as a dep and uberjar it.)
— Reply to this email directly or view it on GitHub.
removed everything but core a1de64567635de83ff463788e595c736eb215420
Beginning in version 1.9.0, the aws sdk is modular, (see http://docs.aws.amazon.com/AWSSdkDocsJava/latest/DeveloperGuide/java-dg-using-maven.html)
Using the following dependencies, I was able to get s3 calls working:
Which will make amazonica much nicer for some of my use cases, (aws lambda jobs, etc.), as it cuts over 115M off the size of the uberjar.
Is there any reason this wouldn't work in all cases? If not, we should add it to the documentation.