Qualified exports to an unknown module
Alex Buckley
alex.buckley at oracle.com
Fri Dec 7 18:59:34 UTC 2018
On 12/7/2018 8:46 AM, cowwoc wrote:
> Back in 2016 you guys had a discussion about qualified exports to a module
> that was not available at compile-time:
> http://jigsaw-dev.1059479.n5.nabble.com/Issue-with-qualified-exports-td5712839.html
>
> I could not find the conclusion to that discussion. How are users supposed
> to use qualified exports to some module that is defined by some future
> compilation? See https://stackoverflow.com/q/53670052/14731 for a concrete
> example.
The decision was: Qualified exports/opens to a non-observable module is
NOT an error (see
https://docs.oracle.com/javase/specs/jls/se11/html/jls-7.html#jls-7.7.2-310).
javac will give an on-by-default lint warning instead.
The StackOverflow question says "Because I configured the compiler to
treat warnings as errors (-Werror), the build fails." so the questioner
should look at disabling the lint warning (see
https://docs.oracle.com/en/java/javase/11/tools/javac.html#GUID-AEEC9F07-CB49-4E96-8BC7-BCC2C7F725C9).
Alex
More information about the jigsaw-dev
mailing list