luke
/
sbt
mirror of https://github.com/sbt/sbt.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
sbt/notes/0.13.16/tweak-new-startup-messages....

37 lines
1.1 KiB
Markdown
Raw Normal View History

Notify users about shell only if compile is present This is a change in strategy. The motivation is the need to find a good balance between: + informing the uninformed that would benefit from this information, & + not spamming the already informed Making it dependent on "compile" being present in remainingCommands will probably make it trigger for, for example, Maven users who are used to running "mvn compile" and always run "sbt compile", and who therefore are unneccesarily suffering terribly slow compile speeds by starting up the jvm and sbt every time. Fixes #3091 Fixes #3097
2017-04-27 14:03:34 +02:00
### Improvements
- Improves the new startup messages. See below.
### Bug fixes
- Fixes the new startup messages. See below.
### Improvements and bug fixes to the new startup messages
The two new startup messages introduced in sbt 0.13.15 are:
+ when writing out `sbt.version` for build reproducability, and
+ when informing the user sbt shell for the performance improvement
When writing out `sbt.version` the messaging now:
+ correctly uses a logger rather than println
+ honours the log level set, for instance, by `--error`
+ never runs when sbt "new" is being run
When informing the user about sbt shell the messaging now:
+ is a 1 line message, rather than 3
+ is at info level, rather than warn level
+ can be suppressed with `suppressSbtShellNotification := false`
+ only triggers when "compile" is being run
+ never shows when sbt "new" is being run
[#3091][]/[#3097][]/[#3147][] by [@dwijnand][]
[#3091]: https://github.com/sbt/sbt/issues/3091
[#3097]: https://github.com/sbt/sbt/issues/3097
[#3147]: https://github.com/sbt/sbt/pull/3147
[@dwijnand]: https://github.com/dwijnand