Skip to content
This repository has been archived by the owner on Jan 10, 2019. It is now read-only.

Old Jackson versions break Android Studio. #11

Open
Tukajo opened this issue Apr 27, 2015 · 2 comments
Open

Old Jackson versions break Android Studio. #11

Tukajo opened this issue Apr 27, 2015 · 2 comments

Comments

@Tukajo
Copy link

Tukajo commented Apr 27, 2015

Importing the dependencies of Jackson Core 1.x.x and Jackson Mapper 1.x.x to an Android Studio project causes a "duplicate file" error. And it cannot be built.

Would this be fixed by updating the dynamodb-geo.jar to reference to the latest 2.x.x. Jackson versions?

Here is a link to a related SO post on the topic I made.
http://stackoverflow.com/questions/29886227/java-lang-noclassdeffounderror-when-already-imported-jar-files-to-android-studio

@david-at-aws
Copy link

I don't understand enough about what's going wrong with Jackson 1.x.x in Android Studio to comment on whether upgrading to 2.x.x will fix the issue you're seeing, but if you'd like to put together a pull request upgrading to a newer version of aws-java-sdk that pulls in Jackson 2.x.x I'd be happy to take a look. Presumably as a 2.0.0 release of this library since it won't be binary-backwards-compatible?

Hopefully you've already seen it but and it's not an issue for you, but I'll copy this portion of the Limitations section from the Readme.md just in case: :)

Because Geo Library calls multiple DynamoDB Query requests and processes the results in memory, it is not suitable for mobile device use. You should maintain a Java server, and use the library on the server.

@bsautner
Copy link

👍 on closing this issue. One shouldn't include this library in a mobile app, it should be used server side and the android sdks should be used to call lambda functions that use it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants