-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Be friendly to SBT plugins that also use URLHandlerRegistry.setDefault #183
Conversation
Add a missing string interp
fix incorrect eviction warning message
add Java 9 test
Other plugins (for example: https://github.com/frugalmechanic/fm-sbt-s3-resolver) also make use of the URLHandlerRegistry.setDefault mechanism to register handlers for other protocols (e.g. "s3"). This change makes it so that SBT will only register the http/https protocols and will preserve any other protocol handlers that have already been registered.
The validator has checked the following projects against Scala 2.12,
✅ The result is: SUCCESS |
I've now tested this fix and it resolves the conflict with fm-sbt-s3-resolver. Here is what I did:
So from my standpoint everything looks good! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent work, thank you @tpunder!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution!
I'm retargeting this to 1.0.x branch so we can include this in sbt 1.0.x. |
After merging it was discovered that there was a bug in sbt [1] preventing `sbt publish` from working. This reverts the changes and updates until this bug is fixed and a new sbt release published. [1] sbt/librarymanagement#183
After merging it was discovered that there was a bug in sbt [1] preventing `sbt publish` from working. This reverts the changes and updates until this bug is fixed and a new sbt release published. [1] sbt/librarymanagement#183
After merging it was discovered that there was a bug in sbt [1] preventing `sbt publish` from working. This reverts the changes and updates until this bug is fixed and a new sbt release published. [1] sbt/librarymanagement#183
This adds a Docker container to run locally for development and for testing, as well as updates various dependencies to latest versions, and moves to CircleCI for testing and publishing. This commit differs from the prior commits by using sbt 1.0.4 which fixes a problem with `sbt publish`. See: sbt/librarymanagement#183
This adds a Docker container to run locally for development and for testing, as well as updates various dependencies to latest versions, and moves to CircleCI for testing and publishing. This commit differs from the prior commits by using sbt 1.0.4 which fixes a problem with `sbt publish`. See: sbt/librarymanagement#183
Other plugins (for example: https://github.com/frugalmechanic/fm-sbt-s3-resolver)
also make use of the URLHandlerRegistry.setDefault mechanism to register handlers
for other protocols (e.g. "s3"). This change makes it so that SBT will only
register the http/https protocols and will preserve any other protocol handlers
that have already been registered.
NOTE: This has now been tested and fixes #175