Move blockhound dependency in 5.1.x to separate branch

[jzheaux]

Spring Security uses BlockHound to track down blocking issues - it however is not yet GA. As such, it can't be included as a dependency in release artifacts.

To facilitate it's continued usage, it could be moved to a separate git branch that is not a release branch, until BlockHound releases.

An alternative to this task would be to update the release process to remove any milestone dependencies from dependency management before releasing, though this would also mean removing any code that is also dependent on those milestones, which seems cumbersome.

[jzheaux]

Fixed via 404ad9a

[bsideup]

I'm just curious: why do you have testCompile dependencies in the release artifacts?

[jzheaux]

@bsideup, I don't think we're including testCompile dependencies in release artifacts.

When we do release builds, though, we only pull from release repositories. Because of this, any milestone dependency will fail the build since it can't be located.

Or did I misunderstand your question?

[bsideup]

@jzheaux ah, I see. Perhaps you can apply the same "is release" conditional logic to BlockHound then, to not remote it completely?