On 04/11/2016 09:22, Jochen Theodorou wrote:
On 04.11.2016 09:25, Remi Forax wrote:
There are two issues with split packages,
- if you have the same class in each part of the package, the
behavior of your problem depend on the order in the classpath,
i've experienced this kind of bugs with two different libraries
requiring different version of ASM, at runtime, a class of the older
version was calling a class of the newer version :(
- security, if you allow split packages, you allow anybody to insert
any classes in any packages.
ok, not sure if I agree that these are reason enough for the
annoyance, but at least I know the proper reason now ;)
This is all part of reliable configuration where you can prove
correctness by construction. Alex's "Under the Hood" session from
JavaOne 2016 [1] is a great resource for understanding the science.
-Alan
[1] http://openjdk.java.net/projects/jigsaw/talks/#j1-2016
