-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Use sbt-native-packager instead of sbt-pack #20547
Conversation
88a77b7
to
59daf47
Compare
3096410
to
073ef51
Compare
6eeb38f
to
7d59d4f
Compare
7d59d4f
to
70fc581
Compare
In #20547, to be able to build an msi installer, the version needs to have the following pattern `A.B.C.D`. This change should be fine but the release procedure of RC1 will have to take it into account.
61b0d9f
to
880d773
Compare
880d773
to
7c996e5
Compare
Some changes are required in We will also be signing the released msi but we don't have yet a code signing certificate so the necessary changes will also follow in another PR |
project/Build.scala
Outdated
maintainer := "The Scala Programming Language", | ||
packageSummary := s"Scala $dottyVersion", | ||
packageDescription := """Installer for the Scala Programming Language""", | ||
wixProductId := "74ED19C3-74FE-4ABA-AF30-55A06B6322A9", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these GUIDs seem a bit underdocumented - where do they come from?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can add some documentation here
This PR is based on #20351.
The idea is to use
sbt-native-packager
instead ofsbt-pack
since it has the ability to generate.msi
files.[test_msi]