Skip to content

Conversation

@GuyIncognito1986
Copy link

No description provided.

GuyIncognito1986 and others added 25 commits October 20, 2018 11:17
…and making this build/work with scala 2.12
…code, tests still broken, but library now builds and we use the correct tasks
…lace, whoever wrote these was a fucking moron
@beloglazov
Copy link
Owner

Thanks for all the changes! I'll start reviewing it soon. Some tests seem to be failing now?

@GuyIncognito1986
Copy link
Author

GuyIncognito1986 commented Nov 15, 2018 via email

@beloglazov
Copy link
Owner

Sorry for not getting back to this earlier. The PR in the current form is too large, and some of the changes are not acceptable, e.g., changing the package / license. I would accept smaller, more targeted PRs with clearer descriptions of what's being done (which would also make it easier and faster to review the changes).


```Scala
libraryDependencies += "com.ibm" %% "couchdb-scala" % "0.7.2"
libraryDependencies += "io.github.guyincognito1986" %% "couchdb-scala" % "1.0.3.1"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol


## Contributors

- Anton Semenov https://github.com/GuyIncognito1986
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cheeky.

@GuyIncognito1986
Copy link
Author

GuyIncognito1986 commented Jan 27, 2019 via email

@giftig
Copy link

giftig commented Jan 27, 2019

You added yourself to the top of the contributor list, above the author, and messed with the licensing information.

As for the maven release, I assume @beloglazov intends to create a release including any patches people contribute. If what you're saying is that the author / IBM aren't maintaining it, why have you even created this PR to the original repo? If you intend to release it separately, no one's stopping you; do it from your fork (it's even namespaced to your fork)

@GuyIncognito1986
Copy link
Author

GuyIncognito1986 commented Jan 27, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants