If you happen to use Apache Commons Imaging for metadata reading & writing you should really consider switching to
https://github.com/ashampoo/kim as Commons Imaging is ridiculously bad maintained!
By porting this framework to Kotlin (which is Kim) I fixed a lot of bugs along the way, which are years old and won’t be fixed.
To contribute back to the original project I opened a
PR for a bug that corrupts EXIF on write. The maintainer demanded a test as a proof which I also
provided. But he really doesn’t understand anything. 🙄
Looking at the
commit history you see him only fixing style issues in the code while there are PRs for bugfixes open for many months and a
lot of bug reports in the issue tracker no one cares about. 🤯
I believe the maintainer even doesn’t understand anything about the domain of the lib. It’s really ridiculous and sad. 😞
I’m angry with myself that I invested the time to craft a PR for the project, because I could have known it beforehand. Despite all the bugs they want to go to 1.0-M1 and I was thinking I want to help users of Commons Imaging. 🤷♂️
But now I think it’s time to just warn about this badly managed project. Don’t use it! ⚠️
Your alternatives are either
Ashampoo Kim for Kotlin Multiplatform or
metadata-extractor if you only need JVM and no write support. And of course there is always the great
ExifTool by Phil Harvey.
Switch to one of these, but please stop using Apache Commons Imaging!