You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Eric Barboni <sk...@apache.org> on 2018/09/03 09:12:43 UTC
RE: Run on JDK8, compile on JDK11
Hi folks
In order to anticipate some jdk11 change (javaee module removal JEP 320) we
need to have a library providing thoose class. As Matthias Bläsing mention
in the PR they are already available in websvc.jaxws21.
But the module is only present for java cluster and must be available to ide
cluster (where db module needs it)
What is the good strategy here in order not to break good module and cluster
independence
Best Regards
Eric
-----Message d'origine-----
De : Eric Barboni <sk...@apache.org>
Envoyé : mercredi 29 août 2018 19:31
À : dev@netbeans.apache.org
Objet : Re: Run on JDK8, compile on JDK11
Hi,
I am an early adopter so , I will participate in this task.
Ii may not be the good path but creating a library in the ide cluster to
wrap the jaws-ri and others apis that are removed due to
JEP 320 seems an option to be able to compile on jdk8 as well as jdk11.
To illustrate concept: https://github.com/apache/incubator-netbeans/pull/816
Best regards
Eric
On 2018/08/28 18:06:26, Geertjan Wielenga <
<ma...@googlemail.com.INVALID> g...@googlemail.com.INVALID> wrote:
> Hi all,>
>
> Organizations building on top of the Apache NetBeans Platform aren't
ready>
> to adopt the upcoming JDK 11 yet. The industry typically will want to
stick>
> with JDK8 for a while still. As such, it is essential for Apache
> NetBeans>
> to support JDK 8 and to continue to allow the Apache NetBeans Platform
and>
> Apache NetBeans IDE to build and run on JDK 8.>
>
> On the other hand, there are early adopters that want to switch to
> the>
> latest JDK for development and execution as soon as possible. As such,
> it>
> is also important to be able to compile the Apache NetBeans Platform
> (and>
> probably also Apache NetBeans IDE) on JDK 11.>
>
> It is therefore great that with PR-790...>
>
> <https://github.com/apache/incubator-netbeans/pull/790>
https://github.com/apache/incubator-netbeans/pull/790>
>
> ...we have started to move in that direction. (Thanks, Jaroslav
> Tulach.)>
> Thanks to the above PR, one of the (in parallel running) Travis jobs
> runs>
> on top of JDK 11 and now builds the Apache NetBeans Platform. That
ensures>
> that the code in "platform" cluster is not using any obsolete APIs.
> Other>
> jobs are still building on JDK 8, ensuring the code isn't
(unconditionally)>
> using any fancy new features not available on JDK 8 (since, as pointed
out>
> above, remember there are groups requesting support of JDK 8).>
>
> PR-790 only made the NetBeans Platform cluster, i.e., the "platform">
> cluster, ready for compilation on JDK 11. The community is encouraged
> to>
> join in and adjust build scripts and code to be ready for compilation
> on>
> both - JDK 8 and JDK 11 - after taking a look at the PR above, in the
other>
> clusters too.>
>
> Build master hackers wanted!>
>
> Gj>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Run on JDK8, compile on JDK11
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
https://issues.apache.org/jira/browse/NETBEANS-805
The above issue relates to http://openjdk.java.net/jeps/320.
Reema is looking into this too.
Thanks,
Gj
On Mon, Sep 3, 2018 at 5:02 PM, Matthias Bläsing <mb...@doppel-helix.eu>
wrote:
> Hi Eric,
>
> Am Montag, den 03.09.2018, 16:35 +0200 schrieb Eric Barboni:
> > This is nice. Derby module as the same utility usage of Holder.
>
> also covered here:
>
> https://github.com/apache/incubator-netbeans/pull/833
>
> Greetings
>
> Matthias
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Run on JDK8, compile on JDK11
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
Hi Eric,
Am Montag, den 03.09.2018, 16:35 +0200 schrieb Eric Barboni:
> This is nice. Derby module as the same utility usage of Holder.
also covered here:
https://github.com/apache/incubator-netbeans/pull/833
Greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: Run on JDK8, compile on JDK11
Posted by Eric Barboni <sk...@apache.org>.
Hi Matthias,
This is nice. Derby module as the same utility usage of Holder.
I guess this is useless to provide library for that.
Regards
Eric
-----Message d'origine-----
De : Matthias Bläsing <mb...@doppel-helix.eu>
Envoyé : lundi 3 septembre 2018 16:11
À : dev@netbeans.incubator.apache.org
Objet : Re: Run on JDK8, compile on JDK11
Hi Eric,
Am Montag, den 03.09.2018, 15:50 +0200 schrieb Eric Barboni:
> I try to compile all clusters of NetBeans with jdk 11.
>
> Lots of javaee class disappears due to JEP 302. (java.xml.ws,
> java.xml.bind,..).
> Some NetBeans module needs thoose class to compile on jdk11.
>
> We need to provide them using library (one lib for each jar) .
> (Recoding seems a bad idea).
> We also need to know the best place to put libraries.
>
I already replied on the issue. From JAX-WS only the Holder class was used. The class was used in the DB modules out of convenience (they were just there and conveyed the right meaning).
There is an easy alternative: Use a one element array. It is typesave (even at runtime), a part of the core language.
This drops the requirement of JAX-WS and the DB module should compile cleanly. There are valid reasons to use JAX-WS and JAXB, but if we don't need them, I would make the change.
I checked db and this is the result from the change:
https://github.com/matthiasblaesing/incubator-netbeans/commit/f53592f9e55d5ac53a5f5817e4a0581396ddc37a
Greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Run on JDK8, compile on JDK11
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
Hi Eric,
Am Montag, den 03.09.2018, 15:50 +0200 schrieb Eric Barboni:
> I try to compile all clusters of NetBeans with jdk 11.
>
> Lots of javaee class disappears due to JEP 302. (java.xml.ws,
> java.xml.bind,..).
> Some NetBeans module needs thoose class to compile on jdk11.
>
> We need to provide them using library (one lib for each jar) .
> (Recoding seems a bad idea).
> We also need to know the best place to put libraries.
>
I already replied on the issue. From JAX-WS only the Holder class was
used. The class was used in the DB modules out of convenience (they
were just there and conveyed the right meaning).
There is an easy alternative: Use a one element array. It is typesave
(even at runtime), a part of the core language.
This drops the requirement of JAX-WS and the DB module should compile
cleanly. There are valid reasons to use JAX-WS and JAXB, but if we
don't need them, I would make the change.
I checked db and this is the result from the change:
https://github.com/matthiasblaesing/incubator-netbeans/commit/f53592f9e55d5ac53a5f5817e4a0581396ddc37a
Greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: Run on JDK8, compile on JDK11
Posted by Eric Barboni <sk...@apache.org>.
I try to compile all clusters of NetBeans with jdk 11.
Lots of javaee class disappears due to JEP 302. (java.xml.ws, java.xml.bind,..).
Some NetBeans module needs thoose class to compile on jdk11.
We need to provide them using library (one lib for each jar) . (Recoding seems a bad idea).
We also need to know the best place to put libraries.
Eric
-----Message d'origine-----
De : Geertjan Wielenga <ge...@googlemail.com.INVALID>
Envoyé : lundi 3 septembre 2018 13:36
À : dev <de...@netbeans.incubator.apache.org>
Objet : Re: Run on JDK8, compile on JDK11
I would like to help, but don't understand the scenario completely -- what are we trying to achieve, why, and how?
Thanks,
Gj
On Mon, Sep 3, 2018 at 11:12 AM, Eric Barboni <sk...@apache.org> wrote:
> Hi folks
>
> In order to anticipate some jdk11 change (javaee module removal JEP
> 320) we need to have a library providing thoose class. As Matthias
> Bläsing mention in the PR they are already available in websvc.jaxws21.
> But the module is only present for java cluster and must be available
> to ide cluster (where db module needs it)
>
> What is the good strategy here in order not to break good module and
> cluster independence
>
> Best Regards
> Eric
> -----Message d'origine-----
> De : Eric Barboni <sk...@apache.org>
> Envoyé : mercredi 29 août 2018 19:31
> À : dev@netbeans.apache.org
> Objet : Re: Run on JDK8, compile on JDK11
>
> Hi,
>
> I am an early adopter so , I will participate in this task.
>
>
>
> Ii may not be the good path but creating a library in the ide cluster
> to wrap the jaws-ri and others apis that are removed due to
>
> JEP 320 seems an option to be able to compile on jdk8 as well as jdk11.
>
>
>
> To illustrate concept: https://github.com/apache/
> incubator-netbeans/pull/816
>
>
>
> Best regards
>
> Eric
>
>
>
> On 2018/08/28 18:06:26, Geertjan Wielenga <
> <ma...@googlemail.com.INVALID> g...@googlemail.com.INVALID> wrote:
>
> > Hi all,>
>
> >
>
> > Organizations building on top of the Apache NetBeans Platform aren't
> ready>
>
> > to adopt the upcoming JDK 11 yet. The industry typically will want
> > to
> stick>
>
> > with JDK8 for a while still. As such, it is essential for Apache
> > NetBeans>
>
>
> > to support JDK 8 and to continue to allow the Apache NetBeans
> > Platform
> and>
>
> > Apache NetBeans IDE to build and run on JDK 8.>
>
> >
>
> > On the other hand, there are early adopters that want to switch to
> > the>
>
> > latest JDK for development and execution as soon as possible. As
> > such,
> > it>
>
>
> > is also important to be able to compile the Apache NetBeans Platform
> > (and>
>
>
> > probably also Apache NetBeans IDE) on JDK 11.>
>
> >
>
> > It is therefore great that with PR-790...>
>
> >
>
> > <https://github.com/apache/incubator-netbeans/pull/790>
> https://github.com/apache/incubator-netbeans/pull/790>
>
> >
>
> > ...we have started to move in that direction. (Thanks, Jaroslav
> > Tulach.)>
>
> > Thanks to the above PR, one of the (in parallel running) Travis jobs
> > runs>
>
>
> > on top of JDK 11 and now builds the Apache NetBeans Platform. That
> ensures>
>
> > that the code in "platform" cluster is not using any obsolete APIs.
> > Other>
>
>
> > jobs are still building on JDK 8, ensuring the code isn't
> (unconditionally)>
>
> > using any fancy new features not available on JDK 8 (since, as
> > pointed
> out>
>
> > above, remember there are groups requesting support of JDK 8).>
>
> >
>
> > PR-790 only made the NetBeans Platform cluster, i.e., the
> > "platform">
>
> > cluster, ready for compilation on JDK 11. The community is
> > encouraged
> > to>
>
> > join in and adjust build scripts and code to be ready for
> > compilation
> > on>
>
> > both - JDK 8 and JDK 11 - after taking a look at the PR above, in
> > the
> other>
>
> > clusters too.>
>
> >
>
> > Build master hackers wanted!>
>
> >
>
> > Gj>
>
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail:
> dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Run on JDK8, compile on JDK11
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
I would like to help, but don't understand the scenario completely -- what
are we trying to achieve, why, and how?
Thanks,
Gj
On Mon, Sep 3, 2018 at 11:12 AM, Eric Barboni <sk...@apache.org> wrote:
> Hi folks
>
> In order to anticipate some jdk11 change (javaee module removal JEP 320) we
> need to have a library providing thoose class. As Matthias Bläsing mention
> in the PR they are already available in websvc.jaxws21.
> But the module is only present for java cluster and must be available to
> ide
> cluster (where db module needs it)
>
> What is the good strategy here in order not to break good module and
> cluster
> independence
>
> Best Regards
> Eric
> -----Message d'origine-----
> De : Eric Barboni <sk...@apache.org>
> Envoyé : mercredi 29 août 2018 19:31
> À : dev@netbeans.apache.org
> Objet : Re: Run on JDK8, compile on JDK11
>
> Hi,
>
> I am an early adopter so , I will participate in this task.
>
>
>
> Ii may not be the good path but creating a library in the ide cluster to
> wrap the jaws-ri and others apis that are removed due to
>
> JEP 320 seems an option to be able to compile on jdk8 as well as jdk11.
>
>
>
> To illustrate concept: https://github.com/apache/
> incubator-netbeans/pull/816
>
>
>
> Best regards
>
> Eric
>
>
>
> On 2018/08/28 18:06:26, Geertjan Wielenga <
> <ma...@googlemail.com.INVALID> g...@googlemail.com.INVALID> wrote:
>
> > Hi all,>
>
> >
>
> > Organizations building on top of the Apache NetBeans Platform aren't
> ready>
>
> > to adopt the upcoming JDK 11 yet. The industry typically will want to
> stick>
>
> > with JDK8 for a while still. As such, it is essential for Apache
> > NetBeans>
>
>
> > to support JDK 8 and to continue to allow the Apache NetBeans Platform
> and>
>
> > Apache NetBeans IDE to build and run on JDK 8.>
>
> >
>
> > On the other hand, there are early adopters that want to switch to
> > the>
>
> > latest JDK for development and execution as soon as possible. As such,
> > it>
>
>
> > is also important to be able to compile the Apache NetBeans Platform
> > (and>
>
>
> > probably also Apache NetBeans IDE) on JDK 11.>
>
> >
>
> > It is therefore great that with PR-790...>
>
> >
>
> > <https://github.com/apache/incubator-netbeans/pull/790>
> https://github.com/apache/incubator-netbeans/pull/790>
>
> >
>
> > ...we have started to move in that direction. (Thanks, Jaroslav
> > Tulach.)>
>
> > Thanks to the above PR, one of the (in parallel running) Travis jobs
> > runs>
>
>
> > on top of JDK 11 and now builds the Apache NetBeans Platform. That
> ensures>
>
> > that the code in "platform" cluster is not using any obsolete APIs.
> > Other>
>
>
> > jobs are still building on JDK 8, ensuring the code isn't
> (unconditionally)>
>
> > using any fancy new features not available on JDK 8 (since, as pointed
> out>
>
> > above, remember there are groups requesting support of JDK 8).>
>
> >
>
> > PR-790 only made the NetBeans Platform cluster, i.e., the "platform">
>
> > cluster, ready for compilation on JDK 11. The community is encouraged
> > to>
>
> > join in and adjust build scripts and code to be ready for compilation
> > on>
>
> > both - JDK 8 and JDK 11 - after taking a look at the PR above, in the
> other>
>
> > clusters too.>
>
> >
>
> > Build master hackers wanted!>
>
> >
>
> > Gj>
>
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>