-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add powershell scripts #21158
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
base: main
Are you sure you want to change the base?
Add powershell scripts #21158
Conversation
This has been decided to be included in 3.6.0 |
Perhaps some others shared my misconception that |
@SethTisue there's a strange bootstrapping issue of baking in the default scala version, and providing an offline classpath , otherwise we'd have to build scala-cli from source in scala3 ci |
c442eaa
to
a7a27cd
Compare
38da491
to
563db30
Compare
$_QUIET = $true | ||
} | ||
"-colors" { | ||
$_COLORS = $true |
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.
you're basically swallowing this setting without passing it on, same with $_QUIET, I understand the bat file did that too for compat - but why bother setting the variable
@@ -0,0 +1,9 @@ | |||
function Scala-GetScalaCLIBinaryName { | |||
if ($PSVersionTable.PSEdition -eq "Core") { | |||
return 'scala-cli' |
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.
The .NET core still runs on Windows, does this work still?
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.
Ah, good catch. That means I also have to change the Get-JavaClasspathSeparator
function. let me do it right now.
563db30
to
66b5168
Compare
@@ -0,0 +1,9 @@ | |||
function Get-ScalaCLIBinaryName { | |||
if ($IsWindows) { |
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.
This now requires PowerShell >= 6.0
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.
Which released in 2023, is that too new?
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.
2018: https://github.com/PowerShell/PowerShell/releases/tag/v6.0.0
is that too new?
Mmmh, the issue with this is that some scripts might not work on some machines without installing pwsh >= 6.0
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.
oh ok, the blog you linked says written 2023, so my bad
What's the status of these changes? What's still missing before we're be able to merge and release in 3.6.0? |
We will not merge it for 3.6.0 (maybe in a few months but it's too soon). Sorry, I forgit to mention it on the PR ! |
No description provided.