Cross-compile Scala 2.10 and 2.11#35
Open
cjwebb wants to merge 1 commit into
Open
Conversation
Cross-Compile to 2.11 and 2.10. Also, upgrade dependencies so that 2.11 works, and bump SBT version to latest. * Update ScalaTest dependency, and fix deprecated class usage. * Update Akka dependency, and fix deprecated class usage.
alexanderdean
changed the title
Collaborator
|
Happy to publish when @piotrga gives the word |
Owner
|
fine by me |
Collaborator
|
Hey guys - we're not using this library at Snowplow currently so can't really spare the time to manage the build and publication process. Sorry about that. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cross-Compile to 2.11 and 2.10. Also, upgrade dependencies so that 2.11 works, and bump SBT version to latest.
The automated tests work for me, connecting to my own AWS account. I spent a bit of time making them work with DynamoDB Local, but I think it would make sense to put that in a separate issue/PR... along with making the Travis build use the local version.
This should help solve issue #31