If I clone a project to test something locally, I don't want to be hassled by a spurious java version check when I publish-local.
Maybe the check could warn instead of erroring for publish-local.
The use case is that requiring Java 6 (for some projects) is especially tiresome. Not all of my machines even have jdk 6 installed, so not even the tiresome PATH=tojdk6/bin:$PATH sbt suffices.
Best solution would be for the build to tell me that normally java 6 is required; I see you have java 6 installed, shall I use that? or, you don't have 6 but you have 7, is that OK for publishing locally?
I think I saw sbt work that way on an episode of Star Trek.
If I clone a project to test something locally, I don't want to be hassled by a spurious java version check when I
publish-local.Maybe the check could warn instead of erroring for
publish-local.The use case is that requiring Java 6 (for some projects) is especially tiresome. Not all of my machines even have jdk 6 installed, so not even the tiresome
PATH=tojdk6/bin:$PATH sbtsuffices.Best solution would be for the build to tell me that normally java 6 is required; I see you have java 6 installed, shall I use that? or, you don't have 6 but you have 7, is that OK for publishing locally?
I think I saw sbt work that way on an episode of Star Trek.