Non-java resources creating split-package problems?

[Alan Bateman]

On 27/08/2019 18:09, Stephan Herrmann wrote:
> :
>
> For the problem at hand I see two possible solutions:
> - the "hack" of forging the ModulePackages attribute
> - rename the folder to change it from encapsulated (a) to legacy (c).
>
> Both options have some kind of negative smell, so let me ask: which 
> solution is recommended when trying to group legalese files in a 
> folder inside a jar that should NEVER be subjected to JPMS-specific 
> conflict checks?
The JAR file format doesn't have a standard location for such files. 
Also the`jar` tool doesn't have an option to exclude specific locations 
when it computes the set of packages. The top-level directory or a 
location such as META-INF/legal will work of course.

-Alan