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

Mark LTS releases in the pom #19691

Closed
Gedochao opened this issue Feb 14, 2024 · 0 comments · Fixed by #19986
Closed

Mark LTS releases in the pom #19691

Gedochao opened this issue Feb 14, 2024 · 0 comments · Fixed by #19986
Assignees
Labels
itype:meta Issues about process/similar
Milestone

Comments

@Gedochao
Copy link
Contributor

Compiler version

LTS

What's the problem?

There's currently no way to programmatically differentiate LTS compiler releases from others, when using them as a dependency.
https://index.scala-lang.org/lampepfl/dotty/artifacts/scala3-compiler/3.3.2
I'd like to be able to identify what's the latest LTS with coursier, for example.

Expected solution

A simple <versionType>LTS</versionType> property in the pom.xml should do the trick.

Context

Scala CLI currently hardcodes LTS to the latest version in the 3.3.x series (refer to VirtusLab/scala-cli#2709)
When a new LTS comes out, we'll have to manually update that (which is a minor toil, but nonetheless toil one needs to remember about).
I bet other apps may want to programmatically track this as well.

@Gedochao Gedochao added the itype:meta Issues about process/similar label Feb 14, 2024
Kordyjan added a commit that referenced this issue Mar 25, 2024
Closes #19691 

When it is backported to 3.3.x, the string will be changed to "LTS". We
handle version number in a similar manner.
@Kordyjan Kordyjan added this to the 3.4.2 milestone Mar 28, 2024
@Kordyjan Kordyjan modified the milestones: 3.4.2, 3.5.0 May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
itype:meta Issues about process/similar
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants