Problems with non-exported split packages (for resources/files)

[Alan Bateman]

On 10/05/2017 08:48, Alessio Stalla wrote:

> Case in point, the rapid application development framework Portofino [1] is
> split in several (non-Jigsaw) modules each with its message bundle
> fragment, which is named portofino-messages and placed in the empty package.
By "the empty package" then I assume you mean the resources are in the 
top-level directory of the JAR file. If that is so then you shouldn't 
have any issues as there is no encapsulation of resources in the 
top-level directory.

On the other hand, if the resources are compiled, meaning you have 
compiled the resources to .class files,  then there will be an issue 
because all types in a named module must be in a named package.

-Alan