Simplify the releasing of sbt plugin projects via incorporating scripted

[huntc]

Would you consider auto-detecting scripted tests and then including them to save developers writing code like this:

https://github.com/sbt/sbt-digest/pull/12/files#diff-51d4ae50524e97cc109f0ada94e15123R11

This would make using sbt-release for releasing plugins a little smoother. WDYT?

[gseitz]

I've been meaning to split the release process into phases, where each phase is a separate setting and can be modified separately. This would make it easier to modify part of the release process, without having to repeat the whole thing.

In that sense, there would be something like the following snippet, which would make it a lot easier to just add the runScripted to the test phase.

// Warning: pseudo code
val releaseTestPhase = TaskKey[Seq[ReleaseStep]]("release-test-phase")
val releasePublishPhase = TaskKey[Seq[ReleaseStep]]("release-publish-phase")
// imagine more phases here

// ...
val settings = Seq[Setting[_]](
  releaseTestPhase := Seq(runTest),
  releasePublishPhase := Seq(runPublish),
  releaseProcess <<= (releaseTestPhase, releasePublishPhase) map { (tp, pp) => tp ++ pp }
)

Would this help?

[huntc]

Hi @gseitz - that may help, but again something out of the box to recognise plugin development mode and the auto-enablement of scripted would be awesome. The less configuration the better of course. Thanks.