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.

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

Getting started description is outdated #1551

Open
Mikhail42 opened this issue Aug 21, 2023 · 5 comments
Open

Getting started description is outdated #1551

Mikhail42 opened this issue Aug 21, 2023 · 5 comments

Comments

@Mikhail42
Copy link

Expected behaviour

addSbtPlugin("com.github.sbt" % "sbt-native-packager" % "1.9.4")

Actual behaviour

addSbtPlugin("com.typesafe.sbt" % "sbt-native-packager" % "x.y.z")

Information

@raboof
Copy link
Contributor

raboof commented Aug 24, 2023

I just ran into this as well. It seems the documentation at https://www.scala-sbt.org/sbt-native-packager/ is outdated, but the documentation at https://sbt-native-packager.readthedocs.io/en/stable/ is up-to-date.

I don't quite understand where https://www.scala-sbt.org/sbt-native-packager/ is coming from, though: I don't see it referenced in https://github.com/sbt/website or https://github.com/sbt/sbt.github.com

@olaf-otto
Copy link

Same here, took me 20 minutes to find the groupid was changed - looks like at least gettingstarted.rst is not published to scala-sbt org as expected.

@raboof
Copy link
Contributor

raboof commented Sep 7, 2023

ok, so apparently it rolls up the pages from https://github.com/sbt/sbt-native-packager/tree/gh-pages - so I guess we should either replace that branch with redirects, delete it entirely, or make sure it's up-to-date. Any preference?

@SethTisue
Copy link
Member

duplicate of #1504 , I think?

@Mikhail42
Copy link
Author

replace that branch with redirects

ok, so apparently it rolls up the pages from https://github.com/sbt/sbt-native-packager/tree/gh-pages - so I guess we should either replace that branch with redirects, delete it entirely, or make sure it's up-to-date. Any preference?

Redirect to the correct page is fine. No need to duplicate info twice, but deleting entirely may be an option, I think google will return more correct pages after that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants