search

sbt / sbt-jshint

Allows jslint to be used from within sbt. Builds on com.typesafe:webdriver in order to execute jslint.js along with the scripts to verify
Other
21 stars 20 forks source link

Bug causing slow startup by SBT #42

Closed bwbecker closed 10 months ago

bwbecker commented 6 years ago

In a clean play-scala-starter-example project (https://github.com/playframework/play-scala-starter-example):

  1. Change build.properties to use sbt 0.13.17.
  2. Add file debug.sbt containing logLevel := Level.Debug to the project directory to enable debugging output from SBT.
  3. Add addSbtPlugin("com.typesafe.sbt" % "sbt-less" % "1.1.2") to plugins.sbt
  4. Run rm -r project/project/ target project/target to get rid of all compiled artifacts
  5. Run sbt | grep ERROR and you see four errors such as CLIENT ERROR: Not Found url=https://repo.typesafe.com/typesafe/ivy-releases/org.webjars.npm/strip-json-comments/
  6. Add addSbtPlugin("com.typesafe.sbt" % "sbt-jshint" % "1.0.6") to plugins.sbt
  7. Remove the compile artifacts again and rerun sbt | grep ERROR. It reports 112 such errors.

Time to launch sbt goes up from 11 seconds to 52 seconds on my recent high-end MacBook Pro when sbt-less and sbt-jshint are included as plugins.

mkurz commented 10 months ago

Looks like this issue was because of slow network or server being slow or a remote repo was not available. Closing for now. I just released version 2.0.0 and all artifacts are hosted on maven central now, so I assume this is fixed. Let me know if you still experience problems.