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

Bumped library versions to compile with Scala 3.1.1 #918

Merged
merged 4 commits into from
Aug 18, 2022

Conversation

hmf
Copy link
Contributor

@hmf hmf commented Mar 16, 2022

I came across the pull request WIP: Support for scala 3.1 #896 and took a stab at it. Apparently the TASTy versions between the 2.13.* and 3.*.* branches needs to be paired correctly. Version 2.13.6 is compatible with 3.0.*; we need at least 2.13.7 for the 3.1.* versions. Cannot recall were I read this.

I have bumped several libraries and the code compiles for all 2.12, 2.13, 3.0 and 3.1 versions. Note that Ammonite has packages compiled for the 2.13.8 branch, however there do not seem to be any cross compilation libraries for 2.13.8. Tests also seem to run correctly.

@hmf hmf mentioned this pull request Mar 17, 2022
@Quafadas
Copy link
Contributor

See also #902... lots of people are hoping for the same :-)!

project/deps.sc Outdated
def scalatags = ivy"com.lihaoyi::scalatags:0.9.4"
def slf4jNop = ivy"org.slf4j:slf4j-nop:1.8.0-beta4"
def scalatags = ivy"com.lihaoyi::scalatags:0.11.1"
def slf4jNop = ivy"org.slf4j:slf4j-nop:2.0.0-alpha6"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is upgrading slf4j to 2.x. Shouldn't we stick to 1.x instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had issue with messages regarding not finding the slf4jNop. Also note that slf4j had a security vulnerability in 2.x but don't think it is this version. Seems to run ok. Is this whats blocking its merge?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to be the latest version in the 1.x series
https://search.maven.org/artifact/org.slf4j/slf4j-nop/1.7.36/jar
I'm guessing here, but maybe it would be for the best to use that, to maintain as broad compatibility as possible. Also not using alpha/beta versions of libraries is good too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. Will have to update and push again.

@hmf
Copy link
Contributor Author

hmf commented Jun 10, 2022

Apologies for the delay.

I have made the slf4j changes and made a new commit (687c73c). I have reviewed the conflicts and changed the .gitignore accordingly. Other changes seem ok. All versions compiled on my machine. BTW, we now have Scala 3.1.2. Maybe we can update to that minor?

 Conflicts:
	modules/scala/scala-interpreter/src/main/scala/almond/ReplApiImpl.scala
	modules/scala/scala-interpreter/src/main/scala/almond/VariableInspectorApiImpl.scala
	project/deps.sc
@alexarchambault
Copy link
Member

Apologies for coming back to this a bit late. I fixed some Scala 3 stuff around the same time in #932. And Scala Steward then bumped to 3.1.3 recently.

@alexarchambault
Copy link
Member

Merging the remaining change, thanks @hmf!

@alexarchambault alexarchambault merged commit 1c7fe15 into almond-sh:main Aug 18, 2022
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

Successfully merging this pull request may close these issues.

4 participants