- Mail original -
> De: "Chris Hegarty" <chris.hega...@oracle.com>
> À: "Remi Forax" <fo...@univ-mlv.fr>
> Cc: "jigsaw-dev" <jigsaw-dev@openjdk.java.net>
> Envoyé: Mardi 17 Janvier 2017 10:36:32
> Objet: Re: RFR 8171380: R
> On 17 Jan 2017, at 00:02, Remi Forax wrote:
>
> Cris,
> it seems that there is a mechanism for API that are experimental in the jdk,
> by example java.net.http uses this mechanism, is it possible to reuse the
> same mechanism for the jlink plugin API ?
I did look at the
t;
> À: "jigsaw-dev" <jigsaw-dev@openjdk.java.net>, "A. Sundararajan"
> <sundararajan.athijegannat...@oracle.com>, "Jim Laskey
> (Oracle)" <james.las...@oracle.com>
> Envoyé: Lundi 16 Janvier 2017 16:46:16
> Objet: RFR 8171380: Remov
On 16/01/17 16:26, Alan Bateman wrote:
This looks okay except CustomPluginTest where I assume you mean to add
it to the ProblemList file.
Ok, I'll remove the @ignore and put the test on the ProblemList
before pushing. Thanks.
-Chris.
On 16/01/2017 15:46, Chris Hegarty wrote:
The Jlink Plugin API is not going to be supported in 9, so
should not be exported [1], for use by third parties. Besides
the removal of the export, most of the changes are adding
@modules tags to existing tests.
+1
-Sundar
On 16/01/17, 9:16 PM, Chris Hegarty wrote:
The Jlink Plugin API is not going to be supported in 9, so
should not be exported [1], for use by third parties. Besides
the removal of the export, most of the changes are adding
@modules tags to existing tests.
The Jlink Plugin API is not going to be supported in 9, so
should not be exported [1], for use by third parties. Besides
the removal of the export, most of the changes are adding
@modules tags to existing tests.
http://cr.openjdk.java.net/~chegar/8171380.00/
Note: Sundar will follow up with