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

Update Mod Infra #25

Closed
wants to merge 4 commits into from
Closed

Update Mod Infra #25

wants to merge 4 commits into from

Conversation

Jugbot
Copy link

@Jugbot Jugbot commented May 13, 2024

As mentioned in #22

This PR simply copies the repo style from https://github.com/FabricMC/fabric-language-kotlin

Admins will need to configure the GH secrets for this repo (and test GH actions)

This was a pretty brain-dead operation so apologies for large PR

@Jugbot Jugbot changed the title Update Mod Update Mod Infra May 13, 2024
@@ -0,0 +1,3 @@
{
"org.scala-lang:scala3-library_3": "3.4.1"
Copy link
Member

Choose a reason for hiding this comment

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

There's only scala-library_3 to include? if so there's no reason for separate JSON. Just use the scala_version.txt.

Copy link
Author

Choose a reason for hiding this comment

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

I wasn't sure why kotlin needed so many dependencies. Maybe scala needs more dependencies for it to work? I haven't actually set up a scala mod yet (lol) but I'm trying that out now so maybe I will find something that needs to be added.

Copy link
Member

Choose a reason for hiding this comment

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

Well, it includes some common library that I'd argue should've been in the standard library.

On second thought, it's fine to do it this way, would make it easier if we do decide to include more modules.

@@ -0,0 +1,3 @@
{
"org.scala-lang:scala3-library_3": "3.4.1"

Choose a reason for hiding this comment

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

I don't think you should use a non-LTS version of Scala unless you can ensure that all versions of Scala (Scala3) can be released once.

Scala has a very unique compilation and loading mechanism, to the point where each revision in Scala2 is not compatible with each other.

The Long-term compatibility plans for Scala 3 figured out that:

The Scala 3 version that you are using to compile your code should be treated the same way as any library dependency in your project. You shouldn’t be afraid of updating it. Bumping the patch version (e.g. 3.1.2 -> 3.1.3) is a no-brainer. Bumping the minor version (e.g. 3.1.3 -> 3.2.0) requires the same considerations as changing the minor version of any other dependency, yet is generally advisable.
You should not cross-compile between Scala 3 versions.

So I think that choose LTS version of Scala3 will be better.

What about Scala2? Let it go, it's time to vanish.

@Jugbot
Copy link
Author

Jugbot commented Jun 26, 2024

Just FYI I moved on to using https://github.com/Kotori316/SLP-fabric since it seems way more mature as a project.
I will not be updating this PR but of course others are free to make their own PR from these changes.

@Jugbot Jugbot closed this Jun 26, 2024
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.

3 participants