netbeans-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geertjan Wielenga <>
Subject Re: IDE-javac
Date Tue, 08 Nov 2016 22:41:03 GMT
Agreed, definitely, something to be discussed.

A starting point to understanding the what and why of nb-javac is here:

However, how is the maintenance of nb-javac any different to the
maintenance of any other part of NetBeans? All of NetBeans needs to be
maintained and developed further, not only nb-javac. That's why we're
building up a very large group of individual committers for Apache NetBeans
(incubating), one of which tasks will be the maintenance of the nb-javac
codebase. Some of those individual committers come from Oracle, so would
logically work on the areas they know best, which includes nb-javac, though
it would be great to share that knowledge around so that others outside
Oracle can work on this too. Where the development of nb-javac will happen
is yet to be determined, possibly on GitHub for example or simply in its
current location, i.e., within its location
under its Oracle license, of course.



On Tue, Nov 8, 2016 at 9:55 PM, Craig Russell <>

> It might be useful to discuss (either on this thread or another) the
> long-term approach to nb-javac.
> Short term (through Apache NetBeans graduation), it appears that Oracle is
> committed to maintaining this code base.
> Medium term (Java 10?) there might need to be significant changes. Will
> Oracle be able/want to keep nb-javac current?
> Long term perhaps some of the Oracle resources working on nb-javac could
> make a more abstract ide-javac (I didn’t quite follow the else-thread
> reference to this) so Apache NetBeans could depend on a less-specific
> nb-javac.
> If this doesn’t make sense, please disregard.
> Craig
> Craig L Russell

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message