On Tue, Oct 19, 2021 at 7:58 PM Michael Bien <[email protected]> wrote:
> On 19.10.21 11:51, Jaroslav Tulach wrote: > > po 18. 10. 2021 v 20:32 odesÃlatel Neil C Smith <[email protected]> > > napsal: > > > >> On Mon, 18 Oct 2021 at 17:44, Michael Bien <[email protected]> wrote: > >>>> That's a developer request, right? We don't want to scare regular > >>>> NetBeans users with such confusing configuration, I assume. At least > >>>> the biggest UX motivation for including nb-javac by default is to > >>>> avoid all the download dialogs when one wants to use NetBeans to > >>>> develop Java. It should work out of the box. > >>> getting rid of the dialog is a worthy effort i suppose, but is it still > >>> possible to disable the nb-javac module in the plugin manage without > >>> breaking NB after the change? > >> I'm curious what the difference between a developer request and a user > >> request really is for us?! > > > > Developers download source releases or work directly with sources in Git. > > Users download complementary binary releases. > > i am not going to maintain my own differently configured fork of NB if > that is what you asking. The point why i open PRs is to hope to get > changes into netbeans, not to get changes into *my* netbeans. > > > Since my question has been avoided so far i will just assume for now > that we won't be able to disable nb-javac after the proposed PR is > integrated. > FWIW, my personal opinion is that the ability to run using javac from JDK is highly desirable. It may not support old(er) JDKs (so that the new APIs can be used directly), and may not be the default, but using javac from (new enough and similar enough) JDKs should be possible, I think. Jan > > > >> also, since automated (!) backporting of javac using jackpot seems > >> to be feasible now (I don't know how reliable that is) > > It is reliable and passes all known tests. > > i was thinking about the automated backporting itself. If the build > would need hand holding every two weeks to account for upstream JDK > changes or not. (i was only thinking loudly, this is probably not > answerable without actually attempting it) > > > >> https://github.com/oracle/nb-javac/pull/12 > >> > >> all what would be needed is to upload weekly > >> builds (pulling from OpenJDK HEAD) > > All you need to do is to get the above repository and modify > > > https://github.com/JaroslavTulach/nb-javac/blob/jtulach/BackportingUpstreamJavac/make/langtools/netbeans/nb-javac/nbproject/project.properties#L3 > > to refer to different revision of OpenJDK. Then rebuild. Setting a weekly > > upload service up should be easy. Feel free to do it. > > thanks, i am going to give this a try next time i work with upstream > JDKs, esp if there is no option left to disable nb-javac in future. > > > -michael > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
