AB-xdev
commented
3 months ago @hazendaz
Current state of the project
Backstory: I forked the plugin
- as we required a replacement for our openapi-templates
- after getting no feedback for a few months (I was pretty much sure that the original plugin was dead when we forked it)
- to fix the issues that I reported there
We plan to maintain the fork at least as long as required for us and if there are a lot of users maybe even indefinitely. It's not that hard/much effort to bump a few versions every few weeks/months and do a release periodically (we also have automation for this in here).
PR and issues from the community are also welcome and I will have a look at them from time to time :)
Checklist
What is/are your question(s)?
As we know the original plugin is not getting releases. It may get one today though. But longer term seems original author isn't using it as was the case before. There are some threads over there discussing it today. This fork is certainly in a better spot currently but want to understand if the support will be on this fork if the original is set to archived. My personal main concerns are the same I think with it working on newer maven properly without warnings. And the original broke today with maven 3.9.8 (needed commons lang3) that is removed here.
Additional information
See comments from here https://github.com/floverfelt/find-and-replace-maven-plugin/pull/11.
I'm also willing to help out as I have extensive maven knowledge and maintain a number of maven plugins and even wrote some myself. I'm also the current maintainer of spotbugs-maven-plugin which is probably the largest used one I directly work on. To a limited extent I have done commits into various maven owned plugins over the years as well.