Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

sbt new triggers batch mode warning #3097

Closed
jastice opened this issue Apr 12, 2017 · 0 comments
Closed

sbt new triggers batch mode warning #3097

jastice opened this issue Apr 12, 2017 · 0 comments
Assignees
@dwijnand
Labels
Bug Regression
Milestone
0.13.16

Comments

@jastice
Copy link
Contributor

jastice commented Apr 12, 2017

steps

with sbt 0.13.15

> sbt new
[warn] Executing in batch mode.
[warn]   For better performance, hit [ENTER] to switch to interactive mode, or
[warn]   consider launching sbt without any commands, or explicitly passing 'shell'

problem

[warn]

expectation

no warning :)
@dwijnand dwijnand self-assigned this Apr 12, 2017
@dwijnand dwijnand added this to the 0.13.16 milestone Apr 12, 2017
dwijnand added a commit to dwijnand/sbt that referenced this issue Apr 13, 2017
@dwijnand
Exclude "new" from interactive mode warning
60b56c5 
Fixes sbt#3097
dwijnand added a commit to dwijnand/sbt that referenced this issue Apr 13, 2017
@dwijnand
Exclude "new" from interactive mode warning
3b94bec 
Fixes sbt#3097
dwijnand added a commit to dwijnand/sbt that referenced this issue Apr 27, 2017
@dwijnand
Exclude "new" from startup messages
2ee0b3c 
Fixes sbt#3097
@dwijnand dwijnand mentioned this issue Apr 27, 2017
Merged
eed3si9n pushed a commit to eed3si9n/sbt that referenced this issue May 27, 2017
@dwijnand @eed3si9n
Notify users about shell only if compile is present
b54c0ff 
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 sbt#3091
Fixes sbt#3097
@eed3si9n eed3si9n mentioned this issue May 27, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dwijnand dwijnand

Labels
Bug Regression
Projects
None yet
Milestone
0.13.16
Development

No branches or pull requests
2 participants
@dwijnand @jastice