Make Tablesaw compliant with Java Platform Module System

The only way I can use Tablesaw in my Java project is to configure my project to be non-modular (i.e. remove the module-info.java file.) It would be fantastic if you could modularize Tablesaw to be compliant with the module system introduced in Java 9.

See this post on Stack Overflow for more information.

[lwhite1]

It would be an extreme approach, but i wonder if it makes sense to fork the project, and leave the Java 8 codebase in bug fix only mode, while doing new development on a different path. I will post in the discussions section, but it would be good to hear any feedback here also.

[aadrian]

@lwhite1

Do you know of some way that I could see which projects that depend on Tablesaw are using Java 8,

Also most corporate projects that depend on jTableSaw that I’m aware of (and are not on GitHub) are still with Java 8.

My biggest concern is that the way tablesaw is organized into sub-projects might make it much more complex to support both approaches.

That’s true. The effort is not worth unless there’s a bigger gain.

I’m not sure I can afford the effort to even make the change, let alone support both versions

Since projects that moved to Java >=11 can still use the Java 8 libraries without issues (and not the other way around), maybe just some hints in the Readme/Wiki should be more than enough to close this topic (e.g. until more projects get the chance to upgrade or there’s an easier migration path)

Breaking backward compatibility to introduce modules was a terrible mistake (IMO).

Exactly ! Backward compatibility was the main reason why Java was widely adopted in first place.