[jira] [Commented] (NETBEANS-888) Open Recent file not working
[ https://issues.apache.org/jira/browse/NETBEANS-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823748#comment-16823748 ] Christian Lenz commented on NETBEANS-888: - Only mac related? For me, on windows 10 with NB 10 and JDK 11.0.2 the menu entry is working. > Open Recent file not working > > > Key: NETBEANS-888 > URL: https://issues.apache.org/jira/browse/NETBEANS-888 > Project: NetBeans > Issue Type: Bug > Components: ide - UI >Affects Versions: 9.0, 10.0, 11.0 > Environment: MacOS High Sierra version 10.13.4 > MacOS Mojave 10.14.4 >Reporter: Javier A. Ortiz >Priority: Major > > Clicking on File>Open Recent File>File doesn't open the file but using the > shortcut for the most recent one works. > No error or suspecting messages in the log either. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-2445) Need for Netbeans Version schema release for Chocolatey Package
[
https://issues.apache.org/jira/browse/NETBEANS-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823709#comment-16823709
]
ComFreek edited comment on NETBEANS-2445 at 4/23/19 6:05 AM:
-
I am a package maintainer as well and involved in the linked discussion. I
think a short TL;DR would be helpful to you:
h2. Summary, TL;DR
Chocolatey is a package manager for Windows.
*Current state:* we have a package "netbeans" for NetBeans 8.2, see
[https://chocolatey.org/packages/netbeans.]
*New state:* Apache NetBeans has officially been approven, thus we now have
three alternative options:
* Provide packages "netbeans", "apache-netbeans": "netbeans" is for the old
version 8, "apache-netbeans" serves versions 9, 10 and 11 in parallel.
Users of "apache-netbeans" may pin their desired major version and thus for
example still receive updates on the 9.x line.
* Provide packages "netbeans", "apache-netbeans9", "apache-netbeans10",
"apache-netbeans11"
Same as above, but now the versions are split onto three packages on their own.
* Provide package "netbeans" with versions 8, 9, 10 and 11 in parallel
Again, users may pin their version and still receive updates.
*Question from us to you*: Which option would you favor?
was (Author: comfreek):
I am a package maintainer as well and involved in the linked discussion. I
think a quick TL;DR would be helpful to you:
h2. Summary, TL;DR
Chocolatey is a package manager for Windows.
*Current state:* we have a package "netbeans" for NetBeans 8.2, see
[https://chocolatey.org/packages/netbeans.]
*New state:* Apache NetBeans has officially been approven, thus we now have
three alternative options:
* Provide packages "netbeans", "apache-netbeans": "netbeans" is for the old
version 8, "apache-netbeans" serves versions 9, 10 and 11 in parallel.
Users of "apache-netbeans" may pin their desired major version and thus for
example still receive updates on the 9.x line.
* Provide packages "netbeans", "apache-netbeans9", "apache-netbeans10",
"apache-netbeans11"
Same as above, but now the versions are split onto three packages on their own.
* Provide package "netbeans" with versions 8, 9, 10 and 11 in parallel
Again, users may pin their version and still receive updates.
*Question from us to you*: Which option would you favor?
> Need for Netbeans Version schema release for Chocolatey Package
> ---
>
> Key: NETBEANS-2445
> URL: https://issues.apache.org/jira/browse/NETBEANS-2445
> Project: NetBeans
> Issue Type: Task
>Affects Versions: 10.0, 11.0
>Reporter: SALES
>Priority: Major
> Labels: documentation, windows
>
> h1. Context
> I'm a chocolatey package maintainer... and also a big fan of Netbeans. I
> recently implemented a dedicated {{Netbeans 11}} package.
> Now, the Chocolatey Moderators are faciing a dilemna about the package
> version scheme.
> I'm about sure your feedback could help a lot.
> h1. Question
> From what I could see I looks more convenient to manage separated packages to
> make softwares updates more confortable.
> I mean : if I initially installed Netbeans 10, I want to stick on 10, and
> when I apply updates, stick on Netbeans 10, *and not upgrade to 11*. From my
> point of view it makes the final user update process easier and safer. For
> example to better manage plugin compatibilities.
> h1. Action
> Could yo please tell us your opinion about that on the dedicated ticket :
> [https://github.com/chocolatey/chocolatey-package-requests/issues/572]
>
> So we can make the {{Netbeans 11}} available on chocolatey central repo ?
>
> h1. Resources
> * Package sources : [https://github.com/adriens/chocolatey-netbeans-11]
> * Package moderation issue :
> [https://github.com/chocolatey/chocolatey-package-requests/issues/572]
>
> Thank you in advance for your help.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-2445) Need for Netbeans Version schema release for Chocolatey Package
[
https://issues.apache.org/jira/browse/NETBEANS-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823709#comment-16823709
]
ComFreek edited comment on NETBEANS-2445 at 4/23/19 6:04 AM:
-
I am a package maintainer as well and involved in the linked discussion. I
think a quick TL;DR would be helpful to you:
h2. Summary, TL;DR
Chocolatey is a package manager for Windows.
*Current state:* we have a package "netbeans" for NetBeans 8.2, see
[https://chocolatey.org/packages/netbeans.]
*New state:* Apache NetBeans has officially been approven, thus we now have
three alternative options:
* Provide packages "netbeans", "apache-netbeans": "netbeans" is for the old
version 8, "apache-netbeans" serves versions 9, 10 and 11 in parallel.
Users of "apache-netbeans" may pin their desired major version and thus for
example still receive updates on the 9.x line.
* Provide packages "netbeans", "apache-netbeans9", "apache-netbeans10",
"apache-netbeans11"
Same as above, but now the versions are split onto three packages on their own.
* Provide package "netbeans" with versions 8, 9, 10 and 11 in parallel
Again, users may pin their version and still receive updates.
*Question from us to you*: Which option would you favor?
was (Author: comfreek):
I am a package maintainer as well and involved in the linked discussion. I
think a quick *TL;DR* would be helpful to you:
Chocolatey is a package manager for Windows.
Current state: we have a package "netbeans" for NetBeans 8.2, see
[https://chocolatey.org/packages/netbeans.]
New state: Apache NetBeans has officially been approven, thus we now have three
alternative options:
* Provide packages "netbeans", "apache-netbeans": "netbeans" is for the old
version 8, "apache-netbeans" serves versions 9, 10 and 11 in parallel.
Users of "apache-netbeans" may pin their desired major version and thus for
example still receive updates on the 9.x line.
* Provide packages "netbeans", "apache-netbeans9", "apache-netbeans10",
"apache-netbeans11"
Same as above, but now the versions are split onto three packages on their own.
* Provide package "netbeans" with versions 8, 9, 10 and 11 in parallel
Again, users may pin their version and still receive updates.
*Question from us to you*: Which option would you favor?
> Need for Netbeans Version schema release for Chocolatey Package
> ---
>
> Key: NETBEANS-2445
> URL: https://issues.apache.org/jira/browse/NETBEANS-2445
> Project: NetBeans
> Issue Type: Task
>Affects Versions: 10.0, 11.0
>Reporter: SALES
>Priority: Major
> Labels: documentation, windows
>
> h1. Context
> I'm a chocolatey package maintainer... and also a big fan of Netbeans. I
> recently implemented a dedicated {{Netbeans 11}} package.
> Now, the Chocolatey Moderators are faciing a dilemna about the package
> version scheme.
> I'm about sure your feedback could help a lot.
> h1. Question
> From what I could see I looks more convenient to manage separated packages to
> make softwares updates more confortable.
> I mean : if I initially installed Netbeans 10, I want to stick on 10, and
> when I apply updates, stick on Netbeans 10, *and not upgrade to 11*. From my
> point of view it makes the final user update process easier and safer. For
> example to better manage plugin compatibilities.
> h1. Action
> Could yo please tell us your opinion about that on the dedicated ticket :
> [https://github.com/chocolatey/chocolatey-package-requests/issues/572]
>
> So we can make the {{Netbeans 11}} available on chocolatey central repo ?
>
> h1. Resources
> * Package sources : [https://github.com/adriens/chocolatey-netbeans-11]
> * Package moderation issue :
> [https://github.com/chocolatey/chocolatey-package-requests/issues/572]
>
> Thank you in advance for your help.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2445) Need for Netbeans Version schema release for Chocolatey Package
[
https://issues.apache.org/jira/browse/NETBEANS-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823709#comment-16823709
]
ComFreek commented on NETBEANS-2445:
I am a package maintainer as well and involved in the linked discussion. I
think a quick *TL;DR* would be helpful to you:
Chocolatey is a package manager for Windows.
Current state: we have a package "netbeans" for NetBeans 8.2, see
[https://chocolatey.org/packages/netbeans.]
New state: Apache NetBeans has officially been approven, thus we now have three
alternative options:
* Provide packages "netbeans", "apache-netbeans": "netbeans" is for the old
version 8, "apache-netbeans" serves versions 9, 10 and 11 in parallel.
Users of "apache-netbeans" may pin their desired major version and thus for
example still receive updates on the 9.x line.
* Provide packages "netbeans", "apache-netbeans9", "apache-netbeans10",
"apache-netbeans11"
Same as above, but now the versions are split onto three packages on their own.
* Provide package "netbeans" with versions 8, 9, 10 and 11 in parallel
Again, users may pin their version and still receive updates.
*Question from us to you*: Which option would you favor?
> Need for Netbeans Version schema release for Chocolatey Package
> ---
>
> Key: NETBEANS-2445
> URL: https://issues.apache.org/jira/browse/NETBEANS-2445
> Project: NetBeans
> Issue Type: Task
>Affects Versions: 10.0, 11.0
>Reporter: SALES
>Priority: Major
> Labels: documentation, windows
>
> h1. Context
> I'm a chocolatey package maintainer... and also a big fan of Netbeans. I
> recently implemented a dedicated {{Netbeans 11}} package.
> Now, the Chocolatey Moderators are faciing a dilemna about the package
> version scheme.
> I'm about sure your feedback could help a lot.
> h1. Question
> From what I could see I looks more convenient to manage separated packages to
> make softwares updates more confortable.
> I mean : if I initially installed Netbeans 10, I want to stick on 10, and
> when I apply updates, stick on Netbeans 10, *and not upgrade to 11*. From my
> point of view it makes the final user update process easier and safer. For
> example to better manage plugin compatibilities.
> h1. Action
> Could yo please tell us your opinion about that on the dedicated ticket :
> [https://github.com/chocolatey/chocolatey-package-requests/issues/572]
>
> So we can make the {{Netbeans 11}} available on chocolatey central repo ?
>
> h1. Resources
> * Package sources : [https://github.com/adriens/chocolatey-netbeans-11]
> * Package moderation issue :
> [https://github.com/chocolatey/chocolatey-package-requests/issues/572]
>
> Thank you in advance for your help.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-2378) .gradle files uneditable until groovy is "activated"
[ https://issues.apache.org/jira/browse/NETBEANS-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Kishalmi resolved NETBEANS-2378. --- Resolution: Fixed Fix Version/s: Next Mark fixed as the corresponding PR got merged. > .gradle files uneditable until groovy is "activated" > > > Key: NETBEANS-2378 > URL: https://issues.apache.org/jira/browse/NETBEANS-2378 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.0 > Environment: Windows 10 x64, Java 12 >Reporter: Mark Claassen >Assignee: Laszlo Kishalmi >Priority: Critical > Labels: pull-request-available > Fix For: Next > > Time Spent: 20m > Remaining Estimate: 0h > > I was trying out Netbeans 11 and it recognized by Gradle project immediately. > However, when I tried to edit any .gradle files, it opened up an editor tab > with no name on it. The tab was in the 'local history' view, which didn't > work, and it was not possible to view the source file. I was unable to find > any way I could edit the .gradle file in Netbeans. > I was able to fix the problem by randomly checking my settings. I went to > the Tools -> Misc ===> "Groovy". When I did that, a groovy "activating" > message appeared quickly. Now, I can now edit .gradle files. > I can appreciate the desire for lazy optimization, but this one can hurt a > bit. Everything else worked, and I had no idea why I couldn't edit the > .gradle files in Netbeans. I almost gave Netbeans 11 a pass because of this, > which is why I put the initial priority as "Critical". > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-2348) "Test Package" does not work in Gradle projects
[ https://issues.apache.org/jira/browse/NETBEANS-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Kishalmi resolved NETBEANS-2348. --- Resolution: Fixed Fix Version/s: Next Mark fixed as the corresponding PR got merged. > "Test Package" does not work in Gradle projects > --- > > Key: NETBEANS-2348 > URL: https://issues.apache.org/jira/browse/NETBEANS-2348 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.0 >Reporter: Travis >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available > Fix For: Next > > Time Spent: 0.5h > Remaining Estimate: 0h > > I'm running Netbeans 11 vc4 on Windows, with the old Gradle plugin version > 2.0.2. And in this case, I was running on Java 8 with Gradle 5.2, in case > that matters (probably doesn't?). > > Right clicking on a test package and selecting the "Test Package" menu item > result in an immediate exception (included below). The operation is then > gracefully terminated without doing anything (which means the "Test Package" > operation is dead in this case). > > I haven't done much work to understand this better yet. It might be > something specific about my project that is just hitting an unusual corner > case. I can try to create and attach a minimal project for you to reproduce > the issue if it would help. > > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 > at java.lang.String.substring(String.java:1967) > at > org.netbeans.modules.gradle.java.GradleJavaTokenProvider.processSelectedClass(GradleJavaTokenProvider.java:93) > at > org.netbeans.modules.gradle.java.GradleJavaTokenProvider.createReplacements(GradleJavaTokenProvider.java:79) > at > org.netbeans.modules.gradle.actions.ReplaceTokenProviderMerger.createReplacements(ReplaceTokenProviderMerger.java:72) > at > org.netbeans.modules.gradle.ActionProviderImpl.replaceTokens(ActionProviderImpl.java:532) > at > org.netbeans.modules.gradle.ActionProviderImpl.evalueteArgs(ActionProviderImpl.java:299) > at > org.netbeans.modules.gradle.ActionProviderImpl.invokeProjectAction(ActionProviderImpl.java:200) > at > org.netbeans.modules.gradle.ActionProviderImpl.invokeAction(ActionProviderImpl.java:128) > at > org.netbeans.modules.project.ui.actions.FileAction$3$1.run(FileAction.java:219) > at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311) > at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758) > at java.awt.EventQueue.access$500(EventQueue.java:97) > at java.awt.EventQueue$3.run(EventQueue.java:709) > at java.awt.EventQueue$3.run(EventQueue.java:703) > at java.security.AccessController.doPrivileged(Native Method) > at > java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74) > at java.awt.EventQueue.dispatchEvent(EventQueue.java:728) > at > org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136) > [catch] at > java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205) > at > java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) > at > java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) > at java.awt.EventDispatchThread.run(EventDispatchThread.java:82) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2397) Java's provide ... with NOT working in maven projects
[ https://issues.apache.org/jira/browse/NETBEANS-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823685#comment-16823685 ] Martin commented on NETBEANS-2397: -- I think the problem might be with nbactions.xml Under the exec-maven-plugin is in version 1.5, but 1.6 is required for java module system ( [here|https://github.com/mojohaus/exec-maven-plugin/issues/55] and [here2|https://github.com/mojohaus/exec-maven-plugin/milestone/3?closed=1 ] ). Will this help solve the problem? > Java's provide ... with NOT working in maven projects > - > > Key: NETBEANS-2397 > URL: https://issues.apache.org/jira/browse/NETBEANS-2397 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.0 > Environment: Windows10 >Reporter: Martin >Priority: Blocker > Attachments: netbeans11_sample.mp4, sample.zip, vscode_sample.mp4 > > > Please check the attached sample. > > The sample is working with VS Code and IntelliJ Idea. > Also working when doing with "old school" netbeans (ant) projects. > > Please fix urgently! > > Some linker problem? > > > Problem is > * mavenproject1 uses I_Sample > * mavenproject2 provides I_Sample with SampleImpl > * mavenproject3 requires mavenproject1 and mavenproject2 > > When you debug or run mavenproject3 > * it will call mavenproject1.Sample.load > * since mavenproject2 is required, the serviceloader must return the loaded > SampleImpl instance BUT IT DOES NOT > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-2293) NPE in "compile file" in gradle project
[
https://issues.apache.org/jira/browse/NETBEANS-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laszlo Kishalmi resolved NETBEANS-2293.
---
Resolution: Fixed
Fix Version/s: Next
Mark fixed as the corresponding PR got merged.
> NPE in "compile file" in gradle project
> ---
>
> Key: NETBEANS-2293
> URL: https://issues.apache.org/jira/browse/NETBEANS-2293
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 11.0
>Reporter: Andreas Eberhöfer
>Assignee: Laszlo Kishalmi
>Priority: Major
> Labels: pull-request-available
> Fix For: Next
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I get a NPE when I press F9 for "compile file" in a gradle project.
> {code:java}
> java.lang.NullPointerException
> at
> org.netbeans.modules.gradle.java.GradleJavaTokenProvider.evaluateSingleMethod(GradleJavaTokenProvider.java:158)
> at
> org.netbeans.modules.gradle.java.GradleJavaTokenProvider.processSelectedMethod(GradleJavaTokenProvider.java:104)
> at
> org.netbeans.modules.gradle.java.GradleJavaTokenProvider.createReplacements(GradleJavaTokenProvider.java:80)
> at
> org.netbeans.modules.gradle.actions.ReplaceTokenProviderMerger.createReplacements(ReplaceTokenProviderMerger.java:72)
> at
> org.netbeans.modules.gradle.ActionProviderImpl.replaceTokens(ActionProviderImpl.java:532)
> at
> org.netbeans.modules.gradle.ActionProviderImpl.evalueteArgs(ActionProviderImpl.java:299)
> at
> org.netbeans.modules.gradle.ActionProviderImpl.invokeProjectAction(ActionProviderImpl.java:200)
> at
> org.netbeans.modules.gradle.ActionProviderImpl.invokeAction(ActionProviderImpl.java:128)
> at
> org.netbeans.modules.project.ui.actions.FileAction$3$1.run(FileAction.java:219)
> at
> java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
> at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:764)
> at java.desktop/java.awt.EventQueue.access$500(EventQueue.java:97)
> at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:717)
> at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:711)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:89)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:734)
> at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
> [catch] at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:199)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
> at
> java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90){code}
> I have a problem with the new gradle support. I tried to press F9 for
> "compile File" in a gradle project. The reason why I would like to have
> support for compiling a single file is, because I'm using
> [https://immutables.github.io/] which is a annotation processor for
> generating implementations and builders for an interface. So it is necessary
> to compile the interface, for getting the builder.
> With to other plugin for gradle it was possible, to "compile on save". The
> new official gradle support don't support this feature and I found an issue
> (NETBEANS-680), which implies, that this feature maybe never be supported. I
> can live with that, but I would love to have a shortcut for triggering the
> compilation task.
> My current workaround is clicking on the project and select the task from the
> navigator. This feels very uncomfortable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2350) Null pointer exception while doing auto complete in rule switch block
[
https://issues.apache.org/jira/browse/NETBEANS-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated NETBEANS-2350:
-
Labels: pull-request-available (was: )
> Null pointer exception while doing auto complete in rule switch block
> -
>
> Key: NETBEANS-2350
> URL: https://issues.apache.org/jira/browse/NETBEANS-2350
> Project: NetBeans
> Issue Type: Bug
>Reporter: vikas kumar prabhakar
>Assignee: vikas kumar prabhakar
>Priority: Major
> Labels: pull-request-available
>
> Null pointer exception while doing auto complete in rule switch block
> Code scenario:
> enum Days\{MON, TUES, WED, THUR, FRI};
> private static void test1(Days day) {
> switch (day)
> { case FRI ->
> System.out.println("javaapplication2.JavaApplication2.test1()"); position> --> Auto complete press 'Ctrl+Space' throw Null pointer exception
> }
> }
>
>
> java.lang.NullPointerException
> at
> org.netbeans.modules.java.completion.JavaCompletionTask.insideSwitch(JavaCompletionTask.java:2296)
> at
> org.netbeans.modules.java.completion.JavaCompletionTask.resolve(JavaCompletionTask.java:412)
> at org.netbeans.modules.java.completion.BaseTask.run(BaseTask.java:93)
> at
> org.netbeans.modules.java.completion.JavaCompletionTask.run(JavaCompletionTask.java:60)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
> at
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130)
> at
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
> at
> org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
> at
> org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
> at
> org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
> at
> org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
> Caused: org.netbeans.modules.parsing.spi.ParseException
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:186)
> at org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
> [catch] at
> org.netbeans.modules.editor.java.JavaCompletionProvider$JavaCompletionQuery.query(JavaCompletionProvider.java:193)
> at
> org.netbeans.spi.editor.completion.support.AsyncCompletionTask.run(AsyncCompletionTask.java:198)
> at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
> at
> org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
> at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
> at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2392) Opening type from Go To Type fails
[ https://issues.apache.org/jira/browse/NETBEANS-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated NETBEANS-2392: - Labels: pull-request-available (was: ) > Opening type from Go To Type fails > -- > > Key: NETBEANS-2392 > URL: https://issues.apache.org/jira/browse/NETBEANS-2392 > Project: NetBeans > Issue Type: Bug > Components: java - Navigation, java - Platform >Affects Versions: 10.0 > Environment: Netbeans 10 and 11 > Open JDK 11 > Gradle 5.2.1 >Reporter: Netbeans User 2019 >Assignee: Jan Lahoda >Priority: Critical > Labels: pull-request-available > > It is simply not open a type that it is clicked from dialog and dialog is > closed, but you have to type such type to editor and import it and then click > it from there for sucessful open. > It seems that does not happend for opened project/sub-projects sources, even > seems no issue e.g. with junit or Java SE API sources. > Additionally this is seen from notification after: > java.lang.ClassCastException: class com.sun.tools.javac.code.Type$ClassType > cannot be cast to class com.sun.tools.javac.code.Type$ErrorType > (com.sun.tools.javac.code.Type$ClassType and > com.sun.tools.javac.code.Type$ErrorType are in unnamed module of loader > org.netbeans.StandardModule$OneModuleClassLoader @27597305) > at > org.netbeans.modules.java.source.builder.TreeFactory.Type(TreeFactory.java:863) > at org.netbeans.api.java.source.TreeMaker.Type(TreeMaker.java:1119) > at > org.netbeans.modules.java.classfile.CodeGenerator$TreeBuilder.computeAnnotationTree(CodeGenerator.java:449) > at > org.netbeans.modules.java.classfile.CodeGenerator$TreeBuilder.computeMods(CodeGenerator.java:411) > at > org.netbeans.modules.java.classfile.CodeGenerator$TreeBuilder.visitType(CodeGenerator.java:373) > at > org.netbeans.modules.java.classfile.CodeGenerator$TreeBuilder.visitType(CodeGenerator.java:285) > at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1473) > at > javax.lang.model.util.AbstractElementVisitor6.visit(AbstractElementVisitor6.java:106) > at > org.netbeans.modules.java.classfile.CodeGenerator.generateCode(CodeGenerator.java:275) > at > org.netbeans.modules.java.classfile.CodeGenerator$1.run(CodeGenerator.java:232) > at > org.netbeans.modules.java.classfile.CodeGenerator$1.run(CodeGenerator.java:152) > at org.netbeans.api.java.source.JavaSource$1.run(JavaSource.java:672) > at org.netbeans.api.java.source.JavaSource$1.run(JavaSource.java:662) > at org.netbeans.api.java.source.JavaSource$MultiTask.run(JavaSource.java:501) > at > org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586) > at > org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130) > at > org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114) > at > org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181) > at > org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178) > at > org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153) > at > org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335) > at > org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118) > at > org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67) > at > org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178) > at > org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81) > at > org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:451) > at > org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:422) > at > org.netbeans.api.java.source.JavaSource.runModificationTask(JavaSource.java:683) > at > org.netbeans.modules.java.classfile.CodeGenerator.generateCode(CodeGenerator.java:152) > at > org.netbeans.modules.java.classfile.BinaryElementOpenImpl.open(BinaryElementOpenImpl.java:44) > at > org.netbeans.api.java.source.ui.ElementOpen.binaryOpen(ElementOpen.java:118) > at org.netbeans.api.java.source.ui.ElementOpen.open(ElementOpen.java:99) > at > org.netbeans.modules.java.source.ui.JavaTypeDescription.open(JavaTypeDescription.java:121) > at > org.netbeans.modules.jumpto.type.GoToTypeAction.actionPerformed(GoToTypeAction.java:153) > at org.openide.windows.TopComponent.processKeyBinding(TopComponent.java:1151) > at > java.desktop/javax.swing.JComponent.processKeyBindings(JComponent.java:2962) > at java.desktop/javax.swing.JComponent.processKeyEvent(JComponent.java:2862) > at java.desktop/java.awt.Component.processEvent(Component.java:6
[jira] [Created] (NETBEANS-2445) Need for Netbeans Version schema release for Chocolatey Package
SALES created NETBEANS-2445:
---
Summary: Need for Netbeans Version schema release for Chocolatey
Package
Key: NETBEANS-2445
URL: https://issues.apache.org/jira/browse/NETBEANS-2445
Project: NetBeans
Issue Type: Task
Affects Versions: 11.0, 10.0
Reporter: SALES
h1. Context
I'm a chocolatey package maintainer... and also a big fan of Netbeans. I
recently implemented a dedicated {{Netbeans 11}} package.
Now, the Chocolatey Moderators are faciing a dilemna about the package version
scheme.
I'm about sure your feedback could help a lot.
h1. Question
>From what I could see I looks more convenient to manage separated packages to
>make softwares updates more confortable.
I mean : if I initially installed Netbeans 10, I want to stick on 10, and when
I apply updates, stick on Netbeans 10, *and not upgrade to 11*. From my point
of view it makes the final user update process easier and safer. For example to
better manage plugin compatibilities.
h1. Action
Could yo please tell us your opinion about that on the dedicated ticket :
[https://github.com/chocolatey/chocolatey-package-requests/issues/572]
So we can make the {{Netbeans 11}} available on chocolatey central repo ?
h1. Resources
* Package sources : [https://github.com/adriens/chocolatey-netbeans-11]
* Package moderation issue :
[https://github.com/chocolatey/chocolatey-package-requests/issues/572]
Thank you in advance for your help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Assigned] (NETBEANS-2444) Teste
[ https://issues.apache.org/jira/browse/NETBEANS-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sites & Apps reassigned NETBEANS-2444: -- Assignee: Sites & Apps > Teste > - > > Key: NETBEANS-2444 > URL: https://issues.apache.org/jira/browse/NETBEANS-2444 > Project: NetBeans > Issue Type: Task >Reporter: Sites & Apps >Assignee: Sites & Apps >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-2444) Teste
Sites & Apps created NETBEANS-2444: -- Summary: Teste Key: NETBEANS-2444 URL: https://issues.apache.org/jira/browse/NETBEANS-2444 Project: NetBeans Issue Type: Task Reporter: Sites & Apps -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2443) Can't start profiler
[
https://issues.apache.org/jira/browse/NETBEANS-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
HenryDL updated NETBEANS-2443:
--
Description:
I'm not able to start the NetBeans Profiler for Maven projects.
*Recreate:*
# Create a new Maven Java Application using the IDE.
# Using the IDE add a new JFrame file (it contains a main method that simply
opens the a new JFrame).
# Right-click the new project and select _Profile_.
# This opens a Profiler tab. Do the calibration, then press the Profile button
at the top of the tab. A _Progress_ popup appears thatgets stuck on the message
"Connecting to the target VM...". The _Output_ tab shows a message: "The syntax
of the command is incorrect.".
*Error (in Output tab):*
{noformat}
cd C:\_Code\TEMP_CODE\mavenproject1; "JAVA_HOME=C:\\Program
Files\\Java\\jdk-12" M2_HOME=C:\\_Code\\_TOOLS\\apache-maven-3.6.0 cmd /c
"\"\"C:\\_Code\\_TOOLS\\apache-maven-3.6.0\\bin\\mvn.cmd\"
-Dexec.args=\"-agentpath:\\\"C:/_Code/_TOOLS/netbeans
11.0/profiler/lib/deployed/jdk16/windows-amd64/profilerinterface.dll\\\"=\\\"C:\\_Code\\_TOOLS\\netbeans
11.0\\profiler\\lib\\\",5140,10 -XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=C:\\Users\\Henry\\AppData\\Local\\NetBeans\\Cache\\11.0\\mavencachedirs\\645799279\\org-netbeans-modules-profiler
-classpath %classpath com.mycompany.mavenproject1.NewJFrame\"
-Dexec.executable=\"C:\\Program Files\\Java\\jdk-12\\bin\\java.exe\"
-Dmaven.ext.class.path=\"C:\\_Code\\_TOOLS\\netbeans
11.0\\java\\maven-nblib\\netbeans-eventspy.jar\" -Dfile.encoding=UTF-8
process-classes org.codehaus.mojo:exec-maven-plugin:1.5.0:exec\""
The syntax of the command is incorrect.
{noformat}
was:
*Recreate:*
# Create a new Maven Java Application using the IDE.
# Using the IDE add a new JFrame file (it contains a main method that simply
opens the a new JFrame).
# Right-click the new project and select _Profile_.
# This opens a Profiler tab. Do the calibration, then press the Profile button
at the top of the tab. A _Progress_ popup appears thatgets stuck on the message
"Connecting to the target VM...". The _Output_ tab shows a message: "The syntax
of the command is incorrect.".
*Error (in Output tab):*
{noformat}
cd C:\_Code\TEMP_CODE\mavenproject1; "JAVA_HOME=C:\\Program
Files\\Java\\jdk-12" M2_HOME=C:\\_Code\\_TOOLS\\apache-maven-3.6.0 cmd /c
"\"\"C:\\_Code\\_TOOLS\\apache-maven-3.6.0\\bin\\mvn.cmd\"
-Dexec.args=\"-agentpath:\\\"C:/_Code/_TOOLS/netbeans
11.0/profiler/lib/deployed/jdk16/windows-amd64/profilerinterface.dll\\\"=\\\"C:\\_Code\\_TOOLS\\netbeans
11.0\\profiler\\lib\\\",5140,10 -XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=C:\\Users\\Henry\\AppData\\Local\\NetBeans\\Cache\\11.0\\mavencachedirs\\645799279\\org-netbeans-modules-profiler
-classpath %classpath com.mycompany.mavenproject1.NewJFrame\"
-Dexec.executable=\"C:\\Program Files\\Java\\jdk-12\\bin\\java.exe\"
-Dmaven.ext.class.path=\"C:\\_Code\\_TOOLS\\netbeans
11.0\\java\\maven-nblib\\netbeans-eventspy.jar\" -Dfile.encoding=UTF-8
process-classes org.codehaus.mojo:exec-maven-plugin:1.5.0:exec\""
The syntax of the command is incorrect.
{noformat}
> Can't start profiler
>
>
> Key: NETBEANS-2443
> URL: https://issues.apache.org/jira/browse/NETBEANS-2443
> Project: NetBeans
> Issue Type: Bug
> Components: profiler - Attach, profiler - Base, profiler - Engine,
> profiler - IDE
>Affects Versions: 11.0
> Environment: Windows 10
> NetBeans 11 using Java 12 (tried with 8 also)
>Reporter: HenryDL
>Priority: Major
>
> I'm not able to start the NetBeans Profiler for Maven projects.
> *Recreate:*
> # Create a new Maven Java Application using the IDE.
> # Using the IDE add a new JFrame file (it contains a main method that simply
> opens the a new JFrame).
> # Right-click the new project and select _Profile_.
> # This opens a Profiler tab. Do the calibration, then press the Profile
> button at the top of the tab. A _Progress_ popup appears thatgets stuck on
> the message "Connecting to the target VM...". The _Output_ tab shows a
> message: "The syntax of the command is incorrect.".
> *Error (in Output tab):*
> {noformat}
> cd C:\_Code\TEMP_CODE\mavenproject1; "JAVA_HOME=C:\\Program
> Files\\Java\\jdk-12" M2_HOME=C:\\_Code\\_TOOLS\\apache-maven-3.6.0 cmd /c
> "\"\"C:\\_Code\\_TOOLS\\apache-maven-3.6.0\\bin\\mvn.cmd\"
> -Dexec.args=\"-agentpath:\\\"C:/_Code/_TOOLS/netbeans
> 11.0/profiler/lib/deployed/jdk16/windows-amd64/profilerinterface.dll\\\"=\\\"C:\\_Code\\_TOOLS\\netbeans
> 11.0\\profiler\\lib\\\",5140,10 -XX:+HeapDumpOnOutOfMemoryError
> -XX:HeapDumpPath=C:\\Users\\Henry\\AppData\\Local\\NetBeans\\Cache\\11.0\\mavencachedirs\\645799279\\org-netbeans-modules-profiler
> -classpath %classpath com.mycompany.mavenproject1.NewJFrame\"
> -Dexec.executable=\"C:\\Program Files\\Ja
[jira] [Created] (NETBEANS-2443) Can't start profiler
HenryDL created NETBEANS-2443:
-
Summary: Can't start profiler
Key: NETBEANS-2443
URL: https://issues.apache.org/jira/browse/NETBEANS-2443
Project: NetBeans
Issue Type: Bug
Components: profiler - Attach, profiler - Base, profiler - Engine,
profiler - IDE
Affects Versions: 11.0
Environment: Windows 10
NetBeans 11 using Java 12 (tried with 8 also)
Reporter: HenryDL
*Recreate:*
# Create a new Maven Java Application using the IDE.
# Using the IDE add a new JFrame file (it contains a main method that simply
opens the a new JFrame).
# Right-click the new project and select _Profile_.
# This opens a Profiler tab. Do the calibration, then press the Profile button
at the top of the tab. A _Progress_ popup appears thatgets stuck on the message
"Connecting to the target VM...". The _Output_ tab shows a message: "The syntax
of the command is incorrect.".
*Error (in Output tab):*
{noformat}
cd C:\_Code\TEMP_CODE\mavenproject1; "JAVA_HOME=C:\\Program
Files\\Java\\jdk-12" M2_HOME=C:\\_Code\\_TOOLS\\apache-maven-3.6.0 cmd /c
"\"\"C:\\_Code\\_TOOLS\\apache-maven-3.6.0\\bin\\mvn.cmd\"
-Dexec.args=\"-agentpath:\\\"C:/_Code/_TOOLS/netbeans
11.0/profiler/lib/deployed/jdk16/windows-amd64/profilerinterface.dll\\\"=\\\"C:\\_Code\\_TOOLS\\netbeans
11.0\\profiler\\lib\\\",5140,10 -XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=C:\\Users\\Henry\\AppData\\Local\\NetBeans\\Cache\\11.0\\mavencachedirs\\645799279\\org-netbeans-modules-profiler
-classpath %classpath com.mycompany.mavenproject1.NewJFrame\"
-Dexec.executable=\"C:\\Program Files\\Java\\jdk-12\\bin\\java.exe\"
-Dmaven.ext.class.path=\"C:\\_Code\\_TOOLS\\netbeans
11.0\\java\\maven-nblib\\netbeans-eventspy.jar\" -Dfile.encoding=UTF-8
process-classes org.codehaus.mojo:exec-maven-plugin:1.5.0:exec\""
The syntax of the command is incorrect.
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-519) Bump Eclipse JGit dependency to latest version
[ https://issues.apache.org/jira/browse/NETBEANS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823139#comment-16823139 ] Agly commented on NETBEANS-519: --- JGit is not at version 5.3.0. It is becoming more difficult to use NetBeans due to issues with the older JGit implementation. I tried building from source and updating my local version to use JGit 5.3.0. Everything builds, but the OSGI framework can't find some of the new dependencies that 5.3.0 has like org.bouncycastle. I added those jars to the "ide/modules" directory, but still it can't find them for some reason. I am not familiar with OSGI, so... I have no choice but to abandon NetBeans for my current development until JGit is updated (or if NETBEANS-2122 ever gets implemented). > Bump Eclipse JGit dependency to latest version > -- > > Key: NETBEANS-519 > URL: https://issues.apache.org/jira/browse/NETBEANS-519 > Project: NetBeans > Issue Type: Improvement > Components: versioncontrol - Git >Affects Versions: 8.2 >Reporter: Christian Bourque >Assignee: Christian Bourque >Priority: Major > Labels: pull-request-available > Time Spent: 6h 50m > Remaining Estimate: 0h > > The current JGit dependency bundled with NetBeans 8.2 is 3 years old and > missing all the newest Git features! This would also be a good time to remove > the old JGit Java 7 NetBeans module... > This would upgrade the current dependency from version 3.6.2 to 4.11.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-519) Bump Eclipse JGit dependency to latest version
[ https://issues.apache.org/jira/browse/NETBEANS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823139#comment-16823139 ] Agly edited comment on NETBEANS-519 at 4/22/19 2:32 PM: JGit is now at version 5.3.0. It is becoming more difficult to use NetBeans due to issues with the older JGit implementation. I tried building from source and updating my local version to use JGit 5.3.0. Everything builds, but the OSGI framework can't find some of the new dependencies that 5.3.0 has like org.bouncycastle. I added those jars to the "ide/modules" directory, but still it can't find them for some reason. I am not familiar with OSGI, so... I have no choice but to abandon NetBeans for my current development until JGit is updated (or if NETBEANS-2122 ever gets implemented). was (Author: agly): JGit is not at version 5.3.0. It is becoming more difficult to use NetBeans due to issues with the older JGit implementation. I tried building from source and updating my local version to use JGit 5.3.0. Everything builds, but the OSGI framework can't find some of the new dependencies that 5.3.0 has like org.bouncycastle. I added those jars to the "ide/modules" directory, but still it can't find them for some reason. I am not familiar with OSGI, so... I have no choice but to abandon NetBeans for my current development until JGit is updated (or if NETBEANS-2122 ever gets implemented). > Bump Eclipse JGit dependency to latest version > -- > > Key: NETBEANS-519 > URL: https://issues.apache.org/jira/browse/NETBEANS-519 > Project: NetBeans > Issue Type: Improvement > Components: versioncontrol - Git >Affects Versions: 8.2 >Reporter: Christian Bourque >Assignee: Christian Bourque >Priority: Major > Labels: pull-request-available > Time Spent: 6h 50m > Remaining Estimate: 0h > > The current JGit dependency bundled with NetBeans 8.2 is 3 years old and > missing all the newest Git features! This would also be a good time to remove > the old JGit Java 7 NetBeans module... > This would upgrade the current dependency from version 3.6.2 to 4.11.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-2442) java.lang.ClassCastException: class org.apache.lucene.codecs.lucene50.Lucene50PostingsFormat
Alex O'Ree created NETBEANS-2442: Summary: java.lang.ClassCastException: class org.apache.lucene.codecs.lucene50.Lucene50PostingsFormat Key: NETBEANS-2442 URL: https://issues.apache.org/jira/browse/NETBEANS-2442 Project: NetBeans Issue Type: Bug Affects Versions: 11.0 Reporter: Alex O'Ree I've seen the following on NB8 and recently started getting it on NB11. I'm not too sure what's causing this but I figured I'd report it anyhow. I don't think it's caused by a plugin given the stack trace. java.lang.ClassCastException: class org.apache.lucene.codecs.lucene50.Lucene50PostingsFormat at java.base/java.lang.Class.asSubclass(Class.java:3593) at org.apache.lucene.util.SPIClassIterator.next(SPIClassIterator.java:158) at org.apache.lucene.util.NamedSPILoader.reload(NamedSPILoader.java:70) at org.apache.lucene.util.NamedSPILoader.(NamedSPILoader.java:51) at org.apache.lucene.util.NamedSPILoader.(NamedSPILoader.java:38) at org.apache.lucene.codecs.PostingsFormat$Holder.(PostingsFormat.java:49) Caused: java.lang.ExceptionInInitializerError at org.apache.lucene.codecs.PostingsFormat.forName(PostingsFormat.java:112) at org.apache.lucene.codecs.lucene54.Lucene54Codec.(Lucene54Codec.java:161) at org.apache.lucene.codecs.lucene54.Lucene54Codec.(Lucene54Codec.java:81) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488) at java.base/java.lang.Class.newInstance(Class.java:560) at org.apache.lucene.util.NamedSPILoader.reload(NamedSPILoader.java:72) at org.apache.lucene.util.NamedSPILoader.(NamedSPILoader.java:49) at org.apache.lucene.util.NamedSPILoader.(NamedSPILoader.java:38) at org.apache.lucene.codecs.Codec$Holder.(Codec.java:47) at org.apache.lucene.codecs.Codec.getDefault(Codec.java:140) at org.apache.lucene.index.LiveIndexWriterConfig.(LiveIndexWriterConfig.java:120) at org.apache.lucene.index.IndexWriterConfig.(IndexWriterConfig.java:140) at org.apache.maven.index.context.NexusIndexWriter.defaultConfig(NexusIndexWriter.java:62) at org.apache.maven.index.context.DefaultIndexingContext.getWriterConfig(DefaultIndexingContext.java:543) at org.apache.maven.index.context.DefaultIndexingContext.openAndWarmup(DefaultIndexingContext.java:531) at org.apache.maven.index.context.DefaultIndexingContext.prepareIndex(DefaultIndexingContext.java:247) at org.apache.maven.index.context.DefaultIndexingContext.(DefaultIndexingContext.java:162) at org.apache.maven.index.context.DefaultIndexingContext.(DefaultIndexingContext.java:172) at org.apache.maven.index.context.DefaultIndexingContext.(DefaultIndexingContext.java:183) at org.apache.maven.index.DefaultIndexer.createIndexingContext(DefaultIndexer.java:86) at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl.addIndexingContextForced(NexusRepositoryIndexerImpl.java:277) at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl.loadIndexingContext2(NexusRepositoryIndexerImpl.java:340) at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl.access$700(NexusRepositoryIndexerImpl.java:122) at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl$3.run(NexusRepositoryIndexerImpl.java:657) at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl$3.run(NexusRepositoryIndexerImpl.java:652) at org.netbeans.modules.openide.util.DefaultMutexImplementation.writeAccess(DefaultMutexImplementation.java:229) at org.openide.util.Mutex.writeAccess(Mutex.java:246) at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl.indexRepo(NexusRepositoryIndexerImpl.java:652) at org.netbeans.modules.maven.indexer.api.RepositoryIndexer.indexRepo(RepositoryIndexer.java:42) at org.netbeans.modules.maven.ProjectOpenedHookImpl$2.run(ProjectOpenedHookImpl.java:207) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418) at org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45) at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://
[jira] [Updated] (NETBEANS-2274) Options Dialog - Panel "Fonts & Colors" - Syntax Pane relies on undocumented ActionEvent#getModifiers behavior
[
https://issues.apache.org/jira/browse/NETBEANS-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated NETBEANS-2274:
-
Labels: pull-request-available (was: )
> Options Dialog - Panel "Fonts & Colors" - Syntax Pane relies on undocumented
> ActionEvent#getModifiers behavior
> --
>
> Key: NETBEANS-2274
> URL: https://issues.apache.org/jira/browse/NETBEANS-2274
> Project: NetBeans
> Issue Type: Bug
> Components: editor - Options
>Affects Versions: 11.0
>Reporter: Matthias Bläsing
>Assignee: Matthias Bläsing
>Priority: Major
> Labels: pull-request-available
> Attachments: Bildschirmfoto_2019-03-18_21-59-36.png
>
>
> In the Options Dialog, the Panel "Fonts & Colors" and there the subpanel
> Syntax Pane relies on undocumented ActionEvent#getModifiers behavior.
> The constructor of ActionEvent:
> [https://docs.oracle.com/javase/8/docs/api/java/awt/event/ActionEvent.html#ActionEvent-java.lang.Object-int-java.lang.String-int-]
> Only talks about modifier keys as parameter options:
> {quote}{{modifiers}} - The modifier keys down during event (shift, ctrl, alt,
> meta). Passing negative parameter is not recommended. Zero value means that
> no modifiers were passed
> {quote}
> The code in the panel checks for the mask for mouse button 1:
> {code:java}
> if(evt.getModifiers() == InputEvent.BUTTON1_MASK) { // mouse
> clicked
> updateLanguageCombobox();
> }{code}
> On Ubuntu 18.10, OpenJDK 1.8u191:
> {noformat}
> openjdk version "1.8.0_191"
> OpenJDK Runtime Environment (build 1.8.0_191-8u191-b12-2ubuntu0.18.10.1-b12)
> OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode){noformat}
> As the keyboard handling for the ComboBox is also explicitly coded in the
> panel:
> {code:java}
> cbLanguage.addKeyListener(new java.awt.event.KeyAdapter() {
> @Override
> public void keyReleased(KeyEvent evt) {
> if (evt.getKeyCode() == KeyEvent.VK_ENTER || evt.getKeyCode()
> == KeyEvent.VK_SPACE) {
> updateLanguageCombobox();
> }
> }
> });{code}
> Both special cases should be removed and replaced with the default combobox
> behavior.
> The attached screenshot shows the broken state (combobox content for language
> does not match displayed language).
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2158) No error when accessing undeclared or private properties
[
https://issues.apache.org/jira/browse/NETBEANS-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabian Kleinhans updated NETBEANS-2158:
---
Affects Version/s: 11.0
This problem still exists in NetBeans 11.
> No error when accessing undeclared or private properties
>
>
> Key: NETBEANS-2158
> URL: https://issues.apache.org/jira/browse/NETBEANS-2158
> Project: NetBeans
> Issue Type: Bug
> Components: php - Code Analysis
>Affects Versions: 10.0, 11.0
>Reporter: Fabian Kleinhans
>Priority: Major
> Labels: php, php7
> Attachments: code.png
>
>
> Hi,
> I just switched from Netbeans 8.2 to 10 some days ago. Now I wonder why
> accessing undeclared or private properties in my PHP files are not marked in
> the code like in 8.2. E.g.:
> {code:java}
> class A {
>
> private $bar;
>
> public function __construct() {
> $this->bar = 1;
> }
> }
> $foo = new A();
> echo $foo->bar;
> echo $foo->bar2;
> {code}
> This code has green status saying "No errors". The project is set as
> PHP-project.
> Have I missed a setting? I spent hours of research but didn't find a solution.
> Thanks for any hint!
> Fabian
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
