On 19/06/18 20:46, Tim Allison wrote:
What would you think of requiring Java 10 to build Tika 2.0 but still
setting 8 as the target?  This would allow us to bake modularity in now.
Given that I haven't actually tried modularizing/jigsawizing Tika yet, this
could be a complete disaster, of course. :)

I'm not sure how well it'd work given that most of our dependencies aren't java module-ized?

David North (from POI) has done quite a bit on java modules for existing codebases, and hit some snags, and IIRC commons have had problems too. I don't mind either way though!

Nick

Reply via email to