On Mon, May 16, 2016 at 10:45 AM, Alan Bateman <alan.bate...@oracle.com> wrote: > > As to what is going on? The java.corba and the EE modules are no longer > resolved by default when compiling code in the unnamed module or where the > main class is loaded from class path. This means the types in these modules > are not visible. Nothing has been removed and if you run with `-addmods > java.se.ee` then each of the Java EE modules will be resolved as they were > previously. We have updated text for JEP 261 that describes this in more > detail, along with the rational. We will likely assess the impact of this > change later in JDK 9 but for now, there is easy workaround for those that > depend on these components being in the JDK. >
Just a little followup: It seems most code impacted by this change is just using jaxb's base64 class. We've seen it not just with Solr but with cloud libraries like AWS SDK and so on. I'm not really suggesting anything here but just mentioning it as a possible "easy win" from usages I have seen.
