Given separate discussion was on Java 8...but isn’t it possible with newer
modules based JDKs (9 I believe) to package multiple versions compiled,
packaged, and compatible with applicable JDKs environment? Multi release jar
(1), (2) for the platform and/or the ide?
(1)
On Sun, 28 Jun 2020 at 19:12, Jan Lahoda wrote:
> Frankly, I wonder what would be the benefit of dropping the JDK 8 support.
> Yes, nb-javac is more strictly needed on JDK 8 than on JDK 11, but running
> without nb-javac on JDK 11 is not particularly pleasant either. So nb-javac
> is effectively
> On Jun 28, 2020, at 2:12 PM, Jan Lahoda wrote:
>
>
> I'd agree with Jaroslav on having this discussion when JDK 17 is out. At
> least unless there's a compelling reason to discuss dropping JDK 8 support
> before that.
It would make sense to establish a policy that users and devs that
Frankly, I wonder what would be the benefit of dropping the JDK 8 support.
Yes, nb-javac is more strictly needed on JDK 8 than on JDK 11, but running
without nb-javac on JDK 11 is not particularly pleasant either. So nb-javac
is effectively needed on JDK 11 as well.
The costs of dropping the JDK
>
>
> In case of Batik, there may be someone creating a plugin for NetBeans 12.0
> that depends on it. It is (shall be) in our interest to make sure that
> such
> plugin continues to work "eternally".
In fact, here is one right now (I've been giving some vector editor
goodness to my old
> > > The thing is that now you cannot remove Batik (easily). It has
> > > become part of the NetBeans platform and shall be supported (until
> > > EOL). OracleLabs has already changed the build of IGV to rely on
> > > platform's provided Batik libraries.
> >
> > So, it looks like it is API as
Hi,
Am Samstag, den 27.06.2020, 09:12 +0100 schrieb Neil C Smith:
> On Sat, 27 Jun 2020 at 07:13, Jaroslav Tulach <
> jaroslav.tul...@gmail.com> wrote:
> > > - is any of it API? I still think we'd be better looking at
> > > svgSalamander, given option to use in FlatLaf and that Karl
> > >
On Sat, 27 Jun 2020 at 07:36, Jaroslav Tulach
wrote: ```
> --release
> Compile for a specific VM version. Supported targets: 6, 7, 8, 9,
> 10, 11
> ```
> modifying our build scripts to use it on JDK9+ would avoid the `ByteBuffer`
> & co. issues.
>From recollection, Ant, unlike Maven,
On Sat, 27 Jun 2020 at 07:13, Jaroslav Tulach wrote:
> > - is any of it API? I still think we'd be better looking at
> > svgSalamander, given option to use in FlatLaf and that Karl appears to
> > now be maintaining it.
> >
>
> The thing is that now you cannot remove Batik (easily). It has become
so 27. 6. 2020 v 8:07 odesílatel Matthias Bläsing
napsal:
>
> I think a staged approach could work (move parts of NetBeans IDE to 11
> and let the platform stay with 8),
OracleLabs IGV includes not only NetBeans Platform cluster, but also
support for Java edit/compile/debug, support for
Hi,
I can't see anybody has asked the question how long Oracle still needs
to stay on JDK8 for its NetBeans based products. Will they ever upgrade
to their own latest JDK LTS release (11, 17 ..)?
IMHO if Oracle need longer LTS support the best way is fork and support
it yourself. Many commercial
>
> > #2 - I feel as well that the versioning scheme should be fixed somehow.
> > The current scheme is confusing, unfortunately changing the current
> > scheme just a little would be more confusing. Probably we shall really
> > go with date based version numbers...
>
Honestly, it is just a
Hi,
Am Samstag, den 27.06.2020, 07:55 +0200 schrieb Jaroslav Tulach:
> > I think support for developing apps on JDK 8 is important, but I
> don’t
> > think it makes sense to hold the NB platform to build/run on JDK 8.
> >
>
> Said to hear that. It is certainly -1 from me to drop JDK8 as the
>
čt 25. 6. 2020 v 3:05 odesílatel Scott Palmer napsal:
> It wasn’t clear to me if #1 was in terms of supporting developing Java
> apps based on JDK 8 or for running NetBeans on JDK 8.
>
OracleLabs is primarily interested in running the NetBeans bits on JDK8.
> I think support for developing
On Thu, 25 Jun 2020 at 00:15, Laszlo Kishalmi wrote:
> #1 - That shall be a question to the community, but I do not see
> anything against to support if nothing else the platform on JDK8 for a
> long while.
I think the concern comes from our discussion on whether it was time
to drop support for
Hello Everybody,
On 23.06.20 15:56, Jaroslav Tulach wrote:
Hello Neil,
I'd like to understand what my colleagues requirements on LTS are as well!
There seems to be some inherent mismatch when we talk about it, so I am not
really sure. But let's try:
#1 - we need support for JDK8 - everytime we
It wasn’t clear to me if #1 was in terms of supporting developing Java apps
based on JDK 8 or for running NetBeans on JDK 8.
I think support for developing apps on JDK 8 is important, but I don’t think it
makes sense to hold the NB platform to build/run on JDK 8.
Scott
> On Jun 24, 2020, at
Thank you, it is good to hear such feedback from time to time.
#1 - That shall be a question to the community, but I do not see
anything against to support if nothing else the platform on JDK8 for a
long while. Though I'd be happy if we can get rid of patches/workarounds
made for pre-JDK8-s.
On Tue, 23 Jun 2020 at 14:56, Jaroslav Tulach wrote:
> I'd like to understand what my colleagues requirements on LTS are as well!
> There seems to be some inherent mismatch when we talk about it, so I am not
> really sure. But let's try:
Thanks! Interested to see what other people have to say
Hello Neil,
I'd like to understand what my colleagues requirements on LTS are as well!
There seems to be some inherent mismatch when we talk about it, so I am not
really sure. But let's try:
#1 - we need support for JDK8 - everytime we upgrade I have to prove that
JDK8 is still supported and
On Mon, 22 Jun 2020 at 11:10, Jaroslav Tulach wrote:
> do we plan to provide patches to 12.0 version? E.g. 12.0.x versions with
> only selected bugfixes? What's the process of getting a fix in? For example
> https://github.com/apache/netbeans/pull/2210 is something I'd like to see
> included.
21 matches
Mail list logo
