Skip to content

SOLR-15854: Upgrade semver library to fix versioning constraint bugs in the PackageManager. #515

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

Merged
merged 6 commits into from
Oct 15, 2022

Conversation

HoustonPutman
Copy link
Contributor

@HoustonPutman HoustonPutman commented Jan 11, 2022

@madrob
Copy link
Contributor

madrob commented Jan 11, 2022

This is kind of a pain, but I’d like to see the commits split into a clean fork and then our changes separately. Also, I don’t think we repackage the files, see org.noggit

Copy link
Contributor

@janhoy janhoy left a comment

Choose a reason for hiding this comment

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

I looked forever too without finding a good, maintained library. I checked the forks etc. Also checked a few Kotlin libs but they tend to have less features.

I really don't like forking that amount of code into the project, it will for sure rot in here.

@janhoy
Copy link
Contributor

janhoy commented Jan 11, 2022

There are already 11 contributors to https://github.com/vdurmont/semver4j. Have you tried contacting them? Perhspa if we submit a PR for vdurmont/semver4j#48 and ping a few of the devs, we can help trigger a new release? Two years old can also mean that it is mature and don't need that many updates...

@epugh
Copy link
Contributor

epugh commented Jan 12, 2022

Maybe for an adjacent library, just having a fixed version that lives as someone's personal fork in Github would also be okay? Versus bringing in this code to the Solr project itself.

Github makes it too easy to get lots of forks that all end up vaguely unmaintained, and I wish it encouraged a cluster of forks like what we see for semver to somehow come back together to a single maintained approach. Oh wait... community over code ;-)

@HoustonPutman
Copy link
Contributor Author

Completely agree with both of you that not forking would be the best path forward. It's hard company-policy-wise for me to move forward with either of those options, but I would appreciate either of you taking it up!

@janhoy
Copy link
Contributor

janhoy commented Jan 14, 2022

I'll not veto the code copy, if you clearly mark it and open, say, a blocker JIRA for 10.0 or something to replace it with something that is maintained...

@risdenk
Copy link
Contributor

risdenk commented Oct 14, 2022

Looks like this was fixed and forked - https://github.com/semver4j/semver4j potentially?

@risdenk risdenk mentioned this pull request Oct 15, 2022
@risdenk
Copy link
Contributor

risdenk commented Oct 15, 2022

I updated this PR with my changes. I realized I didn't need a new PR since I was able to merge main and then use semver4j.

I need to fix a few things still solr/CHANGES.txt and maybe some other minor things, but overall this is ready to go.

@sonatype-lift
Copy link

sonatype-lift bot commented Oct 15, 2022

⚠️ 314 God Classes were detected by Lift in this project. Visit the Lift web console for more details.

Copy link
Contributor

@janhoy janhoy left a comment

Choose a reason for hiding this comment

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

Cool, looks good. Fingers crossed that this gets maintained. GitHub projects cold learn a lot form ASF wrt adding committers and caring about project community health.

@risdenk risdenk changed the title SOLR-15910: Fork semver4j library to fix semver bugs. SOLR-15854: Upgrade semver library to fix versioning constraint bugs in the PackageManager. Oct 15, 2022
@risdenk risdenk self-assigned this Oct 15, 2022
@risdenk risdenk merged commit 7515cd5 into apache:main Oct 15, 2022
risdenk added a commit that referenced this pull request Oct 15, 2022
cpoerschke added a commit to cpoerschke/solr that referenced this pull request Oct 19, 2022
cpoerschke added a commit that referenced this pull request Oct 19, 2022
asfgit pushed a commit that referenced this pull request Oct 19, 2022
@HoustonPutman HoustonPutman deleted the semver-fork branch October 20, 2022 15:19
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.

5 participants