Resolution exception when service interface gets exposed via --add-exports

[Alan Bateman]

On 20/11/2017 21:56, Gunnar Morling wrote:
> I see, thanks for the clarification.
>
> It's a pity, though, I hoped to employ that approach for providing a 
> custom jlink plug-in (implementation of 
> jdk.tools.jlink.plugin.Plugin). So it seems that's not possible until 
> jdk.jlink exports j.t.j.plugin? Are there any plans to do so some time 
> soon?
>
> Even if it was marked as experimental/incubating, being able to 
> provide custom jlink plug-ins would enable interesting use cases.
>
There was interest in creating an incubating module in JDK 9 but it was 
put aside due to the issues of tool modules depending on an incubating 
module. The other issue is that most of the interesting plugins to date 
do code generation at link time and are deeply tied to specific areas of 
java.base and other core modules (they can't really live outside of the 
jdk repo). So while it might be desirable to expose the interface for 
plugins, I think it will need further exploration to see if it makes 
sense or not.

-Alan