Is this project still active?

[garcia-jj]

At this time I see some important issues and pull requests waiting approval like thread-safe issues that can cause bug in several projects that uses this library, like #11 #14 .

Is this project still active? Contributions like this are welcome?

[vtapadia]

We have also faced some issues with the project specially related to thread safety. It would be great to know if this is still supported or not.

[chauhangs]

Also not compatible with spring batch 4

[pavansinguluri]

Any workaround for using beanio with spring batch 4? @chauhangs

[bjansen]

BeanIO has been forked and is actively maintained, see #29 for more info!

[vtapadia]

Hi @bjansen How can we help in maintaining/improving the project? I am not an expert but would like to assist.

[bjansen]

How can we help in maintaining/improving the project?

I can see multiple ways of contributing:

• If you don't have enough time to contribute code, you can still open issues for bugs you encounter, new features that you would like to see, maybe proof-read the docs at https://beanio.github.io/
• If you want to submit code but have no clue how BeanIO works internally (which is more or less where I am at the moment, but I hope I'll figure it out along the way 😄), you could use https://sonarcloud.io/dashboard?id=beanio as a starting point to improve code quality: fix potential bugs, improve code coverage etc. That would be a good way to get familiar with the project.
• If you're feeling confident, you can take one of the open issues (either here or at beanio/beanio) and try to fix/implement it.

To be fair I don't have huge plans for BeanIO. It's been used in many projects for a long time now, and I believe it's very stable and doesn't need a whole rewrite or something like that. There are a few issues that are pretty annoying, a few features that would be nice to have (like type handlers for java.time), and maybe have a better integration with recent technologies (Spring Batch, maybe Java 16 records, things like that). The main point of my attempt at reviving the project is to address these things. I'll still use a new major version (3) to symbolize BeanIO's new life (and Maven coordinates 😃), but I don't think BeanIO 3 is going to be a new revolutionary product.