URLHandlerRegistry conflict with fm-sbt-s3-resolver plugin in SBT 1.0 about librarymanagement HOT 11 CLOSED

Any update on this? This issue has a lot of thumbs up 😞

from librarymanagement.

#183 fixes the problem for me.

from librarymanagement.

This is resolved with SBT 1.0.4! Thanks!

from librarymanagement.

Any news on this issue?

from librarymanagement.

+1 on this issue - rolling back to 0.13.16 fixed the problem for me

from librarymanagement.

I'd love to see a better hook for customizing the URLHandlerRegistry. I'd love to be able to use this to inject kerberos support, but at the moment I can't be confident a custom URLHandler won't get hosed and so am creating a full custom resolver to improve isolation.

from librarymanagement.

This is regretion in SBT 1.0 as we see in tpunder/fm-sbt-s3-resolver#38

from librarymanagement.

Still no news on this? This is invalidating the project https://github.com/frugalmechanic/fm-sbt-s3-resolver ...
I'm also happy to help if needed.

from librarymanagement.

Hey. I've created sbt/sbt#3758 to help track this issue. I've added it to the 1.0.5 milestone, and I hope it can be fixed by then.

If you, @joan38, or anyone wants to help by investigating what the underlying issue is, what possible solutions there might be, and/or submitting a fixing PR that would be great.

Unfortunately I don't have any real information regarding this issue in particular to give at this time.

from librarymanagement.

Thanks @dwijnand for the update and info!

from librarymanagement.

Here is what I'm playing with for fixing this: #183

from librarymanagement.