You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
which is an outdated page that points to the outdated sbt/scala-seed.g8 template, which is an old fork that gives you really old sbt and Scala versions
replace the page with an HTTP redirect to one of those pages
remove the page entirely
looking for references to the old template, we see:
% git grep sbt/scala-seed
src/reference/99-Archive/02-Hello.md:\$ sbt new sbt/scala-seed.g8
src/reference/es/00-Getting-Started/02-sbt-by-example.md:\$ sbt new sbt/scala-seed.g8
src/reference/ja/00-Getting-Started/02-sbt-by-example.md:\$ sbt new sbt/scala-seed.g8
src/reference/ja/99-Archive/02-Hello.md:\$ sbt new sbt/scala-seed.g8
so there's also the translations to worry about.
@eed3si9n I'd be happy to a PR a solution if you give me some guidance on what the appropriate solution is. I'm unsure whether the site infrastructure offers redirects, and I'm uncertain if the page needs to somehow be left in place because it's part of historic sbt 0.13 documentation?
The text was updated successfully, but these errors were encountered:
I am ok with whatever solution. My suggestion probably is direct to sbt-by-example, and then maybe update the page to mention sbt init and/or argument-less sbt new and let the user pick scala/toolkit.local.
on Discord today, a user reported that they googled "scala sbt hello world" and the top hit was https://www.scala-sbt.org/1.x/docs/Hello.html
which is an outdated page that points to the outdated
sbt/scala-seed.g8
template, which is an old fork that gives you really old sbt and Scala versionspossible resolutions:
looking for references to the old template, we see:
so there's also the translations to worry about.
@eed3si9n I'd be happy to a PR a solution if you give me some guidance on what the appropriate solution is. I'm unsure whether the site infrastructure offers redirects, and I'm uncertain if the page needs to somehow be left in place because it's part of historic sbt 0.13 documentation?
The text was updated successfully, but these errors were encountered: