Dropping 1.6 is fair enough.
Moving to Java 11 brought with it the module system which, frankly, causes many pain points.
Consider going back to Java 8 as the project baseline, the module-info artefacts can remain, but the project should build against Java 8.
Related:
862
928
930
944
Also would remove the burden of maintaining the 4.4.x series along with a mirrored 4.5.x series - i.e. the 4.5.x series would no longer be required and could be written off as a folly.
To summarise currently:
4.4.x branch is 1.6 (and still current) 4.x branch branch is 11 and modules (and current of course, 4.5.x is the latest) 5.x master is in development and is currently 11 and modules
The consideration therefore is for the 5.x master to go back to Java 8 and not care about modules (although it should be harmless to retain the module system artefacts? I am not sure about that).
该提问来源于开源项目：caprica/vlcj
