-
Notifications
You must be signed in to change notification settings - Fork 22
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
Give some love to the project #70
base: main
Are you sure you want to change the base?
Conversation
5880888
to
e8fac8a
Compare
31da365
to
9f3d5db
Compare
8436a51
to
f76d299
Compare
- Remove sbt 1.0.0 support - Update Scala version - Update sbt and sbt plugins - Remove deprecated sbt syntax usages - Update Scalafix and improve its configuration - Install Scala Steward to help us maintain this project - Fix Scalafix issues in code
0581ad3
to
f233a78
Compare
2422fdb
to
d5b3a63
Compare
d5b3a63
to
1d5f26b
Compare
2877c87
to
31b34e0
Compare
31b34e0
to
f8cee7a
Compare
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.
Thanks a lot for taking a look at this @guizmaii. As you pointed out, this repo could use some love, but doesn't really have anyone steering the ship on it anymore. I know for myself I don't use it at all, so there isn't a lot of incentive for me to look at it regularly. If this is something you use, would you be interested in joining the group of maintainers for it? I'll happily give you access.
So I just did an initial run through and left a couple nits. I need to look closer at what is going on with the test failure because locally on mac I'm getting failures where before I don't remember getting them. I'm also on an M1 macbook, which won't even load the old build on main. Let me take a closer look and I'll comment back what I find and we can try to get this across the finish line. Again, thanks for taking a look at this.
O, and regarding dropping the 1.3.x support. I think that's fine, especially if it makes maintenance easier at all. I know a lot of the sbt plugin under the sbt org have been doing the same, so I think it's fine to follow here.
.github/workflows/scala-steward.yml
Outdated
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.
Let's remove this for now. We actually have our own scalameta steward here which we can add this repo to once we get this merged in.
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.
If possible, I'd prefer to keep it as, usually, external Scala Steward instances are making PRs from a fork, which makes it harder (if not impossible) to commit on the branches made by Scala Steward (if we need to fix something on one of the update branches)
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.
It should be fine to switch this. We do the same for all the rest of the scalameta projects. Since the PRs are not on the main branch of the fork, a maintainer of the repo is able to add another commit to it.
RemoveUnused { | ||
imports = false // See https://github.com/scalacenter/scalafix/blob/v0.11.0/docs/rules/OrganizeImports.md#configuration | ||
} |
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.
Super nit, but we are sort of mixing styles with how we have this setting defined and how we have the ones below defined. Can we change this to
RemoveUnused { | |
imports = false // See https://github.com/scalacenter/scalafix/blob/v0.11.0/docs/rules/OrganizeImports.md#configuration | |
} | |
RemoveUnused.imports = false |
Just to be consistent with how we do the DisableSyntax
down below. We can do the same with Disable.ifSynthetic
@@ -42,7 +43,6 @@ lazy val plugin = project | |||
.settings( | |||
moduleName := "sbt-native-image", | |||
sbtPlugin := true, | |||
sbtVersion.in(pluginCrossBuild) := "1.0.0", | |||
crossScalaVersions := List(scala212), |
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.
Is this still needed at all?
Hey @ckipp01, Thanks for your comment and initial review :)
I'm already maintaining/helping to maintain too many things but I'll use this plugin, so yes I'm interested in joining 🙂 |
This also bumps some stuff in the CI, even though we'll rip it out after.
46c4025
to
7f29c8e
Compare
Ah annoying, so I tried to bump to 22.3.0 since I was having issues locally with that, but then I also see that the way it's installed in CI now is with Jabba, which we should just ditch and do what you did with the setup-graal. I was also trying to get things locally to pass on my machine, but things fails since I don't have the I might actually take the CI changes PR that you made and put that on top of this just to ensure we can use a newer Graal version in CI. I might also change up the tests to not fail if Also I hope it's ok that I'm just adding commits on top of this. |
We'll use the org one instead
ec7c920
to
101b85e
Compare
It's completely fine. Thanks for your help, Chris! ❤️
Agreed. I'd like to see everything green but we need to make small steps here.
Go for it 🙂 |
I haven't forgotten about this @guizmaii, just been swamped with other stuff. I will get back to it soon. |
The tests are failing, but as they're also failing on the
main
branch, I'm unsure if I broke something.I tried to fixed the tests but I don't understand why the
agent-test
tests are failingCc @ckipp01 @olafurpg