Re: Re: Very Slow Operations with NB 11
Don’t suppose default java memory settings may also be coming in to play here? Maybe bumping these up some might help? Eric Bresie ebre...@gmail.com > On April 12, 2019 at 9:31:22 AM CDT, Kodewerk wrote: > Hi Scott, > > I’d check to see if NB is in a long GC pause first. If not, then take 2-3 > thread dumps during the slow bit and post them. Your project code will not > show up in the thread dump. You can use jstack to obtain the thread dumps. > Just have everything set to trigger (small script) so you don’t miss the > event. > > Kind regards, > Kirk > > > On Apr 12, 2019, at 7:26 AM, Scott Palmer wrote: > > > > What is the best course of action for reporting slowness? I can’t share my > > project. > > I’m not certain how to give step-by-step instructions when the problem is > > basically one step in most cases. E.g. invoke auto-complete - nothing > > happens for several seconds. Invoke rename - dialog doesn’t appear for > > several seconds. Find usages - extremely slow > 5 second delay on a private > > member of a class less than 100 lines. > > > > In general it seems NB 11 is noticeably slower than NB 8.2. Not good > > considering slowness was already my #1 complaint about NB 8.2. I have so > > far found the benefits of NB outweigh the fact that it is much slower than > > other IDEs for the same operations, but the slowness of NB 11 is tipping > > the scale. I don’t want to switch IDEs, pease don’t interpret this as some > > sort of threat to do so. I would like to help find the issues in NB. But I > > don’t have the bandwidth to debug NB and not being about to share my > > project makes it difficult to provide helpful reports :-( > > > > Are others seeing the slowness? > > > > Find usages, renames, call-hierarchy, auto-complete… things I use all the > > time, I often have to wait 5 to 10 seconds for a response from the IDE, > > sometimes more. > > > > I’ve already deleted user dir and cache and restarted. > > I’m using Gradle-based Java projects, running NB 11.0 with JDK 8u202. > > > > Is there a wiki page with instructions on profiling the IDE? Maybe I can > > collect something useful. > > > > Scott > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > >
Re: RE: Redirection of netbeans.org to netbeans.apache.org
I’ve not used it but given the transition to Apache...maybe :-) https://nutch.apache.org/ Eric Bresie ebre...@gmail.com > On April 9, 2019 at 3:35:41 AM CDT, Eric Barboni wrote: > Hi, > Can we once set, stresstest the apidoc via a crawler tool to check for the > wrong link ? > Do you know a tool for that ? > > Regards > Eric > -Message d'origine- > De : Antonio > Envoyé : mardi 9 avril 2019 03:44 > À : dev@netbeans.incubator.apache.org > Objet : Re: Redirection of netbeans.org to netbeans.apache.org > > Hi all, > > We will need the involvement of both ASF Infra _and_ Oracle for this to > happen. > > As a preliminary step we've already set up https://netbeans.apache.org to > redirect non existing pages to https://legacy.netbeans.org [1] > > So, for instance, https://netbeans.apache.org/kb/previous.html now redirects > to https://legacy.netbeans.org/kb/previous.html (which sadly redirects > somewhere to old kenai). > > The steps are as follow: > > 1.- ASF Infra modifies the DNS settings of netbeans.org and makes > - https://legacy.netbeans.org an alias of https://netbeans.org > > 2.- Oracle modifies the configuration of the virtual server(s) in > https://netbeans.org and makes them serve _both_ https://netbeans.org and > https://legacy.netbeans.org with the same content. > > 3.- ASF Infra modifies the DNS settings of netbeans.org and > - makes https://netbeans.org an alias of https://netbeans.apache.org > - makes https://legacy.netbeans.org point to 137.254.56.26 > > With that we should be all set, I think. Please feel free to give > feedback/enhancements as appropriate. I'll update the JIRA by tomorrow > evening. > > Thanks, > Antonio > > > [1] > https://github.com/apache/incubator-netbeans-website/blob/master/netbeans.apache.org/src/content/.htaccess > > > > > > > El 08/04/2019 a las 11:20, Geertjan Wielenga escribió: > > The above sounds like a plan and I think we should simply go ahead with it. > > > > Antonio could you update INFRA-17245 and state who should do what when > > (I would do this but am about to take off into a Cloud). > > > > Gj > > > > > > On Mon, 8 Apr 2019 at 08:44, Antonio wrote: > > > > > Hi, > > > > > > I think this is perfectly possible. The plan could be: > > > > > > 1.- In netbeans.apache.org we add a redirection (.htaccess?) so that > > > all > > > 404 "not found" pages are sent to the existing Oracle hosted web > > > server, by IP address. Much like in the bits.netbeans.org website. > > > This may take one day or so. > > > > > > 2.- ASF Infra changes the DNS settings, making netbeans.org an alias > > > of netbeans.apache.org. Again this could take a few days, depending > > > on Infra availability. > > > > > > 3.- We monitor the 404 pages through the next weeks/month and see > > > which content is still missing in netbeans.apache.org. > > > > > > 4.- The existing Oracle web server is shut down after one/two months > > > and > > > 404 pages return a not found pages. > > > > > > Thoughts on the plan? > > > > > > Thanks, > > > Antonio > > > > > > P.S.: We can also make infra change the DNS settings as in 2.- above, > > > without the redirection. That's faster, but content that has not been > > > migrated will return a 404-Not Found webpage. > > > > > > > > > El 08/04/2019 a las 8:10, Geertjan Wielenga escribió: > > > > Hi all, > > > > > > > > We have this issue: > > > > > > > > https://issues.apache.org/jira/browse/INFRA-17245 > > > > > > > > The intention has been throughout the Apache NetBeans process to > > > > redirect from netbeans.org to netbeans.apache.org. Now that we're > > > > working on graduating, maybe the time for actually doing this has come? > > > > > > > > This point has come up today in the DISCUSS thread re becoming a top > > > level > > > > Apache project, hence maybe the moment is right to actually do this now. > > > > See: > > > > > > > > > > > https://lists.apache.org/thread.html/648834cdb10ce55aff2c6c8dd3c32454 > > > a74711c6289f385e456b74d8@%3Cgeneral.incubator.apache.org%3E > > > > > > > > Thoughts? If not now when. > > > > > > > > Gj > > > > > > > > > > - >
Re: Re: plugins.netbeans.org / netbeans.org
Regarding submitting to Maven Central (1)...this may be of help. https://central.sonatype.org/pages/ossrh-guide.html Eric Bresie ebre...@gmail.com > > > *From:* Geertjan Wielenga > *Sent:* Friday, April 05, 2019 8:31PM > *To:* Dev > *Subject:* Re: plugins.netbeans.org / netbeans.org > > > Here's the rough proposal: > > > > 1. Move all the plugins to Maven Central. Blockers: we don't know how to do > > that, if someone can advise, that will help. > > > > 2. Refactor the plugins.netbeans.org application so that (1) NBM files > > cannot be uploaded anymore and (2) instead of uploading, references need to > > be registered to the location of the NBM on Maven Central. Blockers: this > > is being investigated at the moment, timelines not known yet. This is > > doable because the plugins.netbeans.org application has been donated to > > Apache as part of the 3rd donation. > > > > 3. Deploy the plugins.netbeans.org application from the Apache NetBeans VM. > > There should be no problem with that since we'll not be distributing the > > NBMs from Apache (which would have been a problem since Apache distributes > > source code only) but only pages or references to Maven Central. > > > > 4. Enable the Plugin Manager inside Apache NetBeans to install NBM files > > directly from Maven Central, based on the references retrieved via the > > Update Center from the plugins.netbeans.org application running on the > > Apache NetBeans VM. > > > > 5. Continue using the plugins.netbeans.org URL, except that this will now > > be running at Apache and pointing to the plugins.netbeans.org application > > running on the Apache NetBeans VM. > > > > So, the above would mean that nothing is running on Oracle servers anymore, > > all NBMs that we care about are on Maven Central (and source code could > > mostly be on GitHub, except where plugin owners don't want their source > > code exposed, in which case they'd have it in their local proprietary > > backends), and we have the plugins.netbeans.org application refactored and > > simply showing Maven co-ordinated to the plugins on Maven Central. > > > > How does that sound? > > > > Gj > > > > On Fri, Apr 5, 2019 at 8:21 PM Antonio wrote: > > > > > Hi all, > > > > > > After the 11.0 release announcement, where we migrated most of > > > bits.netbeans.org, shall we tackle the plugins.netbeans.org website and > > > infrastructure for 12.0? Or is it too early? Also, what's missing in > > > netbeans.apache.org that still exists in netbeans.org and we want to keep? > > > > > > I can't remember when the infra @ Oracle for plugins.netbeans.org is > > > going to be shutdown, but the sooner we start thinking on hosting the > > > plugins, the better. This is something that is going to take us long, I > > > think. > > > > > > Thoughts? > > > > > > Thanks, > > > Antonio > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > > > > > For further information about the NetBeans mailing lists, visit: > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > > > > > > > >
Re: Re: [DISCUSS] Resolution for Apache NetBeans graduation to TLP
Just curious where are the “standard ASF guidelines” mentioned for reference? Eric Bresie ebre...@gmail.com > On April 3, 2019 at 2:39:39 AM CDT, Geertjan Wielenga > wrote: > Looks like that whole paragraph will be removed based in Bertrand's and > Jan's earlier comments. > > Gj > > On Tue, Apr 2, 2019 at 10:20 PM Antonio wrote: > > > Hi all, > > > > What about changing: > > > > "RESOLVED, that the initial Apache NetBeans PMC be and hereby is tasked > > with the creation of a set of bylaws intended to encourage open > > development and increased participation in the Apache NetBeans Project; " > > > > To > > > > "RESOLVED, that the initial Apache NetBeans PMC be and hereby is tasked > > to encourage open development and increased participation in the Apache > > NetBeans Project subject to the Bylaws of the Foundation; "? > > > > I'm somewhat concerned about asking our future Vicepresident to "serve > > ... subject to ... the Bylaws of the Foundation" and not to ask the PMC > > to do the same. > > > > That looks unfair to me! :-D > > > > Cheers, > > Antonio > > > > > > > > El 2/4/19 a las 16:54, Bertrand Delacretaz escribió: > > > Hi, > > > > > > the resolution looks mostly good to me, thanks! > > > > > > With one paragraph to remove: > > > > > > On Tue, Apr 2, 2019 at 3:59 PM Geertjan Wielenga > > > wrote: > > > > ...RESOLVED, that the initial Apache NetBeans PMC be and hereby is > > tasked with > > > > the creation of a set of bylaws intended to encourage open development > > and > > > > increased participation in the Apache NetBeans Project; and be it > > further... > > > > > > We don't ask for bylaws anymore, projects are welcome to create > > > community guidelines but that's not a requirement, they can also just > > > lean on the standard ASF guidelines. > > > > > > -Bertrand > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > > For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.incubator.apache.org > > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > >
Re: Re: How to debug NetBeans itself
Silly question what module to start Netbeans itself? Eric Bresie ebre...@gmail.com > On March 19, 2019 at 3:38:19 AM CDT, Geertjan Wielenga > wrote: > 1. Clone the repo. > 2. Open a module that you're interested in debugging. > 3. Place a breakpoint. > 4. Right-click the module and choose Debug. > > Gj > > On Tue, Mar 19, 2019 at 8:39 AM Thomas Kellerer wrote: > > > Is there any proper _written_ documenation rather than videos? > > > > Videos might be approriate for showing cute cats, but not for a serious > > software documentation > > (how do you copy and paste code, config file samples or commands from a > > video?) > > > > Thomas > > > > Geertjan Wielenga schrieb am 19.03.2019 um 08:21: > > > https://www.youtube.com/watch?v=rufG7VE-u9s > > > > > > Gj > > > > > > On Tue, Mar 19, 2019 at 7:52 AM Thomas Kellerer wrote: > > > > > > > I am trying to find the root cause of a NetBeans bug (NETBEANS-2240) > > but I > > > > have no idea on how to do that. > > > > > > > > How do I open NetBeans from within NetBeans? > > > > I can see about 1000 individual nbprojects (for each module I guess) > > when > > > > I check out the source from Github but no "overal" project that would > > > > enable me to open "everything". > > > > > > > > What I would like to do is to run NetBeans in debug mode open my > > projects > > > > that cause the error and investigate the line where the NPE is thrown. > > > > > > > > I went through the Help and FAQ pages on > > > > http://netbeans.apache.org/help/index.html (and > > > > https://github.com/apache/incubator-netbeans-website-cleanup) but > > > > everything seems to be geared towards creating a plugin/module rather > > than > > > > debugging the complete IDE. > > > > > > > > Thanks > > > > Thomas > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > >
Re: Re: Installers for Apache NetBeans 11
Came in late in the discussion so not sure what is presently in use for Netbeans but figured I’d mention. Looking at the Tomcat BUILDING.txt, the ant build script (see release target for dependencies) it appears to use an open source installer (see https://nsis.sourceforge.io/Main_Page ) as part of its build process. On none Windows environments it also uses Wine to build with. Eric Bresie ebre...@gmail.com > On March 19, 2019 at 7:25:45 AM CDT, Geertjan Wielenga > wrote: > Hey all, > > https://archive.apache.org/dist/tomcat/tomcat-9/v9.0.0.M1/bin/ > > Tomcat releases installers for Windows, somehow, let's follow however they > do that in terms of how to release it. > > Gj > > On Tue, Mar 19, 2019 at 12:33 PM Geertjan Wielenga < > geertjan.wiele...@googlemail.com> wrote: > > > Yes, how do we get this resolved, ask our mentors or open a legal issue or > > what do you suggest? > > > > Gj > > > > On Tue, 19 Mar 2019 at 12:31, Neil C Smith wrote: > > > > > On Tue, 19 Mar 2019 at 11:18, Geertjan Wielenga > > > wrote: > > > > Surely > > > > the sources of that installer themselves are not required to be part of > > > the > > > > release too? > > > > > > That (or a separately voted on source release / third-party > > > dependency) would exactly be my expectation, yes. IMO it should > > > always be possible for anyone to take the source release and build the > > > installers entirely from source without relying on anything that > > > hasn't been released. That's my interpretation from both the Apache > > > guidelines and how other FLOSS projects work, but the easiest thing > > > would surely be just to get clarification one way or another whether > > > this would be breaking Apache policy so merging can be considered if > > > required? > > > > > > Best wishes, > > > > > > Neil > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > > > > > For further information about the NetBeans mailing lists, visit: > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > > >
Re: Re: State of the Apache NetBeans installers
Regarding JRE/JDK... I thought one of the driving things about “modules” in new java release (I believe Java 11ish) was to make it so that a modularize jre could be created with only elements needed being included and the. That “custom” JRE would be embedded with the product. So would linking based on needs be viable. Or is inclusion of that counter to accepted practices here? Or am I going in a completely different tangent topic here? Eric Bresie ebre...@gmail.com > On February 5, 2019 at 6:02:43 AM CST, Neil C Smith > wrote: > On Tue, 5 Feb 2019 at 11:46, Emilian Bold wrote: > > Did you manage to digitally sign the EXE on Linux? > > No, that's one thing I haven't looked at yet. As far as I know it's > feasible though. Did a fair bit of reading around Electron packaging > when making a choice of what to go with - various discussion of > options for signing .exe on Linux/Mac there. > > Best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > >
Re: Re: Who wants to be the release manager for NetBeans 11.0?
Silly question but what are the responsibilities of the Release Manager? Eric Bresie ebre...@gmail.com > On February 5, 2019 at 5:42:50 AM CST, Neil C Smith > wrote: > On Tue, 5 Feb 2019 at 11:28, Geertjan Wielenga > wrote: > > Sounds like Emilian is release manager, with Neil as the shadow release > > manager! > > Great! Still be good to get another person who wants to learn the > process in there too - partly prompted by Laszlo's comment about > learning while being main RM. > > > (Not to be confused with British politics where the 'shadow' minister is > > the opposition minister. :-) ) > > In normal times, maybe. Now it's just everyone opposing everyone > else. I will try not to reflect the current chaos of British politics > in this! :-) > > Best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > >
Re: Re: What to do with features for EARs and EJBs?
I’m a little bit of an outsider looking in but give the older technologies are still Java EE why confuse things with Vintage and Legacy and just leave them there with the new Jakarta EE category when available. Then just make sure to have a Version attribute to configure the setup of the project? I thought recent Java EE has different profiles ( Web Profiles, Full Profiles,etc.). Would linking with these profiles work better? Or is the Java Web not necessarily related to Java EE Web Profiles? Is the Java Web more of a micro service? Would having an Enterprise category work better maybe and allowing different flavors under that? Eric Bresie ebre...@gmail.com > On January 28, 2019 at 11:50:02 PM CST, Josh Juneau > wrote: > I certainly agree that we need to keep this functionality within the IDE. > Regarding naming and/or breaking it out into an extension: I would be in > favor of keeping this functionality under a "Vintage Java EE" category. That > is what it is, correct? I think we will need a "Jakarta EE" category in the > near future, and this new category will not contain older functionality. I > would prefer going straight to "Jakarta EE" as a category, rather than use > "Modern Java EE". Jakarta EE 8 is due out soon and it will be in alignment > with Java EE 8. > > Older (deprecated) functionality should go into the "Vintage Java EE" > category. As Ken had mentioned, these technologies have not been deprecated, > but these older EAR wizards would certainly be vintage in my opinion. If the > day comes where most of the necessary EJB functionality is moved into other > APIs, then maybe it can be broken off as an add-on extension...but not until > then. > > Hope this makes sense. Thanks for all of the work that has gone into moving > the IDE forward. > > Josh Juneau > juneau...@gmail.com > http://jj-blogger.blogspot.com > https://www.apress.com/index.php/author/author/view/id/1866 > > > On Jan 28, 2019, at 3:41 PM, Brett Ryan wrote: > > > > Geertjan’s article is not about removing EE support it’s what to do about > > the old Java EE which is deprecated in favour of Jakarta EE in the future > > being the modern EE variant. > > > > For those that do not know, yes; Java EE 8 is the last version of Java EE, > > Jakarta EE while not being a replacement it is the new way forward for > > enterprise web applications. Removing legacy support in favour of new > > technologies is certainly not suicide it is moving with the times. > > > > Spring support has always been brilliant in NetBeans with bean navigation > > suppirt and now a lot of bootstrap support, but that’s the modern current > > focus. > > > > > On 29 Jan 2019, at 08:33, Tomas Poledny wrote: > > > > > > NetBeans had the best support of JEE from all IDE. Support for Spring is > > > very poor. I think remove of support part of JEE is suicide for NetBeans. > > > This is main reason why I am using NetBeans. > > > Tomas > > > > > > > On Mon, Jan 28, 2019, 22:24 Brett Ryan > > > > > > > It’s always a sensitive topic whenever considering to remove something, > > > > however; I am in favour for removing classic JavaEE support in favour of > > > > concentrating on modern java web technologies such as spring and > > > > Jakarta. > > > > > > > > It becomes an enormous task to support everything. We can always provide > > > > support in the form of a plugin though I feel that those using classic > > > > Java > > > > EE may not benefit from the additions being added to NetBeans IDE and > > > > may > > > > continue to use 8.2. > > > > > > > > > > On 29 Jan 2019, at 06:05, Geertjan Wielenga > > > > > wrote: > > > > > > > > > > Hi all, > > > > > > > > > > Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh, > > > > > David, > > > > at > > > > > least -- please advise what should be done with the EAR and EJB > > > > > support, > > > > as > > > > > described here: > > > > https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache > > > > > > > > > > And, hurray, thanks Matthias especially, and Vikas, Arunava, Sarvesh, > > > > > and > > > > > Reema, for a lot of work on relicensing, for getting the enterprise > > > > cluster > > > > > integrated! > > > > > >
Re: Netbeans XML Compilation Issues with JDK 11
Thanks for getting back to me on this...Still new so I welcome input to better understand things here. I will look into that... But still at some point wouldn't using newer jdk version (i.e. 10, 11, 12) for compilation be preferred? I assume some part of that is addressing the changes in modules and related dependencies. Is that something involving changes in the build files, have some jdk dependency versions identified, adding some modules imports of some type maybe? Eric Bresie ebre...@gmail.com On Sun, Jan 6, 2019 at 1:19 PM Geertjan Wielenga wrote: > You need to use JDK 8 to build Apache NetBeans as explained in the README. > > Gj > > On Sunday, January 6, 2019, Eric Bresie wrote: > > > OS: Windows 10, java 11.0.1 2018 > > > > Java: java --version > > > > > > java 11.0.1 2018-10-16 LTS > > > > Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS) > > > > Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode) > > > > > > Ant: > > > > C:\Windows\SysWOW64>ant -v > > > > Apache Ant(TM) version 1.10.5 compiled on July 10 2018 > > > > > > Git: > > > > C:\Windows\SysWOW64>git --version > > > > git version 2.18.0.windows.1 > > > > > > > > cloned from github as of 1/6/2019 11:20 CST > > > > Running build with: > > > > ant -Dcluster.config=full > > > > Received the following error: > > > > [pcompile] Generating 10 resource files to > > C:\git\netbeans\incubator-netbeans\nbbuild\build\ > > langtools\build\gensrc\jdk.jdeps > > [pathconvert] Warning: Nashorn engine is planned to be removed from a > > future JDK release > > [pathconvert] Warning: Nashorn engine is planned to be removed from a > > future JDK release > > [pathconvert] Warning: Nashorn engine is planned to be removed from a > > future JDK release > > [pathconvert] Warning: Nashorn engine is planned to be removed from a > > future JDK release > > [pathconvert] Warning: Nashorn engine is planned to be removed from a > > future JDK release > > [pathconvert] Warning: Nashorn engine is planned to be removed from a > > future JDK release > > [pathconvert] Warning: Nashorn engine is planned to be removed from a > > future JDK release > > [pathconvert] Warning: Nashorn engine is planned to be removed from a > > future JDK release > > [pathconvert] Warning: Nashorn engine is planned to be removed from a > > future JDK release > > [pathconvert] Warning: Nashorn engine is planned to be removed from a > > future JDK release > > > > generate-sources-internal: > > [pcompile] Generating 6 resource files to > > C:\git\netbeans\incubator-netbeans\nbbuild\build\ > > langtools\build\gensrc\jdk.jshell > > [mkdir] Created dir: > > C:\git\netbeans\incubator-netbeans\nbbuild\build\langtools\build\nb > > [javac] Compiling 1031 source files to > > C:\git\netbeans\incubator-netbeans\nbbuild\build\langtools\build\nb > > [javac] C:\git\netbeans\incubator-netbeans\nbbuild\build\ > > langtools\src\java.compiler\share\classes\javax\annotation\processing\ > > Messager.java:28: > > error: package javax.annotation does not exist > > [javac] import javax.annotation.*; > > [javac] ^ > > [javac] C:\git\netbeans\incubator-netbeans\nbbuild\build\ > > langtools\src\jdk.compiler\share\classes\com\sun\tools\ > > javac\model\.java:35: > > error: package sun.reflect.annotation is not visible > > [javac] import sun.reflect.annotation.*; > > [javac] ^ > > [javac] (package sun.reflect.annotation is declared in module java.base, > > which does not export it to module java.compiler) > > [javac] C:\git\netbeans\incubator-netbeans\nbbuild\build\ > > langtools\src\jdk.javadoc\share\classes\com\sun\tools\ > > doclets\internal\toolkit\builders\LayoutParser.java:31: > > error: package javax.xml.parsers is not visible > > [javac] import javax.xml.parsers.*; > > [javac] ^ > > [javac] (package javax.xml.parsers is declared in module java.xml, but > > module java.compiler does not read it) > > [javac] C:\git\netbeans\incubator-netbeans\nbbuild\build\ > > langtools\src\jdk.javadoc\share\classes\com\sun\tools\ > > doclets\internal\toolkit\builders\LayoutParser.java:33: > > error: package org.xml.sax is not visible > > [javac] import org.xml.sax.*; > > [javac] ^ > > [javac] (package org.xml.sax is declared in module java.xml, but module > > java.compiler does not read it) > > [javac] C:\git\netbeans\incubator-netbeans\nbbuild\build\ > > langtools\src\jdk.javadoc\share\cla
Netbeans XML Compilation Issues with JDK 11
tbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.javadoc\share\classes\com\sun\tools\doclets\internal\toolkit\builders\LayoutParser.java:122: error: method does not override or implement a method from a supertype [javac] @Override [javac] ^ [javac] C:\git\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.javadoc\share\classes\jdk\javadoc\internal\doclets\toolkit\builders\LayoutParser.java:110: error: method does not override or implement a method from a supertype [javac] @Override [javac] ^ [javac] C:\git\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.javadoc\share\classes\jdk\javadoc\internal\doclets\toolkit\builders\LayoutParser.java:126: error: method does not override or implement a method from a supertype [javac] @Override [javac] ^ [javac] 12 errors BUILD FAILED C:\git\netbeans\incubator-netbeans\nbbuild\build.xml:154: Compile failed; see the compiler error output for details. I want to apologize up front as I'm rather new to the project and hope I have not gone the wrong way in submitting but have I raised the issue already with https://issues.apache.org/jira/browse/NETBEANS-1866 I suspect this to be due to changes in the jdk 11 but not completely sure. Eric Bresie ebre...@gmail.com
