Stability is also a thing. Resources too, unless you’re volunteering?

Gj

On Fri, 5 Feb 2021 at 17:19, Randamuna Namae <[email protected]> wrote:

> > What is the benefit of this?
>
> Project health. Bit rot <https://en.wikipedia.org/wiki/Software_rot> is a
> thing.
>
> Cheers
>
> On Fri, Feb 5, 2021 at 12:19 PM Geertjan Wielenga
> <[email protected]> wrote:
>
> > What is the benefit of this?
> >
> > Gj
> >
> > On Fri, 5 Feb 2021 at 16:12, Eric Bresie <[email protected]> wrote:
> >
> > > Question on the Netbeans project's plan for moving forward towards
> > > introducing and utilizing features with newer Java versions.
> > >
> > > I understand the basic expectations at present are mainly build on Java
> > 8,
> > > while being possible to build (with applicable flags or jdk settings)
> for
> > > newer java versions.
> > >
> > > At what point do we need to take the plunge and start actually using
> some
> > > of the new features for Java 9 and beyond?
> > >
> > > When compiling with new java, I see
> > >
> > >    1. references to deprecated or removed interfaces so assume that is
> > one
> > >    thing that would have to be addressed.
> > >    2. I see references to "source versions" (I saw one expecting server
> > >    version 1.4) which also show up.  As I understand it, at some point
> > the
> > >    general behavior in some of that will be to only support a few jdk
> > > version
> > >    back so assume this might be a case for other needed changes [what
> > > makes it
> > >    a specific version and is it as simple as changing the source
> version
> > in
> > >    the project details or build scripts]?
> > >
> > > Assume doing so would require changes like
> > >
> > >    1. Any "JDK" specific build details might have to be addressed
> > >    2. Address depreciation and source version differences
> > >    3. Find existing code which are candidates for refactoring with
> newer
> > >    java features involved
> > >    4. Maybe leverage some JDK tools or utilizing netbeans Java
> > "refactoring
> > >    hints" for suggestions (i.e. changing loops to lambdas, utilized
> newer
> > > file
> > >    interfaces, etc.)
> > >    5. Any dependency libraries would have to be updated with compatible
> > >    versions.  This does have the added benefit of utilizing newer
> > versions
> > > in
> > >    these as well which may include performance, security, or bug fits
> > > benefits
> > >    as well.
> > >    6. Update any documentation (i.e. build/runtime environments)
> > >
> > > Given the recent javadocs build issues requiring newer jdk, it may mean
> > the
> > > time is coming sooner rather than later.
> > >
> > > I know this would be a major bit of work but I wanted to raise the
> > > question.
> > >
> > > Eric Bresie
> > > [email protected]
> > >
> >
>

Reply via email to