move to sbt 1. don't support or publish for 0.13 anymore #50
Conversation
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
| this first commit doesn't have any code changes yet, just build changes. setting a baseline. |
This was referenced Feb 16, 2019
Closed
Closed
No need to add an sbt plugin release resolver, re-set the bintray settings (those are the defaults), and upgrade to the sbt 1.2+ way of defining an sbt plugin.
Also avoid sbt's sensitive .value linter.
| GTG for me (if it goes green). |
SethTisue changed the title | thank you Dale, that's a big timesaver |
| gah, I targeted the wrong branch. I'll fix it with force-pushes EDIT: done. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 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.
fixes #32