Re: [External] : [VOTE] Release Apache NetBeans 16 macOS installer
+1 (binding) installed on macOS 12.6.1, NB 16 picked GraalVM CE JDK 11 from system, imported settings from 15. Works nicely, Martin > On 29. 11. 2022, at 0:06, John Mc wrote: > > Vote for Apache NetBeans 16 macOS installer. > > Primary voting artefact : > https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/16/Apache-NetBeans-16-bin-macosx.dmg__;!!ACWV5N9M2RV99hQ!OenJs_R2pGTvSq2IUAT8y6bjxXptMUXEsRbMzLZiz9mHP3dXEKsIJ3iD4pSlDFgEIyjKhrKnOCh1ADUE8hye0JCRKg$ > > > SHA512 checksum : > https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/16/Apache-NetBeans-16-bin-macosx.dmg.sha512__;!!ACWV5N9M2RV99hQ!OenJs_R2pGTvSq2IUAT8y6bjxXptMUXEsRbMzLZiz9mHP3dXEKsIJ3iD4pSlDFgEIyjKhrKnOCh1ADUE8hzIxX8ZcA$ > > > a4294a59335e10975ef42d5b4a8f16a26f98019c22c89ebff81d645a8cdc1a307ce904a06600ecfd5f121307d03c40a755dd1aaeb65b9e851ac0534f9cdb6970 > > KEYS file : > https://urldefense.com/v3/__https://dist.apache.org/repos/dist/release/netbeans/KEYS__;!!ACWV5N9M2RV99hQ!OenJs_R2pGTvSq2IUAT8y6bjxXptMUXEsRbMzLZiz9mHP3dXEKsIJ3iD4pSlDFgEIyjKhrKnOCh1ADUE8hyn8mtZ_w$ > > > PGP signature file : > https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/16/Apache-NetBeans-16-bin-macosx.dmg.asc__;!!ACWV5N9M2RV99hQ!OenJs_R2pGTvSq2IUAT8y6bjxXptMUXEsRbMzLZiz9mHP3dXEKsIJ3iD4pSlDFgEIyjKhrKnOCh1ADUE8hxUIk1D0Q$ > > > Built locally using the artefacts found in the Jenkins job: > https://urldefense.com/v3/__https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/11/__;!!ACWV5N9M2RV99hQ!OenJs_R2pGTvSq2IUAT8y6bjxXptMUXEsRbMzLZiz9mHP3dXEKsIJ3iD4pSlDFgEIyjKhrKnOCh1ADUE8hzVcOTbZg$ > > > This vote is going to be open at least 72 hours, vote with +1, 0, and > -1 as usual. Please mark your vote with (binding) if you're an Apache > NetBeans PMC member. > > This vote is dependent on the main Apache NetBeans 16 release vote passing. > > Regards > > John - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [VOTE] Release Apache NetBeans 16 RPM package
+1 Tested on openSUSE Tumbleweed with OpenJDK 19 and Fedora 37 with OpenJDK 17. - Downloaded the rpm, checked the signature and installed it - Created, built and ran a Hello World project Greetings, Javier El miércoles, 30 de noviembre de 2022 14:26:45 (CET) Neil C Smith escribió: > Vote to release Apache NetBeans 16 RPM package, built from the Apache > NetBeans 16 binary zip release with NBPackage 1.0-beta2. > > The package is architecture independent and reliant on system JDK. > Package built with provided command line (rather than config file). > > RPM package artefact : > https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/16/apach > e-netbeans-16-0.noarch.rpm SHA : > 58643613402cd6035f3be266283ea66c728f6bd843df4a083e588376c45cee0be5aa096 > 41383662a2d1a39f5f340a97e7d0969f473731e74551d5a82f68f SHA file : > https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/16/apac > he-netbeans-16-0.noarch.rpm.sha512 PGP : > https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/16/apac > he-netbeans-16-0.noarch.rpm.asc CLI : ./nbpackage --type linux-rpm > -Pname="Apache NetBeans" > -Pversion=16 -Purl="https://netbeans.apache.org"; > -Prpm.desktop-filename="apache-netbeans-ide-16" -Prpm.wmclass="Apache > NetBeans IDE 16" --input netbeans-16-bin.zip > > > This vote is going to be open at least 72 hours, vote with +1, 0, and > -1 as usual. Please mark your vote with (binding) if you're an Apache > NetBeans PMC member. > > This vote is dependent on the main NBPackage 1.0-beta2 release vote passing. > > > Thanks everyone, and a special thanks to Javier Llorente for recent > contribution of RPM support to NBPackage. > > Best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists -- Javier Llorente signature.asc Description: This is a digitally signed message part.
Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Hi, Any date in mind for this release? Lazslo, release before Christmas break or after? I propose to label PRs and Issues going to this 16.0.1patch release with “16p1” label? Martin > On 1. 12. 2022, at 17:21, Eric Barboni wrote: > > It will keep jenkins busy and trigger a build per commit and do all release > stack. > Only if a release date for release160 is set in the json, jenkins will do > apidoc only. > > > Using delivery may be more Jenkins friendly but I don't think it's a human :p. > > Eric > > > -Message d'origine- > De : Neil C Smith > Envoyé : jeudi 1 décembre 2022 14:52 > À : dev@netbeans.apache.org > Objet : Re: [DISCUSSION] Gradle Patch Release for NetBeans 16 > > On Mon, 28 Nov 2022 at 15:55, Neil C Smith wrote: >> >> On Mon, 28 Nov 2022 at 15:43, László Kishalmi >> wrote: >>> release161 branch has been removed, PR-s have been re-targeted to >>> release160. >> >> Great, thanks! I'm just waiting on votes for rest of additional >> binaries to start and I'll close the main vote. Want to make sure >> everything is OK before we merge anything else into the branch. > > OK, everything done that needs to be done, so release160 can be considered > open again for merging. > > However, I wonder whether we should have a transient branch like delivery > (now deleted) for merging into? Merges into release*** branches trigger a > lot of things. Eric? > > Best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!ACWV5N9M2RV99hQ!IlQ-QlflBngiqiJ-XrDNRp8DGqUnn5Sje469nldr9SZqZxx_bezC8Mq8hTr8TmvWQ0jAtg5rxPxLEVA$ > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!ACWV5N9M2RV99hQ!IlQ-QlflBngiqiJ-XrDNRp8DGqUnn5Sje469nldr9SZqZxx_bezC8Mq8hTr8TmvWQ0jAtg5rxPxLEVA$ > > > > - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: average PR merge time
Oh.. So PR can become to old to merge? Even with all tests passing? On Thu, Dec 1, 2022 at 3:48 PM Brad Walker wrote: > Not at all.. > > But sometimes a PR might need a little bit of "encouragement" to get over > the finish line. > > And I've had PRs that have gotten a little bit "old", if you will.. Usually > a simple message to the group that I've rebased the code, tested it out > again against the latest code base, and it is ready to go, will do the > trick. > > > -brad w. > > On Thu, Dec 1, 2022 at 6:01 AM Łukasz Bownik > wrote: > > > " The slowest response times are for issues where the submitter has gone > > silent and the pull response might need a little bit of work." > > > > Does it mean non-critical PRs get starved unless the submitter is > annoying? > > > > On Tue, Nov 29, 2022 at 8:41 PM Neil C Smith > > wrote: > > > > > On Tue, 29 Nov 2022 at 19:16, Eric Bresie wrote: > > > > Others need to be identified and coordinated for inclusion in a give > > > release with release manager . > > > > > > That only applies to PRs targeting delivery or release** branches, > > > which tend to be managed a little differently. Also, release team, > > > not single release manager. > > > > > > Neil > > > > > -- Łukasz Bownik
RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
It will keep jenkins busy and trigger a build per commit and do all release stack. Only if a release date for release160 is set in the json, jenkins will do apidoc only. Using delivery may be more Jenkins friendly but I don't think it's a human :p. Eric -Message d'origine- De : Neil C Smith Envoyé : jeudi 1 décembre 2022 14:52 À : dev@netbeans.apache.org Objet : Re: [DISCUSSION] Gradle Patch Release for NetBeans 16 On Mon, 28 Nov 2022 at 15:55, Neil C Smith wrote: > > On Mon, 28 Nov 2022 at 15:43, László Kishalmi > wrote: > > release161 branch has been removed, PR-s have been re-targeted to > > release160. > > Great, thanks! I'm just waiting on votes for rest of additional > binaries to start and I'll close the main vote. Want to make sure > everything is OK before we merge anything else into the branch. OK, everything done that needs to be done, so release160 can be considered open again for merging. However, I wonder whether we should have a transient branch like delivery (now deleted) for merging into? Merges into release*** branches trigger a lot of things. Eric? Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.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.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: average PR merge time
Not at all.. But sometimes a PR might need a little bit of "encouragement" to get over the finish line. And I've had PRs that have gotten a little bit "old", if you will.. Usually a simple message to the group that I've rebased the code, tested it out again against the latest code base, and it is ready to go, will do the trick. -brad w. On Thu, Dec 1, 2022 at 6:01 AM Łukasz Bownik wrote: > " The slowest response times are for issues where the submitter has gone > silent and the pull response might need a little bit of work." > > Does it mean non-critical PRs get starved unless the submitter is annoying? > > On Tue, Nov 29, 2022 at 8:41 PM Neil C Smith > wrote: > > > On Tue, 29 Nov 2022 at 19:16, Eric Bresie wrote: > > > Others need to be identified and coordinated for inclusion in a give > > release with release manager . > > > > That only applies to PRs targeting delivery or release** branches, > > which tend to be managed a little differently. Also, release team, > > not single release manager. > > > > Neil > >
Re: [DISCUSSION] Gradle Patch Release for NetBeans 16
On Mon, 28 Nov 2022 at 15:55, Neil C Smith wrote: > > On Mon, 28 Nov 2022 at 15:43, László Kishalmi > wrote: > > release161 branch has been removed, PR-s have been re-targeted to > > release160. > > Great, thanks! I'm just waiting on votes for rest of additional > binaries to start and I'll close the main vote. Want to make sure > everything is OK before we merge anything else into the branch. OK, everything done that needs to be done, so release160 can be considered open again for merging. However, I wonder whether we should have a transient branch like delivery (now deleted) for merging into? Merges into release*** branches trigger a lot of things. Eric? Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: average PR merge time
" The slowest response times are for issues where the submitter has gone silent and the pull response might need a little bit of work." Does it mean non-critical PRs get starved unless the submitter is annoying? On Tue, Nov 29, 2022 at 8:41 PM Neil C Smith wrote: > On Tue, 29 Nov 2022 at 19:16, Eric Bresie wrote: > > Others need to be identified and coordinated for inclusion in a give > release with release manager . > > That only applies to PRs targeting delivery or release** branches, > which tend to be managed a little differently. Also, release team, > not single release manager. > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > -- Łukasz Bownik
Release Apache NetBeans 16 RPM package
Hi constantin, I think you are binding as PMC member. Eric -Message d'origine- De : constantin drabo Envoyé : mercredi 30 novembre 2022 14:50 À : dev@netbeans.apache.org Objet : RE: [VOTE] Release Apache NetBeans 16 RPM package +1 (no-binding) Constantin ?? La Terre est le berceau de l'humanit??, mais on ne passe pas sa vie enti??re dans un berceau. ?? - ConstantinE. Tsiolkovski , p??re de l'astronautique?? et de l'a??rospatiale modernes. De : Neil C Smith Envoyé : mercredi 30 novembre 2022 01:26 À : dev Objet : [VOTE] Release Apache NetBeans 16 RPM package Vote to release Apache NetBeans 16 RPM package, built from the Apache NetBeans 16 binary zip release with NBPackage 1.0-beta2. The package is architecture independent and reliant on system JDK. Package built with provided command line (rather than config file). RPM package artefact : https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/16/apach e-netbeans-16-0.noarch.rpm SHA : 58643613402cd6035f3be266283ea66c728f6bd843df4a083e588376c45cee0be5aa0964 1383662a2d1a39f5f340a97e7d0969f473731e74551d5a82f68f SHA file : https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/16/apach e-netbeans-16-0.noarch.rpm.sha512 PGP : https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/16/apach e-netbeans-16-0.noarch.rpm.asc CLI : ./nbpackage --type linux-rpm -Pname="Apache NetBeans" -Pversion=16 -Purl="https://netbeans.apache.org"; -Prpm.desktop-filename="apache-netbeans-ide-16" -Prpm.wmclass="Apache NetBeans IDE 16" --input netbeans-16-bin.zip This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC member. This vote is dependent on the main NBPackage 1.0-beta2 release vote passing. Thanks everyone, and a special thanks to Javier Llorente for recent contribution of RPM support to NBPackage. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.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.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Netbeans Vision / Roadmap
> > Short answer, yes - eg. link on all release candidate emails > https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16 I didn't know that one. Milestones are a cool way to mark specific merges Longer answer, there is some work going on to better categorize all > this - eg. https://github.com/apache/netbeans/releases The draft one > particularly, but that's private. That is what I was looking for, but this list is not available until a few days before the release, right? Not recently. What prompted the question? > We were wondering if there is a kind of a road map of planned new features people agreed to work on. Moreover in our company, when we foresee to release a given feature for a specific version, we tag it even long before the final release. We were looking for such an equivalent in the NB project. I think that is exactly the purpose of milestones. Thx for your answers On Wed, Nov 30, 2022 at 3:09 PM Neil C Smith wrote: > On Wed, 30 Nov 2022 at 15:02, Jean-Marc Borer wrote: > > Ok, so does it mean, that I have to check Github history to find out what > > is in a upcoming release (16 for example)? > > Short answer, yes - eg. link on all release candidate emails > https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16 > > Longer answer, there is some work going on to better categorize all > this - eg. https://github.com/apache/netbeans/releases The draft one > particularly, but that's private. > > > > > Am I missing something or did something change for the release > > > management? > > Not recently. What prompted the question? > > Best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: [RELEASES] Post-vote release update
On 01.12.22 10:22, Neil C Smith wrote: On Thu, 1 Dec 2022 at 03:41, Michael Bien wrote: On 30.11.22 17:42, Neil C Smith wrote: I also completely didn't see the previous tag option - I swear you just made that appear! :-) #4826 has this marked in a big red box: Well, that explains it then. How am I meant to see it if the red box and arrow are not showing up in the UI correctly?! Obvious accessibility issue that needs reporting. :-) https://github.com/apache/netbeans/pull/4826 :-) In seriousness, yes, time to re-look at that PR and get it merged. I assume we might be able to retrospectively regenerate the older release notes? I hope so yes, since releases do have a "edit release" button which opens a form with an "update release" button. This would hopefully update the release info without notifying users who watch the project again and cause confusion. The config in the PR might need more categories, I didn't put a lot of thought into it - we certainly have more labels than that. -mbien Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.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.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [RELEASES] Post-vote release update
On Thu, 1 Dec 2022 at 03:41, Michael Bien wrote: > On 30.11.22 17:42, Neil C Smith wrote: > I also completely didn't see > > the previous tag option - I swear you just made that appear! :-) > > #4826 has this marked in a big red box: Well, that explains it then. How am I meant to see it if the red box and arrow are not showing up in the UI correctly?! Obvious accessibility issue that needs reporting. :-) > https://github.com/apache/netbeans/pull/4826 :-) In seriousness, yes, time to re-look at that PR and get it merged. I assume we might be able to retrospectively regenerate the older release notes? Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [VOTE] Release Apache NetBeans 16 macOS installer
+1 (non-binding) Product Version: Apache NetBeans IDE 16 Java: 17.0.3.1; OpenJDK 64-Bit Server VM 17.0.3.1+2-LTS Runtime: OpenJDK Runtime Environment 17.0.3.1+2-LTS System: Mac OS X version 12.6 running on aarch64; UTF-8; de_DE (nb) Installation without any issues, but during runtime I got this exception several times: java.lang.NullPointerException: Cannot invoke "com.sun.tools.javac.code.Type.getThrownTypes()" because "tree.meth.type" is null at com.sun.tools.javac.comp.Flow$FlowAnalyzer.visitApply(Flow.java:1576) at com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1799) at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:49) at com.sun.tools.javac.comp.Flow$BaseAnalyzer.scan(Flow.java:447) at com.sun.tools.javac.comp.Flow$FlowAnalyzer.visitVarDef(Flow.java:1317) at com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:1018) at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:49) at com.sun.tools.javac.comp.Flow$BaseAnalyzer.scan(Flow.java:447) at com.sun.tools.javac.comp.Flow$FlowAnalyzer.visitClassDef(Flow.java:1226) at com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:810) at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:49) at com.sun.tools.javac.comp.Flow$BaseAnalyzer.scan(Flow.java:447) at com.sun.tools.javac.comp.Flow$FlowAnalyzer.analyzeTree(Flow.java:1669) at com.sun.tools.javac.comp.Flow$FlowAnalyzer.analyzeTree(Flow.java:1659) at com.sun.tools.javac.comp.Flow.analyzeTree(Flow.java:225) at com.sun.tools.javac.main.JavaCompiler.flow(JavaCompiler.java:1377) at com.sun.tools.javac.main.JavaCompiler.flow(JavaCompiler.java:1341) at com.sun.tools.javac.api.JavacTaskImpl.analyze(JavacTaskImpl.java:404) at com.sun.tools.javac.api.JavacTaskImpl.generate(JavacTaskImpl.java:465) at org.netbeans.modules.java.source.indexing.VanillaCompileWorker$2.run(VanillaCompileWorker.java:359) at org.netbeans.modules.java.source.parsing.FileManagerTransaction.runConcurrent(FileManagerTransaction.java:180) [catch] at org.netbeans.modules.java.source.indexing.VanillaCompileWorker.compile(VanillaCompileWorker.java:346) at org.netbeans.modules.java.source.indexing.JavaCustomIndexer.index(JavaCustomIndexer.java:360) at org.netbeans.modules.parsing.spi.indexing.Indexable$MyAccessor$2.run(Indexable.java:138) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runIndexer(RepositoryUpdater.java:274) at org.netbeans.modules.parsing.spi.indexing.Indexable$MyAccessor.index(Indexable.java:136) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doIndex(RepositoryUpdater.java:2749) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.lambda$index$0(RepositoryUpdater.java:2626) at org.netbeans.modules.parsing.impl.indexing.errors.TaskCache.refreshTransaction(TaskCache.java:540) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.index(RepositoryUpdater.java:2625) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.lambda$scanFiles$2(RepositoryUpdater.java:3332) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.lambda$runInContext$4(RepositoryUpdater.java:2119) at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2117) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2098) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.access$1400(RepositoryUpdater.java:135) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.scanFiles(RepositoryUpdater.java:3290) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$FileListWork.getDone(RepositoryUpdater.java:3832) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doTheWork(RepositoryUpdater.java:3452) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task._run(RepositoryUpdater.java:6197) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task.access$3400(RepositoryUpdater.java:5855) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task$2.lambda$call$0(RepositoryUpdater.java:6116) at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279) at org.netbeans.modules.parsing.impl.RunWhenScanFinishedSupport.performScan(RunWhenScanFinishedSupport.java:83) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task$2.call(RepositoryUpdater.java:6116) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task$2.call(RepositoryUpdater.java:6112) at
