Avoiding same-package conflicts

[Jeroen Frijters]

Alex Buckley wrote:
> Yes. We were clear at JavaOne that 1:1 migration -- one module per JAR
> -- is just one possibility among many. I actually expect the main
> obstacle to 1:1 migration to be not duplication of exported packages but
> rather cycles between classes in the JARs.

In your JavaOne talk you also mentioned "[no] duplication of exported packages", but the real restriction (at least in the current builds) seems to be "no duplication of packages (in the same layer)".

Can you confirm this?

Thanks,
Jeroen