Re: LicenseFinder and Ruby 3.1

63 views
Skip to first unread message

Adam Milligan

unread,
Feb 7, 2022, 3:02:08 PM2/7/22
to license...@googlegroups.com
Is LicenseFinder still actively maintained?  I very much hope so, because it's important and there aren't any other tools I know of doing anything similar.

The current release of LicenseFinder doesn't run on Ruby 3.1, as outlined in this GitHub issue: https://github.com/pivotal/LicenseFinder/issues/841.  There's a PR that fixes the issue (https://github.com/pivotal/LicenseFinder/pull/857).

I have no doubt that there are people who would be happy to help keep LicenseFinder maintained, given the opportunity.  If the project is in need of maintainers, please reach out.

For the moment, this is the one thing blocking a number of projects from upgrading to Ruby 3.1.  I expect a lot of people would really appreciate a release with the aforementioned fix.

Thanks,
Adam
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted

Jason Smith

unread,
Feb 16, 2022, 9:33:45 AM2/16/22
to license-finder
Hi Adam,

Yes, LicenseFinder is still being maintained, but there is only one developer working on it and related projects.

We have seen one PR that added Ruby 3.0.3 support for testing. However, when we merged it in the tests failed to run due to a code crash. We need to update the tests to support Ruby 3.0.x and 3.1.x. We spent some time investigating to see if the the test needed simple changes, but it appears it needs deeper investigation. So we had to roll back those changes.

We need to find someone who can invest some time to add support for Ruby 3.0.x and 3.1.x for the tests and potentially code changes as well.

That said, there is a PR https://github.com/pivotal/LicenseFinder/pull/877 that was merged in which should allow LF to run on Ruby 3.1.0, though not all LF functionality were tested.

Regards,
Jason

Adam Milligan

unread,
Mar 7, 2022, 3:10:38 PM3/7/22
to license-finder
Thank you for the 7.0 release.  I just updated the gem and ruby 3.1 is a go.
Reply all
Reply to author
Forward
0 new messages