Changed behaviour of ResourceBundle#getBundle()

[Alan Bateman]

On 12/12/2016 15:29, Gunnar Morling wrote:

> :
>
> It seems to be related to the fact that the bundle is located in the 
> default package, because the expected exception is raised if the 
> bundle is located in a proper package.
>
Right, resources in the unnamed package or with names that don't map to 
packages in the module are not encapsulated. So what you are seeing is 
correct.

-Alan