[jira] [Resolved] (NETBEANS-3101) Can't launch (and connect) NetBeans from node
[
https://issues.apache.org/jira/browse/NETBEANS-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach resolved NETBEANS-3101.
---
Fix Version/s: 12.2
Resolution: Fixed
> Can't launch (and connect) NetBeans from node
> -
>
> Key: NETBEANS-3101
> URL: https://issues.apache.org/jira/browse/NETBEANS-3101
> Project: NetBeans
> Issue Type: Bug
> Components: platform - Launchers&CLI
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Minor
> Fix For: 12.2
>
>
>
> I am trying to connect to a *NetBeans* based application from _Visual Studio_
> - aka _Electron_ - aka *node*. Somehow the *node* mangles network setup and
> the InetAddress.getHostAddress() isn't the same. To reproduce create
> following structure of files:
> {code:java}
> $ ls -l | cut -c50-
> dump.hprof
> nb.js
> nb.sh
> netbeans -> /home/devel/bin/netbeans/bin/netbeans
> $ cat nb.sh
> ./netbeans 'dump.hprof'
> $ cat nb.js
> var exec = require("child_process").execFile;
> let path = './netbeans';let vvm = exec(path, [ 'dump.hprof' ]){code}
> Then start *./netbeans* on background and wait for the GUI to launch. Then do
> following from command line:
> {code:java}
> ./jvm.sh
> {code}
> The dump.hprof file opens in the the GUI. Close it and try the same via
> *node.js*:
> {code:java}
> node ./jvm.js
> {code}
> The heap dump isn't shown (on my computer), rather a warning dialog appears.
> Result of node and shell script disagreeing on what is local host address.
> One is using IPv6 and one IPv4.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5499) Platform apps cannot connect using HTTP protocol on JDK16
[
https://issues.apache.org/jira/browse/NETBEANS-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308730#comment-17308730
]
Jaroslav Tulach commented on NETBEANS-5499:
---
There is a general problem with {{URLStreamHandlerFactories}} in containers
like NetBeans/Equinox/Felix - they all use reflection and it is going to stop
working in some future JDK. Maybe the faulty behavior in JDK-16 is a "teaser"
for days to come.
> Platform apps cannot connect using HTTP protocol on JDK16
> -
>
> Key: NETBEANS-5499
> URL: https://issues.apache.org/jira/browse/NETBEANS-5499
> Project: NetBeans
> Issue Type: Bug
> Components: core
>Affects Versions: 12.3
>Reporter: Svatopluk Dedic
>Priority: Major
>
> I've found out that my platfom application does not work at all with HTTP
> protocol when run on JDK 16. The error thrown is:
> {code:java}
> INFO
> [org.netbeans.modules.autoupdate.updateproviders.AutoupdateCatalogFactory]:
> Unknown protocol: http
> java.lang.IllegalStateException: Unknown protocol: http
> at
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:373)
> at java.base/java.net.URL.(URL.java:701)
> Caused: java.net.MalformedURLException: Unknown protocol: http
> at java.base/java.net.URL.(URL.java:706)
> at java.base/java.net.URL.(URL.java:568)
> at java.base/java.net.URL.(URL.java:515)
> [catch] at
> org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogFactory.createUpdateProvider(AutoupdateCatalogFactory.java:98)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:567)
> at
> org.netbeans.core.startup.layers.BinaryFS$AttrImpl$MethodAndParams.invoke(BinaryFS.java:730)
> at
> org.netbeans.core.startup.layers.BinaryFS$AttrImpl.getValue(BinaryFS.java:660)
> at
> org.netbeans.core.startup.layers.BinaryFS$BFSBase.getAttribute(BinaryFS.java:506)
> {code}
> No URL with http(s): protocol can be even *parsed*.
> I managed to isolate the issue - it is caused by *Apache Felix* library
> included in NB platform that provides
> {{org.osgi.framework.launch.FrameworkFactory}} token.
> The bug *does not occur* in NetBeans IDE, which has a direct dependency
> (Needs: declaration) on *org.netbeans.netbinox* module from its *ide.kit*
> module. In NetBeans, Netbinox loads and installs its URLStreamHandlerFactory
> ({{org.eclipse.osgi.framework.internal.protocol.StreamHandlerFactory}})
> In a platform app that does not load (need) Netbinox, the Felix library
> installs its own URLStreamHandleFactory (
> {{org.apache.felix.framework.URLHandlers}}), that creates *proxies*. So USHF
> for http *is* actually created, but it afterwards throws
> {{MalformedURLException}} on any http: url spec.
> The bug does not occur on earlier JDKs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5500) URLStreamFactory registration violates JDK9+ reflection restrictions
Jaroslav Tulach created NETBEANS-5500:
-
Summary: URLStreamFactory registration violates JDK9+ reflection
restrictions
Key: NETBEANS-5500
URL: https://issues.apache.org/jira/browse/NETBEANS-5500
Project: NetBeans
Issue Type: Bug
Components: platform - Module System
Affects Versions: 9.0
Reporter: Jaroslav Tulach
If you run NetBeans on JDK9+ you'll see:
{code:java}
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.netbeans.ProxyURLStreamHandlerFactory
(file:/netbeans/nbbuild/netbeans/platform/lib/boot.jar) to field
java.net.URL.handler
WARNING: Please consider reporting this to the maintainers of
org.netbeans.ProxyURLStreamHandlerFactory
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release {code}
There is a new API that one can use to register (most of) the factories on
JDK9+:
[https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/net/spi/URLStreamHandlerProvider.html]
We should use it as once the JDK is going to ban the illegal access operations
and then it is better to be ready.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5468) Gradle parent / containment queries inconsistent
[
https://issues.apache.org/jira/browse/NETBEANS-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-5468:
--
Summary: Gradle parent / containment queries inconsistent (was: Graldle
parent / containment queries inconsistent)
> Gradle parent / containment queries inconsistent
>
>
> Key: NETBEANS-5468
> URL: https://issues.apache.org/jira/browse/NETBEANS-5468
> Project: NetBeans
> Issue Type: Improvement
> Components: projects - Gradle Java EE
>Reporter: Svatopluk Dedic
>Assignee: Laszlo Kishalmi
>Priority: Major
>
> There are queries that power {{ProjectUtils.rootOf}}, {{parentOf}} and
> {{containedSubprojects}}. Their behaviour is largely inconsistent of the root
> project is not opened.
> * subproject B that resides in a direct child of root project A reports A as
> parent
> * but A does not report B as subproject, unless A opens and is trusted
> Project API in general requires that project services does not depend on the
> project being opened in the UI, so this is rather a bug. Given that gradle is
> virtually unable to statically determine project contents or hierarchy, it
> could be clarified in {{ParentProjectProvider}} etc Javadocs that the
> behaviour of unopened project may be reduced, i.e. parent known, but
> subprojects unknown, or something like that. Also it should be documented how
> to programmatically get the system 'into good shape' when the API user wants
> to inspect the hierarchy.
> Maybethe effect of trust and 'opennes' on queries could be discussed also
> with [~jtulach] on dev mailing list.
> Other bug is that if I have
> * root project A
> ** folder F
> *** subproject C
> such as there's {{include :folder:C}} in {{settings.gradle}}, then even
> {{ProjectUtils.parentOf(c)}} returns null - again unless A is opened in the
> UI. This is most probably a bug, since at the same time
> {{ProjectUtils.rootOf(c)}} yields A.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5400) Custom Platform Integration test fail if non converging maven artefacts
[
https://issues.apache.org/jira/browse/NETBEANS-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296800#comment-17296800
]
Jaroslav Tulach commented on NETBEANS-5400:
---
I don't know off-hand. I would have to debug the behavior.
> Custom Platform Integration test fail if non converging maven artefacts
> ---
>
> Key: NETBEANS-5400
> URL: https://issues.apache.org/jira/browse/NETBEANS-5400
> Project: NetBeans
> Issue Type: Bug
> Components: platform - Other
>Affects Versions: 12.2
>Reporter: Eric Barboni
>Priority: Major
>
> Hi, I found an issue on the
> /harness/nbjunit/src/org/netbeans/junit/NbModuleSuite.java.
> I don't know if this is a common use case but if you have two module with
> Maven-Class-Path entry in their manifest you will have an issue during the
> test preparation.
> I have created the following showcase:
> [https://github.com/ebarboni/nbappmaventest]
> wrapper 2 incorporate lucene 3.6.2 and wrapper 1 lucene 5.5.5.
> It build and run but cannot be tested.
> {code}
> java.io.IOException: no match for org.apache.lucene:lucene-core:3.6.2 found
> at org.netbeans.junit.NbModuleSuite$S.rewrite(NbModuleSuite.java:1129)
> at
> org.netbeans.junit.NbModuleSuite$S.turnClassPathModules(NbModuleSuite.java:1094)
> {code}
>
> I have no PR yet because I don't know to handle that.
> If possible may I have feedback from [~jtulach] or [~sdedic].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5380) Background scanning spends significant time in o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner
[
https://issues.apache.org/jira/browse/NETBEANS-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293389#comment-17293389
]
Jaroslav Tulach commented on NETBEANS-5380:
---
Everything seems to work in NetBeans 12.0, 12.3 as well as with [your
patch|https://github.com/matthiasblaesing/netbeans/commit/460042be723b28b430f88c77c1ee7ab18f364892].
To reproduce try:
{code:java}
graal/truffle$ mx build
graal/truffle$ mx netbeansinit
graal/truffle$ netbeans --open
src/com.oracle.truffle.api/src/com/oracle/truffle/api/frame/Frame.java
{code}
and when the {{Frame.java}} file is opened in the editor, press _Ctrl-Shift-1_.
It always opens the right project. E.g.
{{graal/truffle/src/com.oracle.truffle.api}} in case of 12.0 and
{{graal/truffle}} in case of new NetBeans. Thanks a lot for the fix, Matthias!
> Background scanning spends significant time in
> o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner
> --
>
> Key: NETBEANS-5380
> URL: https://issues.apache.org/jira/browse/NETBEANS-5380
> Project: NetBeans
> Issue Type: Bug
> Components: java - Source
>Affects Versions: Next
>Reporter: Matthias Bläsing
>Assignee: Jaroslav Tulach
>Priority: Major
> Attachments: sample1.npss, sample2.npss
>
>
> I opened an angular project into an IDE build from recent master. I observed,
> that a very (> 20 minutes) long background scanning times could be observed.
> I first used visual VM and then the netbeans internal profiler to try to
> narrow it down.
> *Profile*
> I'll attach two self profiles, both show the same picture, so I'll
> concentrate on _sample2.npss_:
> There are 9 entries in the self profile, that show CPU times > 190s. From
> these 8 are waiting in native code and thus false positives:
> - ReferenceHandler
> - FileSystemWatchService
> - process reaper (3x)
> - StreamTerm.Output (2x)
> - pool-5-thread-1 (From the trace LSP integration)
> The one trace, that is connected to the observed scanning and is in java code
> is _RepositoryUpdater.worker._ Breaking this down shows, that, although the
> forward calls split into two branches, both hit:
> _org.netbeans.modules.java.mx.project.SuiteFileOwnerQueryImpl#getOwner_
> That method is responsible for 178s CPU time. No other FileOwnerQueryImpl
> shows up in the trace, and thus this leads me to the conclusion, that this is
> fishy.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5380) Background scanning spends significant time in o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner
[ https://issues.apache.org/jira/browse/NETBEANS-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293366#comment-17293366 ] Jaroslav Tulach commented on NETBEANS-5380: --- I'll do some testing, but the solution seems to be very promising. Thanks for bringing it up. > Background scanning spends significant time in > o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner > -- > > Key: NETBEANS-5380 > URL: https://issues.apache.org/jira/browse/NETBEANS-5380 > Project: NetBeans > Issue Type: Bug > Components: java - Source >Affects Versions: Next >Reporter: Matthias Bläsing >Assignee: Jaroslav Tulach >Priority: Major > Attachments: sample1.npss, sample2.npss > > > I opened an angular project into an IDE build from recent master. I observed, > that a very (> 20 minutes) long background scanning times could be observed. > I first used visual VM and then the netbeans internal profiler to try to > narrow it down. > *Profile* > I'll attach two self profiles, both show the same picture, so I'll > concentrate on _sample2.npss_: > There are 9 entries in the self profile, that show CPU times > 190s. From > these 8 are waiting in native code and thus false positives: > - ReferenceHandler > - FileSystemWatchService > - process reaper (3x) > - StreamTerm.Output (2x) > - pool-5-thread-1 (From the trace LSP integration) > The one trace, that is connected to the observed scanning and is in java code > is _RepositoryUpdater.worker._ Breaking this down shows, that, although the > forward calls split into two branches, both hit: > _org.netbeans.modules.java.mx.project.SuiteFileOwnerQueryImpl#getOwner_ > That method is responsible for 178s CPU time. No other FileOwnerQueryImpl > shows up in the trace, and thus this leads me to the conclusion, that this is > fishy. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5380) Background scanning spends significant time in o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner
[
https://issues.apache.org/jira/browse/NETBEANS-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289757#comment-17289757
]
Jaroslav Tulach edited comment on NETBEANS-5380 at 2/24/21, 8:07 AM:
-
I could modify the {{mx netbeansinit}} generator to leave a note in the
{{nbproject/project.properties}} to skip ownership, if there is a project
relative to this Ant project. Then the workflow would be:
* use global query and find the Ant project
* the Ant project would find the MX project on NetBeans 12.3 and delegate to it
* the Ant project wouldn't find anything on older NetBeans and would handle
the ownership
This way we could get rid of the global mx.FileOwnerQuery and let the price be
paid only by those who are dealing with {{mx}} built projects.
was (Author: jtulach):
I could modify the {{mx netbeansinit}} generator to leave a note in the
{{nbproject/project.properties}} to skip ownership, if there is a project
relative to this Ant project. Then the workflow would be:
* use global query and find the Ant project
* the Ant project would find the MX project on NetBeans 12.3 and delegate to it
* the Ant project wouldn't find anything on older NetBeans and would handle
the ownership
This way we could get rid of the global mx.FileOwnerQuery and let the price be
payed only for those who are dealing with {{mx}} built projects.
> Background scanning spends significant time in
> o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner
> --
>
> Key: NETBEANS-5380
> URL: https://issues.apache.org/jira/browse/NETBEANS-5380
> Project: NetBeans
> Issue Type: Bug
> Components: java - Source
>Affects Versions: Next
>Reporter: Matthias Bläsing
>Assignee: Jaroslav Tulach
>Priority: Major
> Attachments: sample1.npss, sample2.npss
>
>
> I opened an angular project into an IDE build from recent master. I observed,
> that a very (> 20 minutes) long background scanning times could be observed.
> I first used visual VM and then the netbeans internal profiler to try to
> narrow it down.
> *Profile*
> I'll attach two self profiles, both show the same picture, so I'll
> concentrate on _sample2.npss_:
> There are 9 entries in the self profile, that show CPU times > 190s. From
> these 8 are waiting in native code and thus false positives:
> - ReferenceHandler
> - FileSystemWatchService
> - process reaper (3x)
> - StreamTerm.Output (2x)
> - pool-5-thread-1 (From the trace LSP integration)
> The one trace, that is connected to the observed scanning and is in java code
> is _RepositoryUpdater.worker._ Breaking this down shows, that, although the
> forward calls split into two branches, both hit:
> _org.netbeans.modules.java.mx.project.SuiteFileOwnerQueryImpl#getOwner_
> That method is responsible for 178s CPU time. No other FileOwnerQueryImpl
> shows up in the trace, and thus this leads me to the conclusion, that this is
> fishy.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5380) Background scanning spends significant time in o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner
[
https://issues.apache.org/jira/browse/NETBEANS-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289757#comment-17289757
]
Jaroslav Tulach commented on NETBEANS-5380:
---
I could modify the {{mx netbeansinit}} generator to leave a note in the
{{nbproject/project.properties}} to skip ownership, if there is a project
relative to this Ant project. Then the workflow would be:
* use global query and find the Ant project
* the Ant project would find the MX project on NetBeans 12.3 and delegate to it
* the Ant project wouldn't find anything on older NetBeans and would handle
the ownership
This way we could get rid of the global mx.FileOwnerQuery and let the price be
payed only for those who are dealing with {{mx}} built projects.
> Background scanning spends significant time in
> o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner
> --
>
> Key: NETBEANS-5380
> URL: https://issues.apache.org/jira/browse/NETBEANS-5380
> Project: NetBeans
> Issue Type: Bug
> Components: java - Source
>Affects Versions: Next
>Reporter: Matthias Bläsing
>Assignee: Jaroslav Tulach
>Priority: Major
> Attachments: sample1.npss, sample2.npss
>
>
> I opened an angular project into an IDE build from recent master. I observed,
> that a very (> 20 minutes) long background scanning times could be observed.
> I first used visual VM and then the netbeans internal profiler to try to
> narrow it down.
> *Profile*
> I'll attach two self profiles, both show the same picture, so I'll
> concentrate on _sample2.npss_:
> There are 9 entries in the self profile, that show CPU times > 190s. From
> these 8 are waiting in native code and thus false positives:
> - ReferenceHandler
> - FileSystemWatchService
> - process reaper (3x)
> - StreamTerm.Output (2x)
> - pool-5-thread-1 (From the trace LSP integration)
> The one trace, that is connected to the observed scanning and is in java code
> is _RepositoryUpdater.worker._ Breaking this down shows, that, although the
> forward calls split into two branches, both hit:
> _org.netbeans.modules.java.mx.project.SuiteFileOwnerQueryImpl#getOwner_
> That method is responsible for 178s CPU time. No other FileOwnerQueryImpl
> shows up in the trace, and thus this leads me to the conclusion, that this is
> fishy.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5380) Background scanning spends significant time in o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner
[
https://issues.apache.org/jira/browse/NETBEANS-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288180#comment-17288180
]
Jaroslav Tulach edited comment on NETBEANS-5380 at 2/23/21, 7:58 AM:
-
OK, that'd be ideal. However historically the Graal project provided {{mx
netbeansinit}} support which generates 8.2 Ant {{nbproject/project.xml}}
projects based on content of {{suite/mx.suite/suite.py}}. They were usually
located in {{suite/src/*/nbproject}} directories.
My goal with the new {{java.mx.projects}} support is to take over the old
system and ignore the old projects if there is a {{mx.*/suite.py}} above. To do
that I created own global {{FileOwnerQueryImpl}}.
Of course, it is not acceptable to slow down 99% of users because of
functionality they don't want. I'll try to marry the two goals.
was (Author: jtulach):
OK, that'd be ideal.
> Background scanning spends significant time in
> o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner
> --
>
> Key: NETBEANS-5380
> URL: https://issues.apache.org/jira/browse/NETBEANS-5380
> Project: NetBeans
> Issue Type: Bug
> Components: java - Source
>Affects Versions: Next
>Reporter: Matthias Bläsing
>Assignee: Jaroslav Tulach
>Priority: Major
> Attachments: sample1.npss, sample2.npss
>
>
> I opened an angular project into an IDE build from recent master. I observed,
> that a very (> 20 minutes) long background scanning times could be observed.
> I first used visual VM and then the netbeans internal profiler to try to
> narrow it down.
> *Profile*
> I'll attach two self profiles, both show the same picture, so I'll
> concentrate on _sample2.npss_:
> There are 9 entries in the self profile, that show CPU times > 190s. From
> these 8 are waiting in native code and thus false positives:
> - ReferenceHandler
> - FileSystemWatchService
> - process reaper (3x)
> - StreamTerm.Output (2x)
> - pool-5-thread-1 (From the trace LSP integration)
> The one trace, that is connected to the observed scanning and is in java code
> is _RepositoryUpdater.worker._ Breaking this down shows, that, although the
> forward calls split into two branches, both hit:
> _org.netbeans.modules.java.mx.project.SuiteFileOwnerQueryImpl#getOwner_
> That method is responsible for 178s CPU time. No other FileOwnerQueryImpl
> shows up in the trace, and thus this leads me to the conclusion, that this is
> fishy.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5380) Background scanning spends significant time in o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner
[ https://issues.apache.org/jira/browse/NETBEANS-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288180#comment-17288180 ] Jaroslav Tulach commented on NETBEANS-5380: --- OK, that'd be ideal. > Background scanning spends significant time in > o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner > -- > > Key: NETBEANS-5380 > URL: https://issues.apache.org/jira/browse/NETBEANS-5380 > Project: NetBeans > Issue Type: Bug > Components: java - Source >Affects Versions: Next >Reporter: Matthias Bläsing >Assignee: Jaroslav Tulach >Priority: Major > Attachments: sample1.npss, sample2.npss > > > I opened an angular project into an IDE build from recent master. I observed, > that a very (> 20 minutes) long background scanning times could be observed. > I first used visual VM and then the netbeans internal profiler to try to > narrow it down. > *Profile* > I'll attach two self profiles, both show the same picture, so I'll > concentrate on _sample2.npss_: > There are 9 entries in the self profile, that show CPU times > 190s. From > these 8 are waiting in native code and thus false positives: > - ReferenceHandler > - FileSystemWatchService > - process reaper (3x) > - StreamTerm.Output (2x) > - pool-5-thread-1 (From the trace LSP integration) > The one trace, that is connected to the observed scanning and is in java code > is _RepositoryUpdater.worker._ Breaking this down shows, that, although the > forward calls split into two branches, both hit: > _org.netbeans.modules.java.mx.project.SuiteFileOwnerQueryImpl#getOwner_ > That method is responsible for 178s CPU time. No other FileOwnerQueryImpl > shows up in the trace, and thus this leads me to the conclusion, that this is > fishy. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5380) Background scanning spends significant time in o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner
[
https://issues.apache.org/jira/browse/NETBEANS-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288051#comment-17288051
]
Jaroslav Tulach commented on NETBEANS-5380:
---
It is always good to enable the (although improper) _"Hit Count"_ to see where
the loops occur. Checking the second sample and the RepositoryUpdater.worker
thread I see:
*
org.netbeans.modules.html.editor.lib.api.SyntaxAnalyzerResult$ElementContentFilter.getMasks()
6x
*
org.netbeans.modules.html.editor.lib.api.SyntaxAnalyzerResult$ElementContentFilter.shouldBeFiltered()
3280x
then it goes to:
*
org.netbeans.modules.parsing.spi.indexing.support.QuerySupport.reduceRootsByProjects()
3306x
* org.netbeans.modules.java.mx.project.SuiteFileOwnerQueryImpl.getOwner() 3642x
One option would be to decrease the number of calls to {{getOwner()}} when
parsing. The other is to improve {{mx}} - the problem there is that mx checks
for project two levels deep. A folder is Mx project if it contains {{mx.*}}
subfolder and that folder contains {{suite.py}} file. FileSystems API isn't
particularly fast in checking that.
I'll think about an improvement. Thanks for bug report.
> Background scanning spends significant time in
> o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner
> --
>
> Key: NETBEANS-5380
> URL: https://issues.apache.org/jira/browse/NETBEANS-5380
> Project: NetBeans
> Issue Type: Bug
> Components: java - Source
>Affects Versions: Next
>Reporter: Matthias Bläsing
>Assignee: Jaroslav Tulach
>Priority: Major
> Attachments: sample1.npss, sample2.npss
>
>
> I opened an angular project into an IDE build from recent master. I observed,
> that a very (> 20 minutes) long background scanning times could be observed.
> I first used visual VM and then the netbeans internal profiler to try to
> narrow it down.
> *Profile*
> I'll attach two self profiles, both show the same picture, so I'll
> concentrate on _sample2.npss_:
> There are 9 entries in the self profile, that show CPU times > 190s. From
> these 8 are waiting in native code and thus false positives:
> - ReferenceHandler
> - FileSystemWatchService
> - process reaper (3x)
> - StreamTerm.Output (2x)
> - pool-5-thread-1 (From the trace LSP integration)
> The one trace, that is connected to the observed scanning and is in java code
> is _RepositoryUpdater.worker._ Breaking this down shows, that, although the
> forward calls split into two branches, both hit:
> _org.netbeans.modules.java.mx.project.SuiteFileOwnerQueryImpl#getOwner_
> That method is responsible for 178s CPU time. No other FileOwnerQueryImpl
> shows up in the trace, and thus this leads me to the conclusion, that this is
> fishy.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5339) Let's NetBeans Java Support work with --release X flag
Jaroslav Tulach created NETBEANS-5339:
-
Summary: Let's NetBeans Java Support work with --release X flag
Key: NETBEANS-5339
URL: https://issues.apache.org/jira/browse/NETBEANS-5339
Project: NetBeans
Issue Type: Improvement
Components: java - Source
Affects Versions: 12.0
Reporter: Jaroslav Tulach
Assignee: Jan Lahoda
Since JDK9 there is {{-release}} flag which can specify which JDK API one
wishes to compile against. Time to use it in NetBeans!
Historically NetBeans Java support tries to detect a JDK one is running on and
decrease the requested {{--source}} level to the supported JDK. This is very
annoying and in the context of {{--release}} flag, unnecessary.
Modern {{javac}} compiler have snapshot JDK API for each version since JDK7 to
the latest JDK. Regardless on which version the NetBeans IDE is running, people
should be able to select the right release/target JDK and get errors according
to its API.
By default a specified {{--source}} (by a SourceVersionQuery) should also imply
appropriate {{--release}}. There might be other means how to control both
source as well as release.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Closed] (NETBEANS-4996) Hints in VSCode editor aren't refreshed after successful build
[
https://issues.apache.org/jira/browse/NETBEANS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach closed NETBEANS-4996.
-
Fix Version/s: 12.3
Resolution: Fixed
[PR-2648 |https://github.com/apache/netbeans/pull/2648/]has been integrated and
is available in 12.2 u1 as well as 12.3.
> Hints in VSCode editor aren't refreshed after successful build
> --
>
> Key: NETBEANS-4996
> URL: https://issues.apache.org/jira/browse/NETBEANS-4996
> Project: NetBeans
> Issue Type: Bug
> Components: vscode
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Martin Entlicher
>Priority: Minor
> Labels: pull-request-available
> Fix For: 12.3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After successful Gradle build the hint on {{package}} statement should
> disappear. It doesn't right now. One needs to perform edit (press Enter?) in
> the editor to refresh the hints. To reproduce:
> Create new Gradle project with some (not downloaded) dependencies. Open it in
> VSCode Apache NetBeans Language Server 12.2. There should be hint "Missing
> mandatory classpath entries" on {{package}} statement. Select fix, the build
> is started and finishes successfully. However the hint still remains.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4996) Hints in VSCode editor aren't refreshed after successful build
[
https://issues.apache.org/jira/browse/NETBEANS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach reassigned NETBEANS-4996:
-
Assignee: Martin Entlicher (was: Jan Lahoda)
> Hints in VSCode editor aren't refreshed after successful build
> --
>
> Key: NETBEANS-4996
> URL: https://issues.apache.org/jira/browse/NETBEANS-4996
> Project: NetBeans
> Issue Type: Bug
> Components: vscode
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Martin Entlicher
>Priority: Minor
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After successful Gradle build the hint on {{package}} statement should
> disappear. It doesn't right now. One needs to perform edit (press Enter?) in
> the editor to refresh the hints. To reproduce:
> Create new Gradle project with some (not downloaded) dependencies. Open it in
> VSCode Apache NetBeans Language Server 12.2. There should be hint "Missing
> mandatory classpath entries" on {{package}} statement. Select fix, the build
> is started and finishes successfully. However the hint still remains.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Closed] (NETBEANS-5229) Problems view unusable, polluted with JDK problems
[ https://issues.apache.org/jira/browse/NETBEANS-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach closed NETBEANS-5229. - Fix Version/s: 12.3 Resolution: Fixed [PR-2657|https://github.com/apache/netbeans/pull/2657] integrated as well as backported via [PR-2662|https://github.com/apache/netbeans/pull/2662] into 12.2.1 > Problems view unusable, polluted with JDK problems > -- > > Key: NETBEANS-5229 > URL: https://issues.apache.org/jira/browse/NETBEANS-5229 > Project: NetBeans > Issue Type: Bug > Components: vscode >Affects Versions: 12.2 >Reporter: Martin Balin >Assignee: Jan Lahoda >Priority: Major > Labels: pull-request-available > Fix For: 12.3 > > Attachments: _thumb_38094.png > > Time Spent: 50m > Remaining Estimate: 0h > > Using apache-netbeans-java-12.3.380.vsix, Java 8 via graalVM, Maven Micronaut > application. > Just playing with some simple Java code, occasionally invoking Ctrl+Click to > a JDK class. Each time the JDK code is scanned for problems and added to the > Problems view, eventually showing duplicated items. > Is it necessary to report problems in JDK here at all? Definitely should not > be duplicated (actually multiple occurences of the same class). > *Even worse - the items are being added to the Problems view just by > Ctrl+hover over the class/method!* > See the attached screenshot. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-4996) Hints in VSCode editor aren't refreshed after successful build
[
https://issues.apache.org/jira/browse/NETBEANS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260990#comment-17260990
]
Jaroslav Tulach commented on NETBEANS-4996:
---
Martin Entlicher has created
[PR-2648|https://github.com/apache/netbeans/pull/2648/].
> Hints in VSCode editor aren't refreshed after successful build
> --
>
> Key: NETBEANS-4996
> URL: https://issues.apache.org/jira/browse/NETBEANS-4996
> Project: NetBeans
> Issue Type: Bug
> Components: vscode
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Jan Lahoda
>Priority: Minor
>
> After successful Gradle build the hint on {{package}} statement should
> disappear. It doesn't right now. One needs to perform edit (press Enter?) in
> the editor to refresh the hints. To reproduce:
> Create new Gradle project with some (not downloaded) dependencies. Open it in
> VSCode Apache NetBeans Language Server 12.2. There should be hint "Missing
> mandatory classpath entries" on {{package}} statement. Select fix, the build
> is started and finishes successfully. However the hint still remains.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5215) Progress API use-cases aren't valid
Jaroslav Tulach created NETBEANS-5215:
-
Summary: Progress API use-cases aren't valid
Key: NETBEANS-5215
URL: https://issues.apache.org/jira/browse/NETBEANS-5215
Project: NetBeans
Issue Type: Bug
Components: platform - Progress
Affects Versions: 11.1
Reporter: Jaroslav Tulach
Assignee: Svatopluk Dedic
Looking at
[https://bits.netbeans.org/11.1/javadoc/org-netbeans-api-progress/overview-summary.html]
I see that the documentation hasn't been properly updated to reflect the split
of Progress API and Progress Swing API. For example:
{code:java}
ProgressHandle handle = ProgressHandleFactory.creatHandle("My custom task");
{code}
there is a typo (consider using @codesnippet tag, at least in documentation
inside of classes). Moreover the {{ProgressHandleFactory}} isn't even in the
Progress API!
Various other apichanges entries like showProgressDialogAndRun are also
out of scope and belong to Progress Swing API.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4996) Hints in VSCode editor aren't refreshed after successful build
[
https://issues.apache.org/jira/browse/NETBEANS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17258681#comment-17258681
]
Jaroslav Tulach commented on NETBEANS-4996:
---
I would really need help or at least a hint with respect to this issue.
> Hints in VSCode editor aren't refreshed after successful build
> --
>
> Key: NETBEANS-4996
> URL: https://issues.apache.org/jira/browse/NETBEANS-4996
> Project: NetBeans
> Issue Type: Bug
> Components: vscode
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Jan Lahoda
>Priority: Minor
>
> After successful Gradle build the hint on {{package}} statement should
> disappear. It doesn't right now. One needs to perform edit (press Enter?) in
> the editor to refresh the hints. To reproduce:
> Create new Gradle project with some (not downloaded) dependencies. Open it in
> VSCode Apache NetBeans Language Server 12.2. There should be hint "Missing
> mandatory classpath entries" on {{package}} statement. Select fix, the build
> is started and finishes successfully. However the hint still remains.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-2764) NoClassDefFoundError upon Netbeans 11.1-beta2 startup while network is connected with proxy
[ https://issues.apache.org/jira/browse/NETBEANS-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17257641#comment-17257641 ] Jaroslav Tulach commented on NETBEANS-2764: --- Thanks for cleaning up the JIRA, Tomáši. > NoClassDefFoundError upon Netbeans 11.1-beta2 startup while network is > connected with proxy > --- > > Key: NETBEANS-2764 > URL: https://issues.apache.org/jira/browse/NETBEANS-2764 > Project: NetBeans > Issue Type: Bug > Components: core, platform - Proxy >Affects Versions: 11.1 > Environment: Netbeans 11.1-beta2 > Oracle JDK 8 > Windows 10 >Reporter: Travis >Assignee: Jaroslav Tulach >Priority: Major > Labels: pull-request-available > Fix For: 11.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Immediately upon startup of Netbeans 11.1-beta2 while connected over VPN > (with proxy), I get a notification with the exception below. > This bug is vaguely similar to NETBEANS-1775. Seems like the Netbeans test > suite needs to be augmented with some test coverage for network proxies, to > prevent this type of bug from reappearing again and again? > > org.graalvm.polyglot.PolyglotException: java.lang.NoClassDefFoundError: > com/oracle/truffle/api/library/Library > at > com.oracle.truffle.js.nodes.control.DeletePropertyNode.create(DeletePropertyNode.java:107) > at > com.oracle.truffle.js.nodes.NodeFactory.createDeleteProperty(NodeFactory.java:667) > at > com.oracle.truffle.js.parser.GraalJSTranslator.enterDeleteIndex(GraalJSTranslator.java:2154) > at > com.oracle.truffle.js.parser.GraalJSTranslator.enterDelete(GraalJSTranslator.java:2134) > at > com.oracle.truffle.js.parser.GraalJSTranslator.enterUnaryNode(GraalJSTranslator.java:1986) > at > com.oracle.truffle.js.parser.JavaScriptTranslator.enterUnaryNode(JavaScriptTranslator.java:70) > at > com.oracle.truffle.js.parser.GraalJSTranslator.enterUnaryNode(GraalJSTranslator.java:173) > at com.oracle.js.parser.ir.UnaryNode.accept(UnaryNode.java:138) > at > com.oracle.truffle.js.parser.GraalJSTranslator.transform(GraalJSTranslator.java:203) > at > com.oracle.truffle.js.parser.GraalJSTranslator.enterExpressionStatement(GraalJSTranslator.java:3091) > at > com.oracle.truffle.js.parser.JavaScriptTranslator.enterExpressionStatement(JavaScriptTranslator.java:70) > at > com.oracle.truffle.js.parser.GraalJSTranslator.enterExpressionStatement(GraalJSTranslator.java:173) > at > com.oracle.js.parser.ir.ExpressionStatement.accept(ExpressionStatement.java:87) > at > com.oracle.truffle.js.parser.GraalJSTranslator.transform(GraalJSTranslator.java:203) > at > com.oracle.truffle.js.parser.GraalJSTranslator.transformStatementInBlock(GraalJSTranslator.java:1471) > at > com.oracle.truffle.js.parser.GraalJSTranslator.transformStatements(GraalJSTranslator.java:1402) > at > com.oracle.truffle.js.parser.GraalJSTranslator.enterBlock(GraalJSTranslator.java:1319) > at > com.oracle.truffle.js.parser.JavaScriptTranslator.enterBlock(JavaScriptTranslator.java:70) > at > com.oracle.truffle.js.parser.GraalJSTranslator.enterBlock(GraalJSTranslator.java:173) > at com.oracle.js.parser.ir.Block.accept(Block.java:182) > at > com.oracle.js.parser.ir.LexicalContextNode.accept(LexicalContextNode.java:81) > at com.oracle.js.parser.ir.Block.accept(Block.java:378) > at > com.oracle.truffle.js.parser.GraalJSTranslator.transform(GraalJSTranslator.java:203) > at > com.oracle.truffle.js.parser.GraalJSTranslator.enterForNode(GraalJSTranslator.java:1804) > at > com.oracle.truffle.js.parser.JavaScriptTranslator.enterForNode(JavaScriptTranslator.java:70) > at > com.oracle.truffle.js.parser.GraalJSTranslator.enterForNode(GraalJSTranslator.java:173) > at com.oracle.js.parser.ir.ForNode.accept(ForNode.java:125) > at > com.oracle.js.parser.ir.LexicalContextNode.accept(LexicalContextNode.java:81) > at > com.oracle.js.parser.ir.LexicalContextStatement.accept(LexicalContextStatement.java:68) > at > com.oracle.truffle.js.parser.GraalJSTranslator.transform(GraalJSTranslator.java:203) > at > com.oracle.truffle.js.parser.GraalJSTranslator.transformStatementInBlock(GraalJSTranslator.java:1471) > at > com.oracle.truffle.js.parser.GraalJSTranslator.transformStatements(GraalJSTranslator.java:1402) > at > com.oracle.truffle.js.parser.GraalJSTranslator.enterBlock(GraalJSTranslator.java:1319) > at > com.oracle.truffle.js.parser.JavaScriptTranslator.enterBlock(JavaScriptTranslator.java:70) > at > com.oracle.truffle.js.parser.GraalJSTranslator.enterBlock(GraalJSTranslator.java:173) > at com.oracle.js.parser.ir.Block.accept(Block.java:182) > at > com.oracle.js.parser.ir.LexicalContextNode.accept(LexicalContextNode.java:81) > a
[jira] [Updated] (NETBEANS-5188) Cannot use Jackpot30 on HTML/Java API
[
https://issues.apache.org/jira/browse/NETBEANS-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-5188:
--
Description:
I am trying to eliminate use of lamdas in HTML/Java Generics processor. One
option is to switch to target level 1.7, but then I'd have to avoid using text
blocks. The other option is to keep target level 1.8, but use a [Jackpot hint
to avoid
lambdas|https://github.com/oracle/graal/blob/master/truffle/src/com.oracle.truffle.api/src/META-INF/upgrade/nolambdas.hint].
However last version of Jackpot cannot handle Java 15 features anyway. Apply
following patch to [https://github.com/apache/netbeans-html4j/]
{code:java}
netbeans-html4j/generic$ git diff
diff --git a/generic/pom.xml b/generic/pom.xml
index 6500712e..0b29e2f2 100644
--- a/generic/pom.xml
+++ b/generic/pom.xml
@@ -84,10 +84,13 @@
${project.version}
- 15
- 1.8
+
+ org.apache.netbeans.modules.jackpot30
+ jackpot30-maven-plugin
+ 11.1
+
org.apache.maven.plugins
maven-deploy-plugin
{code}
and then try to run Jackpot:
{code:java}
netbeans-html4j/generic$ JAVA_HOME=~/bin/jdk-15 mvn jackpot30:analyze
[INFO] Scanning for projects...
[INFO]
[INFO] -< org.netbeans.html:generic >--
[INFO] Building DukeScript Generic Presenter 2.0-SNAPSHOT
[INFO] ---[ bundle ]---
[INFO]
[INFO] --- jackpot30-maven-plugin:11.1:analyze (default-cli) @ generic ---
java.lang.NoSuchMethodError: 'void
com.sun.tools.javac.tree.JCTree$JCClassDecl.(com.sun.tools.javac.tree.JCTree$JCModifiers,
com.sun.tools.javac.util.Name, com.sun.tools.javac.util.List,
com.sun.tools.javac.tree.JCTree$JCExpression, com.sun.tools.javac.util.List,
com.sun.tools.javac.util.List, com.sun.tools.javac.code.Symbol$ClassSymbol)'
at
org.netbeans.lib.nbjavac.services.NBTreeMaker$IndexedClassDecl.(NBTreeMaker.java:91)
at
org.netbeans.lib.nbjavac.services.NBTreeMaker.ClassDef(NBTreeMaker.java:75)
at
org.netbeans.lib.nbjavac.services.NBTreeMaker.ClassDef(NBTreeMaker.java:40)
at jdk.compiler/com.sun.tools.javac.comp.Enter.(Enter.java:132)
at org.netbeans.lib.nbjavac.services.NBEnter.(NBEnter.java:47)
at org.netbeans.lib.nbjavac.services.NBEnter$1.make(NBEnter.java:38)
at org.netbeans.lib.nbjavac.services.NBEnter$1.make(NBEnter.java:36)
at jdk.compiler/com.sun.tools.javac.util.Context.get(Context.java:150)
at jdk.compiler/com.sun.tools.javac.comp.Enter.instance(Enter.java:111)
at
jdk.compiler/com.sun.tools.javac.comp.DeferredAttr.(DeferredAttr.java:118)
at
jdk.compiler/com.sun.tools.javac.comp.DeferredAttr.instance(DeferredAttr.java:107)
at
jdk.compiler/com.sun.tools.javac.comp.Resolve.(Resolve.java:128)
at org.netbeans.lib.nbjavac.services.NBResolve.(NBResolve.java:50)
at org.netbeans.lib.nbjavac.services.NBResolve$1.make(NBResolve.java:44)
at org.netbeans.lib.nbjavac.services.NBResolve$1.make(NBResolve.java:42)
at jdk.compiler/com.sun.tools.javac.util.Context.get(Context.java:150)
at
jdk.compiler/com.sun.tools.javac.comp.Resolve.instance(Resolve.java:162)
at jdk.compiler/com.sun.tools.javac.comp.Check.(Check.java:123)
at jdk.compiler/com.sun.tools.javac.comp.Check.instance(Check.java:111)
at
jdk.compiler/com.sun.tools.javac.comp.Modules.(Modules.java:189)
at
jdk.compiler/com.sun.tools.javac.comp.Modules.instance(Modules.java:179)
at jdk.compiler/com.sun.tools.javac.code.Symtab.(Symtab.java:516)
at jdk.compiler/com.sun.tools.javac.code.Symtab.instance(Symtab.java:92)
at jdk.compiler/com.sun.tools.javac.comp.Attr.(Attr.java:136)
at org.netbeans.lib.nbjavac.services.NBAttr.(NBAttr.java:58)
at org.netbeans.lib.nbjavac.services.NBAttr$1.make(NBAttr.java:49)
at org.netbeans.lib.nbjavac.services.NBAttr$1.make(NBAttr.java:47)
at jdk.compiler/com.sun.tools.javac.util.Context.get(Context.java:150)
at jdk.compiler/com.sun.tools.javac.comp.Attr.instance(Attr.java:125)
at
jdk.compiler/com.sun.tools.javac.comp.Annotate.(Annotate.java:109)
at
jdk.compiler/com.sun.tools.javac.comp.Annotate.instance(Annotate.java:84)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassReader.(ClassReader.java:257)
at
org.netbeans.lib.nbjavac.services.NBClassReader.(NBClassReader.java:50)
at
org.netbeans.lib.nbjavac.services.NBClassReader$1.make(NBClassReader.java:41)
at
org.netbeans.lib.nbjavac.services.NBClassReader$1.make(NBClassReader.java:39)
at jdk.compiler/com.sun.tools.j
[jira] [Created] (NETBEANS-5188) Cannot use Jackpot30 on HTML/Java API
Jaroslav Tulach created NETBEANS-5188:
-
Summary: Cannot use Jackpot30 on HTML/Java API
Key: NETBEANS-5188
URL: https://issues.apache.org/jira/browse/NETBEANS-5188
Project: NetBeans
Issue Type: Bug
Components: java - Refactoring
Affects Versions: 11.1
Reporter: Jaroslav Tulach
Assignee: Jan Lahoda
I am trying to eliminate use of lamdas in HTML/Java Generics processor. One
option is to switch to target level 1.7, but then I'd have to avoid using text
blocks. The other option is to keep target level 1.8, but use a Jackpot hint to
avoid lambdas.
However last version of Jackpot cannot handle Java 15 features anyway. Apply
following patch to https://github.com/apache/netbeans-html4j/
{code:java}
netbeans-html4j/generic$ git diff
diff --git a/generic/pom.xml b/generic/pom.xml
index 6500712e..0b29e2f2 100644
--- a/generic/pom.xml
+++ b/generic/pom.xml
@@ -84,10 +84,13 @@
${project.version}
- 15
- 1.8
+
+ org.apache.netbeans.modules.jackpot30
+ jackpot30-maven-plugin
+ 11.1
+
org.apache.maven.plugins
maven-deploy-plugin
{code}
and then try to run Jackpot:
{code:java}
netbeans-html4j/generic$ JAVA_HOME=~/bin/jdk-15 mvn jackpot30:analyze
[INFO] Scanning for projects...
[INFO]
[INFO] -< org.netbeans.html:generic >--
[INFO] Building DukeScript Generic Presenter 2.0-SNAPSHOT
[INFO] ---[ bundle ]---
[INFO]
[INFO] --- jackpot30-maven-plugin:11.1:analyze (default-cli) @ generic ---
java.lang.NoSuchMethodError: 'void
com.sun.tools.javac.tree.JCTree$JCClassDecl.(com.sun.tools.javac.tree.JCTree$JCModifiers,
com.sun.tools.javac.util.Name, com.sun.tools.javac.util.List,
com.sun.tools.javac.tree.JCTree$JCExpression, com.sun.tools.javac.util.List,
com.sun.tools.javac.util.List, com.sun.tools.javac.code.Symbol$ClassSymbol)'
at
org.netbeans.lib.nbjavac.services.NBTreeMaker$IndexedClassDecl.(NBTreeMaker.java:91)
at
org.netbeans.lib.nbjavac.services.NBTreeMaker.ClassDef(NBTreeMaker.java:75)
at
org.netbeans.lib.nbjavac.services.NBTreeMaker.ClassDef(NBTreeMaker.java:40)
at jdk.compiler/com.sun.tools.javac.comp.Enter.(Enter.java:132)
at org.netbeans.lib.nbjavac.services.NBEnter.(NBEnter.java:47)
at org.netbeans.lib.nbjavac.services.NBEnter$1.make(NBEnter.java:38)
at org.netbeans.lib.nbjavac.services.NBEnter$1.make(NBEnter.java:36)
at jdk.compiler/com.sun.tools.javac.util.Context.get(Context.java:150)
at jdk.compiler/com.sun.tools.javac.comp.Enter.instance(Enter.java:111)
at
jdk.compiler/com.sun.tools.javac.comp.DeferredAttr.(DeferredAttr.java:118)
at
jdk.compiler/com.sun.tools.javac.comp.DeferredAttr.instance(DeferredAttr.java:107)
at
jdk.compiler/com.sun.tools.javac.comp.Resolve.(Resolve.java:128)
at org.netbeans.lib.nbjavac.services.NBResolve.(NBResolve.java:50)
at org.netbeans.lib.nbjavac.services.NBResolve$1.make(NBResolve.java:44)
at org.netbeans.lib.nbjavac.services.NBResolve$1.make(NBResolve.java:42)
at jdk.compiler/com.sun.tools.javac.util.Context.get(Context.java:150)
at
jdk.compiler/com.sun.tools.javac.comp.Resolve.instance(Resolve.java:162)
at jdk.compiler/com.sun.tools.javac.comp.Check.(Check.java:123)
at jdk.compiler/com.sun.tools.javac.comp.Check.instance(Check.java:111)
at
jdk.compiler/com.sun.tools.javac.comp.Modules.(Modules.java:189)
at
jdk.compiler/com.sun.tools.javac.comp.Modules.instance(Modules.java:179)
at jdk.compiler/com.sun.tools.javac.code.Symtab.(Symtab.java:516)
at jdk.compiler/com.sun.tools.javac.code.Symtab.instance(Symtab.java:92)
at jdk.compiler/com.sun.tools.javac.comp.Attr.(Attr.java:136)
at org.netbeans.lib.nbjavac.services.NBAttr.(NBAttr.java:58)
at org.netbeans.lib.nbjavac.services.NBAttr$1.make(NBAttr.java:49)
at org.netbeans.lib.nbjavac.services.NBAttr$1.make(NBAttr.java:47)
at jdk.compiler/com.sun.tools.javac.util.Context.get(Context.java:150)
at jdk.compiler/com.sun.tools.javac.comp.Attr.instance(Attr.java:125)
at
jdk.compiler/com.sun.tools.javac.comp.Annotate.(Annotate.java:109)
at
jdk.compiler/com.sun.tools.javac.comp.Annotate.instance(Annotate.java:84)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassReader.(ClassReader.java:257)
at
org.netbeans.lib.nbjavac.services.NBClassReader.(NBClassReader.java:50)
at
org.netbeans.lib.nbjavac.services.NBClassReader$1.make(NBClassReader.java:41)
at
org.netbeans.li
[jira] [Assigned] (NETBEANS-5155) NPE in PHP Smarty tpl files
[ https://issues.apache.org/jira/browse/NETBEANS-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach reassigned NETBEANS-5155: - Assignee: Svatopluk Dedic > NPE in PHP Smarty tpl files > --- > > Key: NETBEANS-5155 > URL: https://issues.apache.org/jira/browse/NETBEANS-5155 > Project: NetBeans > Issue Type: Bug > Components: javascript - Editor, php - Smarty >Affects Versions: 12.2 > Environment: Windows 10 64-bit 20H2 >Reporter: Michal Koscielny >Assignee: Svatopluk Dedic >Priority: Major > > Netbeans 12.2 reports NullPointerException when editing many of tpl files > (Smarty templates). It looks like the NPE is shown if the file contains an > html
[jira] [Created] (NETBEANS-5159) Select proper JDK for mx project
Jaroslav Tulach created NETBEANS-5159:
-
Summary: Select proper JDK for mx project
Key: NETBEANS-5159
URL: https://issues.apache.org/jira/browse/NETBEANS-5159
Project: NetBeans
Issue Type: New Feature
Components: java - Project
Affects Versions: 12.3
Reporter: Jaroslav Tulach
"mx project support" as developed in
[PR-2575|https://github.com/apache/netbeans/pull/2575] should be able to
properly select the right JDK for each "javaCompliance" level. Various
{{EXTRA_JAVA_HOMES}} can be specified in {{mx}}'s {{env}} files and the right
JDK should be used for each source root.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5158) More user friendly configuration for mx projects
Jaroslav Tulach created NETBEANS-5158:
-
Summary: More user friendly configuration for mx projects
Key: NETBEANS-5158
URL: https://issues.apache.org/jira/browse/NETBEANS-5158
Project: NetBeans
Issue Type: New Feature
Components: java - Project
Affects Versions: 12.3
Reporter: Jaroslav Tulach
Assignee: Jaroslav Tulach
"mx project support" as provided by
[PR-2575|https://github.com/apache/netbeans/pull/2575] is assuming that {{mx}}
is on execution path, that {{$HOME/.mx/env}} is set properly and doesn't
provide any UI to configure that. Should be improved, if the support is
supposed to be used by non-educated users.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5134) Error nodes in Gradle subprojects
[
https://issues.apache.org/jira/browse/NETBEANS-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248299#comment-17248299
]
Jaroslav Tulach commented on NETBEANS-5134:
---
I am not sure if misplaced directories is problem of
[https://github.com/daemontus/heap-language/] - there is {{heap/src/main/java}}
and still the _Error Node_ appears.
> Error nodes in Gradle subprojects
> -
>
> Key: NETBEANS-5134
> URL: https://issues.apache.org/jira/browse/NETBEANS-5134
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: image-2020-12-10-04-55-17-574.png
>
>
> I am trying to open
> [https://github.com/daemontus/heap-language/]
> project in NetBeans 12.2 and this is the result:
> !image-2020-12-10-04-55-17-574.png!
> There is a lot of Error Node. This is caused by {{SourcesNodeFactory}}:
> {code:java}
> @Override
> public Node node(SourceGroup group) {
> Project owner = FileOwnerQuery.getOwner(group.getRootFolder());
> if (owner != project) {
> if (owner == null) {
> //#152418 if project for folder is not found, just look
> the other way..
>
> Logger.getLogger(SourcesNodeFactory.class.getName()).log(Level.INFO, "Cannot
> find a project owner for folder {0}", group.getRootFolder()); //NOI18N
> return null;
> }
> AbstractNode erroNode = new AbstractNode(Children.LEAF);
> String prjText =
> ProjectUtils.getInformation(owner).getDisplayName();
> //TODO: Could this happen? Use Bundle.
> erroNode.setDisplayName("Error Node: " +
> group.getDisplayName() + " " + prjText);
> return erroNode;
> } {code}
> the {{group.getRootFolder()}} belongs to sub project, but the {{owner}} is
> identified as the parent project.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-1765) Cannot install JavaScript Kit
[
https://issues.apache.org/jira/browse/NETBEANS-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach resolved NETBEANS-1765.
---
Fix Version/s: 12.0
Resolution: Fixed
Fixed at least for 12.0 by relicensing the requested version of JavaScript
parser under UPL and distributing it with NetBeans by default.
> Cannot install JavaScript Kit
> -
>
> Key: NETBEANS-1765
> URL: https://issues.apache.org/jira/browse/NETBEANS-1765
> Project: NetBeans
> Issue Type: Bug
> Components: javascript - Model, platform - Autoupdate
>Affects Versions: 10.0
>Reporter: Jaroslav Tulach
>Assignee: Svatopluk Dedic
>Priority: Minor
> Fix For: 12.0
>
>
> Update NetBeans to version
> {code:java}
> commit ab822e2c93541f69bc5e27250f22ba84c4f581ec (HEAD ->
> feature/autoupdate_enable_download, sdedic/feature/autoupdate_enable_download)
> Author: Svata Dedic
> Date: Fri Nov 30 18:33:37 2018 +0100
> {code}
> and then {{ant build}} and start with clean userdir:
> {code:java}
> nbbuild$ rm -rf netbeans/ testuserdir/; unzip
> NetBeans-dev-*-ab822e2c9354-release.zip ; ant tryme{code}
> Go to _Tools/Plugins/Installed_, check the _Show details_ checkbox, so one
> sees not only features, but all AU visible modules and try to activate
> *JavaScript2 Kit*:
> {code:java}
> Activation failed: Not all requested modules can be enabled:
> [StandardModule:org.netbeans.modules.javascript2.kit jarFile:
> nbbuild/netbeans/webcommon/modules/org-netbeans-modules-javascript2-kit.jar]{code}
>
> There is a workaround. One can go into the _Available Plugins_ tab and
> install *Oracle Javascript Parser implementation* first. Then activation of
> *JavaScript2 Kit* (btw. why "2", that is an implementation detail the version
> "1" is buried in history for many years) succeeds.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4699) Make it easy to create dynamically updated ProxyLookup
[ https://issues.apache.org/jira/browse/NETBEANS-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach resolved NETBEANS-4699. --- Fix Version/s: 12.2 Resolution: Fixed Integrated, as far as I know. > Make it easy to create dynamically updated ProxyLookup > -- > > Key: NETBEANS-4699 > URL: https://issues.apache.org/jira/browse/NETBEANS-4699 > Project: NetBeans > Issue Type: Improvement > Components: platform - Lookup >Affects Versions: 12.0 >Reporter: Jaroslav Tulach >Assignee: Tim Boudreau >Priority: Major > Fix For: 12.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > One of the most common uses of ProxyLookup is to dynamically change the set > of lookups being delegated to. The objection to exposing the > setLookups() method is straightforward it would be inviting > clients of such a Lookup to call it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5134) Error nodes in Gradle subprojects
Jaroslav Tulach created NETBEANS-5134:
-
Summary: Error nodes in Gradle subprojects
Key: NETBEANS-5134
URL: https://issues.apache.org/jira/browse/NETBEANS-5134
Project: NetBeans
Issue Type: Bug
Components: projects - Gradle
Affects Versions: 12.2
Reporter: Jaroslav Tulach
Assignee: Laszlo Kishalmi
Attachments: image-2020-12-10-04-55-17-574.png
I am trying to open
[https://github.com/daemontus/heap-language/]
project in NetBeans 12.2 and this is the result:
!image-2020-12-10-04-55-17-574.png!
There is a lot of Error Node. This is caused by
{code:java}
@Override
public Node node(SourceGroup group) {
Project owner = FileOwnerQuery.getOwner(group.getRootFolder());
if (owner != project) {
if (owner == null) {
//#152418 if project for folder is not found, just look the
other way..
Logger.getLogger(SourcesNodeFactory.class.getName()).log(Level.INFO, "Cannot
find a project owner for folder {0}", group.getRootFolder()); //NOI18N
return null;
}
AbstractNode erroNode = new AbstractNode(Children.LEAF);
String prjText =
ProjectUtils.getInformation(owner).getDisplayName();
//TODO: Could this happen? Use Bundle.
erroNode.setDisplayName("Error Node: " + group.getDisplayName()
+ " " + prjText);
return erroNode;
} {code}
the {{group.getRootFolder()}} belongs to sub project, but the {{owner}} is
identified as the parent project.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5134) Error nodes in Gradle subprojects
[
https://issues.apache.org/jira/browse/NETBEANS-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-5134:
--
Description:
I am trying to open
[https://github.com/daemontus/heap-language/]
project in NetBeans 12.2 and this is the result:
!image-2020-12-10-04-55-17-574.png!
There is a lot of Error Node. This is caused by {{SourcesNodeFactory}}:
{code:java}
@Override
public Node node(SourceGroup group) {
Project owner = FileOwnerQuery.getOwner(group.getRootFolder());
if (owner != project) {
if (owner == null) {
//#152418 if project for folder is not found, just look the
other way..
Logger.getLogger(SourcesNodeFactory.class.getName()).log(Level.INFO, "Cannot
find a project owner for folder {0}", group.getRootFolder()); //NOI18N
return null;
}
AbstractNode erroNode = new AbstractNode(Children.LEAF);
String prjText =
ProjectUtils.getInformation(owner).getDisplayName();
//TODO: Could this happen? Use Bundle.
erroNode.setDisplayName("Error Node: " + group.getDisplayName()
+ " " + prjText);
return erroNode;
} {code}
the {{group.getRootFolder()}} belongs to sub project, but the {{owner}} is
identified as the parent project.
was:
I am trying to open
[https://github.com/daemontus/heap-language/]
project in NetBeans 12.2 and this is the result:
!image-2020-12-10-04-55-17-574.png!
There is a lot of Error Node. This is caused by
{code:java}
@Override
public Node node(SourceGroup group) {
Project owner = FileOwnerQuery.getOwner(group.getRootFolder());
if (owner != project) {
if (owner == null) {
//#152418 if project for folder is not found, just look the
other way..
Logger.getLogger(SourcesNodeFactory.class.getName()).log(Level.INFO, "Cannot
find a project owner for folder {0}", group.getRootFolder()); //NOI18N
return null;
}
AbstractNode erroNode = new AbstractNode(Children.LEAF);
String prjText =
ProjectUtils.getInformation(owner).getDisplayName();
//TODO: Could this happen? Use Bundle.
erroNode.setDisplayName("Error Node: " + group.getDisplayName()
+ " " + prjText);
return erroNode;
} {code}
the {{group.getRootFolder()}} belongs to sub project, but the {{owner}} is
identified as the parent project.
> Error nodes in Gradle subprojects
> -
>
> Key: NETBEANS-5134
> URL: https://issues.apache.org/jira/browse/NETBEANS-5134
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: image-2020-12-10-04-55-17-574.png
>
>
> I am trying to open
> [https://github.com/daemontus/heap-language/]
> project in NetBeans 12.2 and this is the result:
> !image-2020-12-10-04-55-17-574.png!
> There is a lot of Error Node. This is caused by {{SourcesNodeFactory}}:
> {code:java}
> @Override
> public Node node(SourceGroup group) {
> Project owner = FileOwnerQuery.getOwner(group.getRootFolder());
> if (owner != project) {
> if (owner == null) {
> //#152418 if project for folder is not found, just look
> the other way..
>
> Logger.getLogger(SourcesNodeFactory.class.getName()).log(Level.INFO, "Cannot
> find a project owner for folder {0}", group.getRootFolder()); //NOI18N
> return null;
> }
> AbstractNode erroNode = new AbstractNode(Children.LEAF);
> String prjText =
> ProjectUtils.getInformation(owner).getDisplayName();
> //TODO: Could this happen? Use Bundle.
> erroNode.setDisplayName("Error Node: " +
> group.getDisplayName() + " " + prjText);
> return erroNode;
> } {code}
> the {{group.getRootFolder()}} belongs to sub project, but the {{owner}} is
> identified as the parent project.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5017) Broken to text block with concatentation refactoring
[
https://issues.apache.org/jira/browse/NETBEANS-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-5017:
--
Description:
I tried to apply Convert to Text block refactoring to code in [netbeans-html4j
repository|https://github.com/apache/netbeans-html4j/blob/006488782a6d1567eacb080443bcd9329988f323/json/src/test/java/net/java/html/json/ModelProcessorTest.java#L507]
that looks like this:
{code:java}
private void needsAnArg(String method) throws Exception {
String html = ""
+ "";
String code = "package x.y.z;\n"
+ "import net.java.html.json.Model;\n"
+ "import net.java.html.json.Property;\n"
+ "import net.java.html.json.OnReceive;\n"
+ "@Model(className=\"XModel\", properties={\n"
+ " @Property(name=\"prop\", type=long.class)\n"
+ "})\n"
+ "class X {\n"
+ " @Model(className=\"PQ\", properties={})\n"
+ " class PImpl {\n"
+ " }\n"
+ " @OnReceive(method=\"" + method + "\", url=\"whereever\")\n"
+ " static void obtained(XModel m, PQ p) { }\n"
+ "}\n";
{code}
The result isn't compilable. Possibly confused by terminal {{\"}}.
was:
I tried to apply Convert to Text block refactoring to code in netbeans-html4j
repository that looks like this:
{code:java}
private void needsAnArg(String method) throws Exception {
String html = ""
+ "";
String code = "package x.y.z;\n"
+ "import net.java.html.json.Model;\n"
+ "import net.java.html.json.Property;\n"
+ "import net.java.html.json.OnReceive;\n"
+ "@Model(className=\"XModel\", properties={\n"
+ " @Property(name=\"prop\", type=long.class)\n"
+ "})\n"
+ "class X {\n"
+ " @Model(className=\"PQ\", properties={})\n"
+ " class PImpl {\n"
+ " }\n"
+ " @OnReceive(method=\"" + method + "\", url=\"whereever\")\n"
+ " static void obtained(XModel m, PQ p) { }\n"
+ "}\n";
{code}
The result isn't compilable. Possibly confused by terminal {{\"}}.
> Broken to text block with concatentation refactoring
>
>
> Key: NETBEANS-5017
> URL: https://issues.apache.org/jira/browse/NETBEANS-5017
> Project: NetBeans
> Issue Type: Bug
> Components: java - Hints
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Akshay Gupta
>Priority: Major
>
> I tried to apply Convert to Text block refactoring to code in
> [netbeans-html4j
> repository|https://github.com/apache/netbeans-html4j/blob/006488782a6d1567eacb080443bcd9329988f323/json/src/test/java/net/java/html/json/ModelProcessorTest.java#L507]
> that looks like this:
> {code:java}
> private void needsAnArg(String method) throws Exception {
> String html = ""
> + "";
> String code = "package x.y.z;\n"
> + "import net.java.html.json.Model;\n"
> + "import net.java.html.json.Property;\n"
> + "import net.java.html.json.OnReceive;\n"
> + "@Model(className=\"XModel\", properties={\n"
> + " @Property(name=\"prop\", type=long.class)\n"
> + "})\n"
> + "class X {\n"
> + " @Model(className=\"PQ\", properties={})\n"
> + " class PImpl {\n"
> + " }\n"
> + " @OnReceive(method=\"" + method + "\", url=\"whereever\")\n"
> + " static void obtained(XModel m, PQ p) { }\n"
> + "}\n";
> {code}
> The result isn't compilable. Possibly confused by terminal {{\"}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5017) Broken to text block with concatentation refactoring
Jaroslav Tulach created NETBEANS-5017:
-
Summary: Broken to text block with concatentation refactoring
Key: NETBEANS-5017
URL: https://issues.apache.org/jira/browse/NETBEANS-5017
Project: NetBeans
Issue Type: Bug
Components: java - Hints
Affects Versions: 12.2
Reporter: Jaroslav Tulach
Assignee: Akshay Gupta
I tried to apply Convert to Text block refactoring to code in netbeans-html4j
repository that looks like this:
{code:java}
private void needsAnArg(String method) throws Exception {
String html = ""
+ "";
String code = "package x.y.z;\n"
+ "import net.java.html.json.Model;\n"
+ "import net.java.html.json.Property;\n"
+ "import net.java.html.json.OnReceive;\n"
+ "@Model(className=\"XModel\", properties={\n"
+ " @Property(name=\"prop\", type=long.class)\n"
+ "})\n"
+ "class X {\n"
+ " @Model(className=\"PQ\", properties={})\n"
+ " class PImpl {\n"
+ " }\n"
+ " @OnReceive(method=\"" + method + "\", url=\"whereever\")\n"
+ " static void obtained(XModel m, PQ p) { }\n"
+ "}\n";
{code}
The result isn't compilable. Possibly confused by terminal {{\"}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4931) nb-javac breaks project test classes
[ https://issues.apache.org/jira/browse/NETBEANS-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach reassigned NETBEANS-4931: - Assignee: (was: Akshay K. Ukey) > nb-javac breaks project test classes > > > Key: NETBEANS-4931 > URL: https://issues.apache.org/jira/browse/NETBEANS-4931 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.0, 12.1, 12.2 >Reporter: Javier A. Ortiz >Priority: Major > Attachments: before.log, netbeans.log > > > Something changed with nb-javac (upgrade?) that affects both 12.0 and 12.1. > All of sudden the red icons started showing up in the test classes > complaining about missing definitions (classes, methods, etc.) from stuff > within the same project. > Tried reinstalling and nothing. The project compiles and runs but some > functionality is just not there due to this. Was able to fix it by > uninstalling nb-javac plugin. > See the log before enabling the nb-javac plugin with opened projects and > compare it to the other one just after restarting as part of installing the > plugin. > I've tried this in the following JDK versions: > * JDK 8 > * JDK 9 > * JDK 12 > * JDK 14 > And in various versions with the same behavior: > * 12.0 > * 12.1 > * 12.2 beta 3 > -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-4931) nb-javac breaks project test classes
[ https://issues.apache.org/jira/browse/NETBEANS-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach reassigned NETBEANS-4931: - Assignee: Akshay K. Ukey > nb-javac breaks project test classes > > > Key: NETBEANS-4931 > URL: https://issues.apache.org/jira/browse/NETBEANS-4931 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.0, 12.1, 12.2 >Reporter: Javier A. Ortiz >Assignee: Akshay K. Ukey >Priority: Major > Attachments: before.log, netbeans.log > > > Something changed with nb-javac (upgrade?) that affects both 12.0 and 12.1. > All of sudden the red icons started showing up in the test classes > complaining about missing definitions (classes, methods, etc.) from stuff > within the same project. > Tried reinstalling and nothing. The project compiles and runs but some > functionality is just not there due to this. Was able to fix it by > uninstalling nb-javac plugin. > See the log before enabling the nb-javac plugin with opened projects and > compare it to the other one just after restarting as part of installing the > plugin. > I've tried this in the following JDK versions: > * JDK 8 > * JDK 9 > * JDK 12 > * JDK 14 > And in various versions with the same behavior: > * 12.0 > * 12.1 > * 12.2 beta 3 > -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5007) No restart of language server after change of JDK home
Jaroslav Tulach created NETBEANS-5007:
-
Summary: No restart of language server after change of JDK home
Key: NETBEANS-5007
URL: https://issues.apache.org/jira/browse/NETBEANS-5007
Project: NetBeans
Issue Type: Bug
Components: vscode
Affects Versions: 12.2
Reporter: Jaroslav Tulach
Assignee: Svatopluk Dedic
Fix For: 12.2
Choose File/Preferences/Settings and change the value of
{color:#9cdcfe}"netbeans.jdkhome"{color}{color:#d4d4d4}:
{color}{color:#ce9178}""{color}{color:#d4d4d4},{color}
while the Apache NetBeans Language Server VSCode extension is running. The
{{nbcode}} backend shall be killed and restarted on the new JDK. However it
goes into strange loop and then stops listening for changes in the property
completely. Example of output:
{code:java}
Initiating server activation
extension.js:184
Request to kill LSP server.
extension.js:190
Cannot kill: current process is None
extension.js:212
LSP server launching: 27193
extension.js:252
LSP server 27193 terminated with 0
extension.js:277
Initiating server activation
extension.js:184
Request to kill LSP server.
extension.js:190
Killing LSP server 27193
extension.js:201
rejected promise not handled within 1 second: Cannot kill
extensionHostProcess.js:1059
Server activation requested repeatedly, ignoring...
extension.js:173
Server activation requested repeatedly, ignoring...
extension.js:173
Server activation requested repeatedly, ignoring... {code}
[~sdedic] has already addressed this issue in
[PR-2531|https://github.com/apache/netbeans/pull/2531].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4998) Annotation processor completions not displayed in VSCode
Jaroslav Tulach created NETBEANS-4998:
-
Summary: Annotation processor completions not displayed in VSCode
Key: NETBEANS-4998
URL: https://issues.apache.org/jira/browse/NETBEANS-4998
Project: NetBeans
Issue Type: Bug
Components: vscode
Affects Versions: 12.2
Reporter: Jaroslav Tulach
Assignee: Jan Lahoda
The VSCode doesn't display hints from annotation processors. To reproduce clone:
{code:java}
https://github.com/jtulach/netbeans-html4j {code}
and checkout revision
{code:java}
eb1841800ae16782b781a60bda4a23593502ae60 {code}
after building the gradle (please use JDK11) -
{code:java}
$ JAVA_HOME=/jdk-11 ./gradlew assemble
{code}
you can open {{TicTacToe1.java}} and go to line 37, after second {{{}} there
should be a CC:
{code:java}
{|shows list of parameters}{code}
This seems to work in NetBeans 12.2, but not in VSCode.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4996) Hints in VSCode editor aren't refreshed after successful build
Jaroslav Tulach created NETBEANS-4996:
-
Summary: Hints in VSCode editor aren't refreshed after successful
build
Key: NETBEANS-4996
URL: https://issues.apache.org/jira/browse/NETBEANS-4996
Project: NetBeans
Issue Type: Bug
Components: vscode
Affects Versions: 12.2
Reporter: Jaroslav Tulach
Assignee: Jan Lahoda
After successful Gradle build the hint on {{package}} statement should
disappear. It doesn't right now. One needs to perform edit (press Enter?) in
the editor to refresh the hints. To reproduce:
Create new Gradle project with some (not downloaded) dependencies. Open it in
VSCode Apache NetBeans Language Server 12.2. There should be hint "Missing
mandatory classpath entries" on {{package}} statement. Select fix, the build is
started and finishes successfully. However the hint still remains.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4981) NPE when launching VSCode extension on JDK8
[
https://issues.apache.org/jira/browse/NETBEANS-4981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225198#comment-17225198
]
Jaroslav Tulach commented on NETBEANS-4981:
---
I've just initiated [PR-2517|https://github.com/apache/netbeans/pull/2517] to
address the problem.
> NPE when launching VSCode extension on JDK8
> ---
>
> Key: NETBEANS-4981
> URL: https://issues.apache.org/jira/browse/NETBEANS-4981
> Project: NetBeans
> Issue Type: Bug
> Components: vscode
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Jan Lahoda
>Priority: Major
> Fix For: 12.2
>
>
> When launching 12.2beta3 [VSCode
> extension|https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/164/]
> with JDK8 following error is raised:
> {code:java}
> Exit code 0[Error - 8:23:34] Server initialization failed. Message: Internal
> error. Code: -32603 java.util.concurrent.CompletionException:
> java.lang.NullPointerExceptionat
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
> at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
> at
> java.util.concurrent.CompletableFuture.uniRun(CompletableFuture.java:708)
> at
> java.util.concurrent.CompletableFuture$UniRun.tryFire(CompletableFuture.java:687)
> at
> java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
> at
> java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)
> at
> org.netbeans.modules.java.lsp.server.protocol.Server$LanguageServerImpl.asyncOpenSelectedProjects(Server.java:210)
> at
> org.netbeans.modules.java.lsp.server.protocol.Server$LanguageServerImpl.lambda$initialize$1(Server.java:276)
> 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)Caused
> by: java.lang.NullPointerExceptionat
> org.netbeans.modules.java.lsp.server.protocol.Server$LanguageServerImpl.showIndexingCompleted(Server.java:219)
> at
> java.util.concurrent.CompletableFuture.uniRun(CompletableFuture.java:705)
> {code}
> This is very likely due to missing {{nbjavac}}. Try:
> {code:java}
> netbeans/java/java.lsp.server/vscode$ npm run nbcode -- --jdkhome /jdk1.8.0/
> -J-Dnetbeans.logger.console=true
> {code}
> followed by
> {code:java}
> netbeans/java/java.lsp.server/vscode$ code --extensionDevelopmentPath=`pwd`
> ~/tmp/withcontrol/
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4981) NPE when launching VSCode extension on JDK8
[
https://issues.apache.org/jira/browse/NETBEANS-4981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-4981:
--
Description:
When launching 12.2beta3 [VSCode
extension|https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/164/]
with JDK8 following error is raised:
{code:java}
Exit code 0[Error - 8:23:34] Server initialization failed. Message: Internal
error. Code: -32603 java.util.concurrent.CompletionException:
java.lang.NullPointerExceptionat
java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
at
java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
at
java.util.concurrent.CompletableFuture.uniRun(CompletableFuture.java:708)at
java.util.concurrent.CompletableFuture$UniRun.tryFire(CompletableFuture.java:687)
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
at
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)
at
org.netbeans.modules.java.lsp.server.protocol.Server$LanguageServerImpl.asyncOpenSelectedProjects(Server.java:210)
at
org.netbeans.modules.java.lsp.server.protocol.Server$LanguageServerImpl.lambda$initialize$1(Server.java:276)
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)Caused
by: java.lang.NullPointerExceptionat
org.netbeans.modules.java.lsp.server.protocol.Server$LanguageServerImpl.showIndexingCompleted(Server.java:219)
at
java.util.concurrent.CompletableFuture.uniRun(CompletableFuture.java:705) {code}
This is very likely due to missing {{nbjavac}}. Try:
{code:java}
netbeans/java/java.lsp.server/vscode$ npm run nbcode -- --jdkhome /jdk1.8.0/
-J-Dnetbeans.logger.console=true
{code}
followed by
{code:java}
netbeans/java/java.lsp.server/vscode$ code --extensionDevelopmentPath=`pwd`
~/tmp/withcontrol/
{code}
was:
When launching 12.2beta3 [VSCode
extension|https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/164/]
with JDK8 following error is raised:
{code:java}
Exit code 0[Error - 8:23:34] Server initialization failed. Message: Internal
error. Code: -32603 java.util.concurrent.CompletionException:
java.lang.NullPointerExceptionat
java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
at
java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
at
java.util.concurrent.CompletableFuture.uniRun(CompletableFuture.java:708)at
java.util.concurrent.CompletableFuture$UniRun.tryFire(CompletableFuture.java:687)
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
at
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)
at
org.netbeans.modules.java.lsp.server.protocol.Server$LanguageServerImpl.asyncOpenSelectedProjects(Server.java:210)
at
org.netbeans.modules.java.lsp.server.protocol.Server$LanguageServerImpl.lambda$initialize$1(Server.java:276)
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)Caused
by: java.lang.NullPointerExceptionat
org.netbeans.modules.java.lsp.server.protocol.Server$LanguageServerImpl.showIndexingCompleted(Server.java:219)
at
java.util.concurrent.CompletableFuture.uniRun(CompletableFuture.java:705) {code}
This is very likely due to missing {{nbjavac}}.
> NPE when launching VSCode extension on JDK8
> ---
>
> Key: NETBEANS-4981
> URL: https://issues.apache.org/jira/browse/NETBEANS-4981
> Project: NetBeans
> Issue Type: Bug
> Components: vscode
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Jan Lahoda
>Priority: Major
> Fix For: 12.2
>
>
> When launching 12.2beta3 [VSCode
> extension|https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/164/]
> with JDK8 following error is raised:
> {code:java}
> Exit code 0[Error - 8:23:34] Server initialization failed. Message: Internal
> error. Code: -32603 java.util.concurrent.CompletionException:
> java.lang.NullPointerExceptionat
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
> at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
> at
> java.util.concurrent.CompletableFuture.uniRun(CompletableF
[jira] [Created] (NETBEANS-4981) NPE when launching VSCode extension on JDK8
Jaroslav Tulach created NETBEANS-4981:
-
Summary: NPE when launching VSCode extension on JDK8
Key: NETBEANS-4981
URL: https://issues.apache.org/jira/browse/NETBEANS-4981
Project: NetBeans
Issue Type: Bug
Components: vscode
Affects Versions: 12.2
Reporter: Jaroslav Tulach
Assignee: Jan Lahoda
Fix For: 12.2
When launching 12.2beta3 [VSCode
extension|https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/164/]
with JDK8 following error is raised:
{code:java}
Exit code 0[Error - 8:23:34] Server initialization failed. Message: Internal
error. Code: -32603 java.util.concurrent.CompletionException:
java.lang.NullPointerExceptionat
java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
at
java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
at
java.util.concurrent.CompletableFuture.uniRun(CompletableFuture.java:708)at
java.util.concurrent.CompletableFuture$UniRun.tryFire(CompletableFuture.java:687)
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
at
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)
at
org.netbeans.modules.java.lsp.server.protocol.Server$LanguageServerImpl.asyncOpenSelectedProjects(Server.java:210)
at
org.netbeans.modules.java.lsp.server.protocol.Server$LanguageServerImpl.lambda$initialize$1(Server.java:276)
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)Caused
by: java.lang.NullPointerExceptionat
org.netbeans.modules.java.lsp.server.protocol.Server$LanguageServerImpl.showIndexingCompleted(Server.java:219)
at
java.util.concurrent.CompletableFuture.uniRun(CompletableFuture.java:705) {code}
This is very likely due to missing {{nbjavac}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4917) Cannot convert to text
[
https://issues.apache.org/jira/browse/NETBEANS-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach resolved NETBEANS-4917.
---
Resolution: Cannot Reproduce
Thanks for trying Akshay. Yes, I can confirm that
{code:java}
netbeans$ ant tryme -Dtryme.jdkhome=$HOME/bin/jdk-15{code}
and setting the source level to 15 does work. I am not sure what kind of
mistake I did before! Sorry for bothering.
> Cannot convert to text
> --
>
> Key: NETBEANS-4917
> URL: https://issues.apache.org/jira/browse/NETBEANS-4917
> Project: NetBeans
> Issue Type: Bug
> Components: java - Hints
>Reporter: Jaroslav Tulach
>Assignee: Akshay Gupta
>Priority: Major
> Attachments: image-2020-10-17-08-54-06-928.png
>
>
> I am not able to invoke "Convert to Text Block" hint/inspect & refactor, etc.
> To reproduce my problem:
> * clone https://github.com/JaroslavTulach/heapdump/ revision
> 2c8cd7e89ee4cc613a345df023e93b0662df391b
> * open in NetBeans
> * go to Main.java line 52
> * try to convert to text block
> * it is not working for me. No hint.
> * Tried Refactor/Inspect + single inspection: Convert to Text block. Nothing.
> !image-2020-10-17-08-54-06-928.png!
> The {{pom.xml}} contains source and target set to 8. I tried everything:
> change that to 15, run the NetBeans on 15. No luck.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Closed] (NETBEANS-4938) Missing sources & co. after creating Gradle Frontend App in 12.2-beta2
[
https://issues.apache.org/jira/browse/NETBEANS-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach closed NETBEANS-4938.
-
I've just created new Java Frontend Application project with commit
{color:#00}cee80c2704dac3e35f71e5cefea67916a7ff7dc2{color}
and the result is great:
!image-2020-10-27-05-52-46-561.png!
Sources are visible, there are no errors, configurations are present. Thank you.
The only missing piece (compared to Maven) is the "Web Pages" node, but that's
not a bug report, but a feature request for some future version of NetBeans.
> Missing sources & co. after creating Gradle Frontend App in 12.2-beta2
> --
>
> Key: NETBEANS-4938
> URL: https://issues.apache.org/jira/browse/NETBEANS-4938
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Major
> Labels: pull-request-available
> Fix For: 12.2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> I am trying to test
> "New Project/Java with Gradle/Java Frontend Application"
> on 12.2-beta2 of
> {code:java}
> bin/netbeans --userdir emptyud --jdkhome /jdk-11
> {code}
> the project is generated, but it only shows a single node "Build Scripts".
> Why?
> Next step. Run "Build" from popup menu: "BUILD SUCCESSFUL". But still just a
> single node "Build Scripts".
> Invoked "Reload Project". Now there are three nodes: "Configurations" (no
> children), "Build Scripts" and "Sub Projects" (no children).
> Subsequent "Reaload Project" - shows "Sub Projects" children. Finally!
> Opening the ":desktop" and ":web" projects seems to work OK. Just
> "DesktopMain" class contains an error (cannot find "Demo" class). The same
> for "BrowserMain" class. Giving up and restarting.
> After the errors in "DesktopMain" and "BrowserMain" are gone. Moreover I can
> also see the source packages for the main project (this time, it may not be
> fully reliable).
> Creating another "New Project/Java with Gradle/Java Frontend Application"
> seems to exhibit the same behavior. E.g. only project with "Builds
> Scripts"... then two reload project actions - sub projects visible. But still
> no sources...
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4938) Missing sources & co. after creating Gradle Frontend App in 12.2-beta2
[
https://issues.apache.org/jira/browse/NETBEANS-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220309#comment-17220309
]
Jaroslav Tulach commented on NETBEANS-4938:
---
Another issue is missing "Web Pages" node. There is {{src/main/webapp}}
directory in a plain Java SE project, but it is not displayed as Java EE
feature of Gradle isn't activated. Any idea what to do about it?
> Missing sources & co. after creating Gradle Frontend App in 12.2-beta2
> --
>
> Key: NETBEANS-4938
> URL: https://issues.apache.org/jira/browse/NETBEANS-4938
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> I am trying to test
> "New Project/Java with Gradle/Java Frontend Application"
> on 12.2-beta2 of
> {code:java}
> bin/netbeans --userdir emptyud --jdkhome /jdk-11
> {code}
> the project is generated, but it only shows a single node "Build Scripts".
> Why?
> Next step. Run "Build" from popup menu: "BUILD SUCCESSFUL". But still just a
> single node "Build Scripts".
> Invoked "Reload Project". Now there are three nodes: "Configurations" (no
> children), "Build Scripts" and "Sub Projects" (no children).
> Subsequent "Reaload Project" - shows "Sub Projects" children. Finally!
> Opening the ":desktop" and ":web" projects seems to work OK. Just
> "DesktopMain" class contains an error (cannot find "Demo" class). The same
> for "BrowserMain" class. Giving up and restarting.
> After the errors in "DesktopMain" and "BrowserMain" are gone. Moreover I can
> also see the source packages for the main project (this time, it may not be
> fully reliable).
> Creating another "New Project/Java with Gradle/Java Frontend Application"
> seems to exhibit the same behavior. E.g. only project with "Builds
> Scripts"... then two reload project actions - sub projects visible. But still
> no sources...
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4938) Missing sources & co. after creating Gradle Frontend App in 12.2-beta2
[
https://issues.apache.org/jira/browse/NETBEANS-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220277#comment-17220277
]
Jaroslav Tulach commented on NETBEANS-4938:
---
Why better now. I see the source packages. However shouldn't we also see
something under Configurations node of the root project? It contains:
{code:java}
dependencies {
compile "org.netbeans.html:net.java.html.json:1.6.1"
compile "com.dukescript.api:javafx.base:8.60.11"
compile "com.dukescript.api:javafx.beaninfo:0.5"
runtime "org.netbeans.html:ko4j:1.6.1"
} {code}
but I see neither compile, neither runtime. Restarting doesn't help.
> Missing sources & co. after creating Gradle Frontend App in 12.2-beta2
> --
>
> Key: NETBEANS-4938
> URL: https://issues.apache.org/jira/browse/NETBEANS-4938
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> I am trying to test
> "New Project/Java with Gradle/Java Frontend Application"
> on 12.2-beta2 of
> {code:java}
> bin/netbeans --userdir emptyud --jdkhome /jdk-11
> {code}
> the project is generated, but it only shows a single node "Build Scripts".
> Why?
> Next step. Run "Build" from popup menu: "BUILD SUCCESSFUL". But still just a
> single node "Build Scripts".
> Invoked "Reload Project". Now there are three nodes: "Configurations" (no
> children), "Build Scripts" and "Sub Projects" (no children).
> Subsequent "Reaload Project" - shows "Sub Projects" children. Finally!
> Opening the ":desktop" and ":web" projects seems to work OK. Just
> "DesktopMain" class contains an error (cannot find "Demo" class). The same
> for "BrowserMain" class. Giving up and restarting.
> After the errors in "DesktopMain" and "BrowserMain" are gone. Moreover I can
> also see the source packages for the main project (this time, it may not be
> fully reliable).
> Creating another "New Project/Java with Gradle/Java Frontend Application"
> seems to exhibit the same behavior. E.g. only project with "Builds
> Scripts"... then two reload project actions - sub projects visible. But still
> no sources...
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4945) Newly applying java plugin on an open Gradle Project doe not propagate the Java SourceGroups
[ https://issues.apache.org/jira/browse/NETBEANS-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220276#comment-17220276 ] Jaroslav Tulach commented on NETBEANS-4945: --- Right now I don't see any problems. Projects created after NETBEANS-4938 seem to open fine including the Java source packages. > Newly applying java plugin on an open Gradle Project doe not propagate the > Java SourceGroups > - > > Key: NETBEANS-4945 > URL: https://issues.apache.org/jira/browse/NETBEANS-4945 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Reporter: Laszlo Kishalmi >Assignee: Jaroslav Tulach >Priority: Major > > Let the issue 1 identified in NETBEANS-4938 live here. > > Issue number 1 is much harder and requires a good knowledge on how the Lookup > system works. > So the Lookup of NBGradleProjectImpl consists of a basic lookup created at: > [https://github.com/apache/netbeans/blob/3a2cad159a2a60665653ce83a67547f679ec/extide/gradle/src/org/netbeans/modules/gradle/NbGradleProjectImpl.java#L161] > and a plugin dependent ProxyLookup at > [https://github.com/apache/netbeans/blob/3a2cad159a2a60665653ce83a67547f679ec/extide/gradle/src/org/netbeans/modules/gradle/NbGradleProjectImpl.java#L330] > > The issue is the following: > # Project loads with no plugins, the base set of lookups registers a > SourcesMerger > # Initially the only Sources implementation is for GENERIC_SOURCE_TYPE for > the project folder. > # On reload through the PluginDependentLookup a new Sources implementation > become available org.netbeans.modules.gradle.java.classpath.GradleSourcesImpl > from the Gradle Java project > # Unfortunately the SourceMerger is not pick up the new Sources > implementations -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-4945) Newly applying java plugin on an open Gradle Project doe not propagate the Java SourceGroups
[ https://issues.apache.org/jira/browse/NETBEANS-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-4945: -- Description: Let the issue 1 identified in NETBEANS-4938 live here. Issue number 1 is much harder and requires a good knowledge on how the Lookup system works. So the Lookup of NBGradleProjectImpl consists of a basic lookup created at: [https://github.com/apache/netbeans/blob/3a2cad159a2a60665653ce83a67547f679ec/extide/gradle/src/org/netbeans/modules/gradle/NbGradleProjectImpl.java#L161] and a plugin dependent ProxyLookup at [https://github.com/apache/netbeans/blob/3a2cad159a2a60665653ce83a67547f679ec/extide/gradle/src/org/netbeans/modules/gradle/NbGradleProjectImpl.java#L330] The issue is the following: # Project loads with no plugins, the base set of lookups registers a SourcesMerger # Initially the only Sources implementation is for GENERIC_SOURCE_TYPE for the project folder. # On reload through the PluginDependentLookup a new Sources implementation become available org.netbeans.modules.gradle.java.classpath.GradleSourcesImpl from the Gradle Java project # Unfortunately the SourceMerger is not pick up the new Sources implementations was:Let the issue 1 identified in NETBEANS-4938 live here. > Newly applying java plugin on an open Gradle Project doe not propagate the > Java SourceGroups > - > > Key: NETBEANS-4945 > URL: https://issues.apache.org/jira/browse/NETBEANS-4945 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Reporter: Laszlo Kishalmi >Assignee: Jaroslav Tulach >Priority: Major > > Let the issue 1 identified in NETBEANS-4938 live here. > > Issue number 1 is much harder and requires a good knowledge on how the Lookup > system works. > So the Lookup of NBGradleProjectImpl consists of a basic lookup created at: > [https://github.com/apache/netbeans/blob/3a2cad159a2a60665653ce83a67547f679ec/extide/gradle/src/org/netbeans/modules/gradle/NbGradleProjectImpl.java#L161] > and a plugin dependent ProxyLookup at > [https://github.com/apache/netbeans/blob/3a2cad159a2a60665653ce83a67547f679ec/extide/gradle/src/org/netbeans/modules/gradle/NbGradleProjectImpl.java#L330] > > The issue is the following: > # Project loads with no plugins, the base set of lookups registers a > SourcesMerger > # Initially the only Sources implementation is for GENERIC_SOURCE_TYPE for > the project folder. > # On reload through the PluginDependentLookup a new Sources implementation > become available org.netbeans.modules.gradle.java.classpath.GradleSourcesImpl > from the Gradle Java project > # Unfortunately the SourceMerger is not pick up the new Sources > implementations -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-4938) Missing sources & co. after creating Gradle Frontend App in 12.2-beta2
[
https://issues.apache.org/jira/browse/NETBEANS-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220140#comment-17220140
]
Jaroslav Tulach commented on NETBEANS-4938:
---
If I remember correctly the behavior was shaky in previous versions of NetBeans
, but mostly working. Now it seems consistently broken. At least it is easier
to reproduce. Thanks for looking at it.
> Missing sources & co. after creating Gradle Frontend App in 12.2-beta2
> --
>
> Key: NETBEANS-4938
> URL: https://issues.apache.org/jira/browse/NETBEANS-4938
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Major
>
> I am trying to test
> "New Project/Java with Gradle/Java Frontend Application"
> on 12.2-beta2 of
> {code:java}
> bin/netbeans --userdir emptyud --jdkhome /jdk-11
> {code}
> the project is generated, but it only shows a single node "Build Scripts".
> Why?
> Next step. Run "Build" from popup menu: "BUILD SUCCESSFUL". But still just a
> single node "Build Scripts".
> Invoked "Reload Project". Now there are three nodes: "Configurations" (no
> children), "Build Scripts" and "Sub Projects" (no children).
> Subsequent "Reaload Project" - shows "Sub Projects" children. Finally!
> Opening the ":desktop" and ":web" projects seems to work OK. Just
> "DesktopMain" class contains an error (cannot find "Demo" class). The same
> for "BrowserMain" class. Giving up and restarting.
> After the errors in "DesktopMain" and "BrowserMain" are gone. Moreover I can
> also see the source packages for the main project (this time, it may not be
> fully reliable).
> Creating another "New Project/Java with Gradle/Java Frontend Application"
> seems to exhibit the same behavior. E.g. only project with "Builds
> Scripts"... then two reload project actions - sub projects visible. But still
> no sources...
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4938) Missing sources & co. after creating Gradle Frontend App in 12.2-beta2
Jaroslav Tulach created NETBEANS-4938:
-
Summary: Missing sources & co. after creating Gradle Frontend App
in 12.2-beta2
Key: NETBEANS-4938
URL: https://issues.apache.org/jira/browse/NETBEANS-4938
Project: NetBeans
Issue Type: Bug
Components: projects - Gradle
Affects Versions: 12.2
Reporter: Jaroslav Tulach
Assignee: Laszlo Kishalmi
I am trying to test
"New Project/Java with Gradle/Java Frontend Application"
on 12.2-beta2 of
{code:java}
bin/netbeans --userdir emptyud --jdkhome /jdk-11
{code}
the project is generated, but it only shows a single node "Build Scripts". Why?
Next step. Run "Build" from popup menu: "BUILD SUCCESSFUL". But still just a
single node "Build Scripts".
Invoked "Reload Project". Now there are three nodes: "Configurations" (no
children), "Build Scripts" and "Sub Projects" (no children).
Subsequent "Reaload Project" - shows "Sub Projects" children. Finally! Opening
the ":desktop" and ":web" projects seems to work OK. Just "DesktopMain" class
contains an error (cannot find "Demo" class). The same for "BrowserMain" class.
Giving up and restarting.
After the errors in "DesktopMain" and "BrowserMain" are gone. Moreover I can
also see the source packages for the main project (this time, it may not be
fully reliable).
Creating another "New Project/Java with Gradle/Java Frontend Application" seems
to exhibit the same behavior. E.g. only project with "Builds Scripts"... then
two reload project actions - sub projects visible. But still no sources...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4746) Running test in Maven is slower than in Ant
[
https://issues.apache.org/jira/browse/NETBEANS-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17218853#comment-17218853
]
Jaroslav Tulach commented on NETBEANS-4746:
---
Looks like both problems would be solved by using
[mavendaemon|https://github.com/mvndaemon/mvnd].
> Running test in Maven is slower than in Ant
> ---
>
> Key: NETBEANS-4746
> URL: https://issues.apache.org/jira/browse/NETBEANS-4746
> Project: NetBeans
> Issue Type: Task
> Components: projects - Maven
>Affects Versions: 12.0
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Minor
> Attachments: justtest.diff, preexec-6.patch
>
>
> NetBeans users has just recently complained that Maven support is slower than
> Ant - some even claimed they [rather maintain dual Ant script
> support|http://mail-archives.apache.org/mod_mbox//netbeans-dev/202008.mbox/browser]
> than wait for Maven to launch. I've created this issue to investigate the
> problem.
> First of all we need a sample project: [^justtest.diff] - apply it {{patch
> -p1 it with Maven:
> {code:java}
> $ time JAVA_HOME=~/bin/jdk-8/ mvn -quiet
> -Dtest=com.mycompany.justtest.MainTest process-test-classes surefire:test
> ---
> T E S T S
> ---
> Running com.mycompany.justtest.MainTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.071 sec
> Results :Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> real0m2,633s
> user0m6,986s
> sys 0m0,257s
> {code}
> and you can also run it with Ant:
> {code:java}
> time JAVA_HOME=~/bin/jdk-8/ ant -q test-single
> -Djavac.includes=com/mycompany/justtest/MainTest.java
> -Dtest.includes=com/mycompany/justtest/MainTest.java
> BUILD SUCCESSFUL
> Total time: 1 second
> real0m1,899s
> user0m4,250s
> sys 0m0,244s
> {code}
> 2.6s vs. 1.9s! Really? Is that the problem? Probably not, I guess the
> difference is the integration into the IDE then.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4917) Cannot convert to text
[
https://issues.apache.org/jira/browse/NETBEANS-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215803#comment-17215803
]
Jaroslav Tulach edited comment on NETBEANS-4917 at 10/17/20, 7:02 AM:
--
Btw. why there is "Flip operands of +" on string concatenation? Of course it
changes semantics! It makes no sense to have such hint when {{+}} operates on
String.
was (Author: jtulach):
Btw. why there is "Flip operands of '+'" on string concatenation? Of course it
changes semantics! It makes no sense to have such hint when {{+}} operates on
String.
> Cannot convert to text
> --
>
> Key: NETBEANS-4917
> URL: https://issues.apache.org/jira/browse/NETBEANS-4917
> Project: NetBeans
> Issue Type: Bug
> Components: java - Hints
>Reporter: Jaroslav Tulach
>Priority: Major
> Attachments: image-2020-10-17-08-54-06-928.png
>
>
> I am not able to invoke "Convert to Text Block" hint/inspect & refactor, etc.
> To reproduce my problem:
> * clone https://github.com/JaroslavTulach/heapdump/ revision
> 2c8cd7e89ee4cc613a345df023e93b0662df391b
> * open in NetBeans
> * go to Main.java line 52
> * try to convert to text block
> * it is not working for me. No hint.
> * Tried Refactor/Inspect + single inspection: Convert to Text block. Nothing.
> !image-2020-10-17-08-54-06-928.png!
> The {{pom.xml}} contains source and target set to 8. I tried everything:
> change that to 15, run the NetBeans on 15. No luck.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4917) Cannot convert to text
[
https://issues.apache.org/jira/browse/NETBEANS-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215803#comment-17215803
]
Jaroslav Tulach edited comment on NETBEANS-4917 at 10/17/20, 7:02 AM:
--
Btw. why there is "Flip operands of plus" on string concatenation? Of course it
changes semantics! It makes no sense to have such hint when {{+}} operates on
String.
was (Author: jtulach):
Btw. why there is "Flip operands of +" on string concatenation? Of course it
changes semantics! It makes no sense to have such hint when {{+}} operates on
String.
> Cannot convert to text
> --
>
> Key: NETBEANS-4917
> URL: https://issues.apache.org/jira/browse/NETBEANS-4917
> Project: NetBeans
> Issue Type: Bug
> Components: java - Hints
>Reporter: Jaroslav Tulach
>Priority: Major
> Attachments: image-2020-10-17-08-54-06-928.png
>
>
> I am not able to invoke "Convert to Text Block" hint/inspect & refactor, etc.
> To reproduce my problem:
> * clone https://github.com/JaroslavTulach/heapdump/ revision
> 2c8cd7e89ee4cc613a345df023e93b0662df391b
> * open in NetBeans
> * go to Main.java line 52
> * try to convert to text block
> * it is not working for me. No hint.
> * Tried Refactor/Inspect + single inspection: Convert to Text block. Nothing.
> !image-2020-10-17-08-54-06-928.png!
> The {{pom.xml}} contains source and target set to 8. I tried everything:
> change that to 15, run the NetBeans on 15. No luck.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4917) Cannot convert to text
[
https://issues.apache.org/jira/browse/NETBEANS-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215803#comment-17215803
]
Jaroslav Tulach commented on NETBEANS-4917:
---
Btw. why there is "Flip operands of '+'" on string concatenation? Of course it
changes semantics! It makes no sense to have such hint when {{+}} operates on
String.
> Cannot convert to text
> --
>
> Key: NETBEANS-4917
> URL: https://issues.apache.org/jira/browse/NETBEANS-4917
> Project: NetBeans
> Issue Type: Bug
> Components: java - Hints
>Reporter: Jaroslav Tulach
>Priority: Major
> Attachments: image-2020-10-17-08-54-06-928.png
>
>
> I am not able to invoke "Convert to Text Block" hint/inspect & refactor, etc.
> To reproduce my problem:
> * clone https://github.com/JaroslavTulach/heapdump/ revision
> 2c8cd7e89ee4cc613a345df023e93b0662df391b
> * open in NetBeans
> * go to Main.java line 52
> * try to convert to text block
> * it is not working for me. No hint.
> * Tried Refactor/Inspect + single inspection: Convert to Text block. Nothing.
> !image-2020-10-17-08-54-06-928.png!
> The {{pom.xml}} contains source and target set to 8. I tried everything:
> change that to 15, run the NetBeans on 15. No luck.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4917) Cannot convert to text
Jaroslav Tulach created NETBEANS-4917:
-
Summary: Cannot convert to text
Key: NETBEANS-4917
URL: https://issues.apache.org/jira/browse/NETBEANS-4917
Project: NetBeans
Issue Type: Bug
Components: java - Hints
Reporter: Jaroslav Tulach
Attachments: image-2020-10-17-08-54-06-928.png
I am not able to invoke "Convert to Text Block" hint/inspect & refactor, etc.
To reproduce my problem:
* clone https://github.com/JaroslavTulach/heapdump/ revision
2c8cd7e89ee4cc613a345df023e93b0662df391b
* open in NetBeans
* go to Main.java line 52
* try to convert to text block
* it is not working for me. No hint.
* Tried Refactor/Inspect + single inspection: Convert to Text block. Nothing.
!image-2020-10-17-08-54-06-928.png!
The {{pom.xml}} contains source and target set to 8. I tried everything: change
that to 15, run the NetBeans on 15. No luck.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4845) javaee.wildfly cannot be built without access to network
[
https://issues.apache.org/jira/browse/NETBEANS-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach resolved NETBEANS-4845.
---
Fix Version/s: 12.2
Resolution: Fixed
Fixed by [~matthiasblaesing] in https://github.com/apache/netbeans/pull/2417
> javaee.wildfly cannot be built without access to network
>
>
> Key: NETBEANS-4845
> URL: https://issues.apache.org/jira/browse/NETBEANS-4845
> Project: NetBeans
> Issue Type: Bug
> Components: serverplugins - WildFly
>Affects Versions: 12.0, 12.1
>Reporter: Jaroslav Tulach
>Assignee: Emmanuel Hugonnet
>Priority: Blocker
> Fix For: 12.2
>
>
> Hello Emmanuel,
> as noted
> [PR-2000|https://github.com/apache/netbeans/pull/2000#issuecomment-675890873]
> I have troubles building *wildfly* support behind corporate proxy. Probably
> the goal of "Removing external downloads and updating schemas" wasn't fully
> fulfilled. My proxy says that
> [http://java.sun.com/xml/ns/javaee/javaee_6.xsd] doesn't exists. When I
> replace:
> {code:java}
> ---
> a/enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/jboss-common_6_0_1.xsd
> +++
> b/enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/jboss-common_6_0_1.xsd
> @@ -61,7 +61,7 @@
> consistency with the Servlet API.
>
>
> - http://java.sun.com/xml/ns/javaee";
> schemaLocation="http://java.sun.com/xml/ns/javaee/javaee_6.xsd"/>
> + http://java.sun.com/xml/ns/javaee";
> schemaLocation="javaee_6.xsd"/>
>
>
> {code}
> Then my build succeeds. Btw. I did a grep and there are more places that
> would deserve replacement:
> {code:java}
> netbeans$ grep -r xsd.import.*namespace enterprise/javaee.wildfly/src/
> enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/javaee_6.xsd:
> http://www.w3.org/XML/1998/namespace";
> enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/jboss-web_14_1.xsd:
> http://xmlns.jcp.org/xml/ns/javaee";
> schemaLocation="http://www.jboss.org/schema/jbossas/web-app_4_0.xsd"/>
> enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/jboss-common_6_0_1.xsd:
> http://java.sun.com/xml/ns/javaee";
> schemaLocation="javaee_6.xsd"/>
> enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/jboss-common_8_1.xsd:
> http://xmlns.jcp.org/xml/ns/javaee";
> schemaLocation="http://www.jboss.org/schema/jbossas/javaee_8.xsd"/>
> enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/javaee_8.xsd:
> http://www.w3.org/XML/1998/namespace";
> enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/jboss-web_7_3_1.xsd:
> http://java.sun.com/xml/ns/javaee";
> schemaLocation="http://www.jboss.org/schema/jbossas/web-app_3_0.xsd"/>
> {code}
> however when I tried to replace the other, I got missing file errors like
> {{FileNotFoundException:
> netbeans/enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/web-common_4_0.xsd}}
> - I guess there are additional transitive dependencies that need to be
> fixed. As such I decided to leave a note here rather than fixing just the one
> xsd file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4836) Travis build random failure for java.hints and other modules.
[
https://issues.apache.org/jira/browse/NETBEANS-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203866#comment-17203866
]
Jaroslav Tulach edited comment on NETBEANS-4836 at 9/29/20, 11:31 AM:
--
FYI: Consider using {{timeOut()}} feature of {{NbTestCase}} as described among
other test patterns: https://openide.netbeans.org/tutorial/test-patterns.html
was (Author: jtulach):
FYI: Consider using {{timeOut()}} feature of {{NbTestCase}} as described among
other test patterns:
[+https://openide.netbeans.org/tutorial/test-patterns.html+]
> Travis build random failure for java.hints and other modules.
> -
>
> Key: NETBEANS-4836
> URL: https://issues.apache.org/jira/browse/NETBEANS-4836
> Project: NetBeans
> Issue Type: Bug
>Reporter: Akhilesh Singh
>Priority: Critical
> Labels: travis-ci
>
> Travis builds are failed randomly for java.hints and other modules. Identify
> the timed out test cases and mark all of them as @RandomlyFails.
> [https://travis-ci.org/github/apache/netbeans/builds/]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4836) Travis build random failure for java.hints and other modules.
[
https://issues.apache.org/jira/browse/NETBEANS-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203866#comment-17203866
]
Jaroslav Tulach commented on NETBEANS-4836:
---
FYI: Consider using {{timeOut()}} feature of {{NbTestCase}} as described among
other test patterns:
[+https://openide.netbeans.org/tutorial/test-patterns.html+]
> Travis build random failure for java.hints and other modules.
> -
>
> Key: NETBEANS-4836
> URL: https://issues.apache.org/jira/browse/NETBEANS-4836
> Project: NetBeans
> Issue Type: Bug
>Reporter: Akhilesh Singh
>Priority: Critical
> Labels: travis-ci
>
> Travis builds are failed randomly for java.hints and other modules. Identify
> the timed out test cases and mark all of them as @RandomlyFails.
> [https://travis-ci.org/github/apache/netbeans/builds/]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4821) Cannot attach JavaFX Bean Info sources to Gradle library
[
https://issues.apache.org/jira/browse/NETBEANS-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach reassigned NETBEANS-4821:
-
Assignee: Anton Epple (was: Laszlo Kishalmi)
> Cannot attach JavaFX Bean Info sources to Gradle library
>
>
> Key: NETBEANS-4821
> URL: https://issues.apache.org/jira/browse/NETBEANS-4821
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.1
>Reporter: Jaroslav Tulach
>Assignee: Anton Epple
>Priority: Trivial
> Attachments: image-2020-09-20-08-06-46-654.png
>
>
> I am developing a sample demo using Gradle and I am unable to debug into a
> library used in a test, as the source isn't available. To try:
> {code:java}
> $ git clone --single-branch --branch react4jdemo
> https://github.com/jtulach/netbeans-html4j react4jdemo
> $ cd react4jdemo
> # following identifies the exact version I have on local disk:
> react4jdemo$ git log | head -n5
> commit 1e18917d0be1fc090cc9500c8286119710a29fde
> Author: Jaroslav Tulach
> Date: Sun Sep 20 07:50:11 2020 +0200Verify component class is
> accessible before generating subclass{code}
> and open that and its {{api}} subproject in NetBeans 12.1. The following
> picture... !image-2020-09-20-08-06-46-654.png! ... shows what I did:
> * expand the API's project junit-browser-runner library
> * select BrowserRunner.class file
> * right click, Open => opens the bytecode
> * click "Attach Sources" and "Download"
> * an error is shown
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4821) Cannot attach JavaFX Bean Info sources to Gradle library
[
https://issues.apache.org/jira/browse/NETBEANS-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-4821:
--
Summary: Cannot attach JavaFX Bean Info sources to Gradle library (was:
Cannot attach sources to Gradle library)
> Cannot attach JavaFX Bean Info sources to Gradle library
>
>
> Key: NETBEANS-4821
> URL: https://issues.apache.org/jira/browse/NETBEANS-4821
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.1
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Trivial
> Attachments: image-2020-09-20-08-06-46-654.png
>
>
> I am developing a sample demo using Gradle and I am unable to debug into a
> library used in a test, as the source isn't available. To try:
> {code:java}
> $ git clone --single-branch --branch react4jdemo
> https://github.com/jtulach/netbeans-html4j react4jdemo
> $ cd react4jdemo
> # following identifies the exact version I have on local disk:
> react4jdemo$ git log | head -n5
> commit 1e18917d0be1fc090cc9500c8286119710a29fde
> Author: Jaroslav Tulach
> Date: Sun Sep 20 07:50:11 2020 +0200Verify component class is
> accessible before generating subclass{code}
> and open that and its {{api}} subproject in NetBeans 12.1. The following
> picture... !image-2020-09-20-08-06-46-654.png! ... shows what I did:
> * expand the API's project junit-browser-runner library
> * select BrowserRunner.class file
> * right click, Open => opens the bytecode
> * click "Attach Sources" and "Download"
> * an error is shown
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4847) Changing set of modules in Module suite adds always adds applemenu & performance
[
https://issues.apache.org/jira/browse/NETBEANS-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202518#comment-17202518
]
Jaroslav Tulach commented on NETBEANS-4847:
---
{{applemenu.jdk9}} has been removed from the code base a week or two ago, btw.
> Changing set of modules in Module suite adds always adds applemenu &
> performance
>
>
> Key: NETBEANS-4847
> URL: https://issues.apache.org/jira/browse/NETBEANS-4847
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Project
>Affects Versions: 11.3
>Reporter: Svatopluk Dedic
>Priority: Major
>
> When I exclude some modules from module suite (working with IDE cluster), the
> GUI always removes some exclusions == adds certain modules back:
> - applemenu.jdk9
> - performance
> - performance.java
> // cc:[~jtulach]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4848) Annotation processing in Gradle 4.10 vs. 6.x versions
[
https://issues.apache.org/jira/browse/NETBEANS-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202245#comment-17202245
]
Jaroslav Tulach commented on NETBEANS-4848:
---
Using Tools/Options/Java/Gradle and setting _Use Standard Gradle Version to
4.10_ (and restarting) fixes the problem. However I don't want to change the
Gradle version for all projects. Couldn't the IDE use `gradlew` to deduce the
classpath/processor path? Btw. the checkbox _Preffer to use Gradle Wrapper that
Comes with the Project_ is checked.
> Annotation processing in Gradle 4.10 vs. 6.x versions
> -
>
> Key: NETBEANS-4848
> URL: https://issues.apache.org/jira/browse/NETBEANS-4848
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.0, 12.1
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Major
>
> A description of a problem shall not start with finding the root cause, but
> be it: It never stops surprising me how incompatible Gradle is. I have
> written some {{build.gradle}} scripts for some version of Gradle, but then
> after few new releases, those scripts don't work at all. The fix is simple:
> include `gradlew` in your repository and fix Gradle version, but this is
> so(!) different compared to Maven! Let me explain the problem:
> * Follow [the
> steps|https://github.com/JaroslavTulach/oraclejet4j/blob/master/README.md]
> and get the repository, commit
> [eee35b7|https://github.com/JaroslavTulach/oraclejet4j/commit/eee35b737795ef03c45028c0809b388aa8552367]
> * Usage from command line works, but:
> * Open the project in NetBeans. There are errors in {{RootViewModel}} class
> My IDE cannot find {{RootViewModelBase}}, {{NavItemBase}},
> {{FooterLinkBase}}. Those classes are generated by annotation processor
> (\{{"com.dukescript.api:javafx.beaninfo:0.6"}}). A normal behavior of
> {{javac}} is to locate all annotation processors on "compile" class path and
> use them. Gradle 4.10 does that. New versions of Gradle don't do that().
>
> I assume NetBeans 12.x is using new version of Gradle internally and as such,
> it doesn't find the annotation processor. As such the code is rendered as
> broken. Can we fix that somehow (without rewriting the project to Maven ;))?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4848) Annotation processing in Gradle 4.10 vs. 6.x versions
Jaroslav Tulach created NETBEANS-4848:
-
Summary: Annotation processing in Gradle 4.10 vs. 6.x versions
Key: NETBEANS-4848
URL: https://issues.apache.org/jira/browse/NETBEANS-4848
Project: NetBeans
Issue Type: Bug
Components: projects - Gradle
Affects Versions: 12.0, 12.1
Reporter: Jaroslav Tulach
Assignee: Laszlo Kishalmi
A description of a problem shall not start with finding the root cause, but be
it: It never stops surprising me how incompatible Gradle is. I have written
some {{build.gradle}} scripts for some version of Gradle, but then after few
new releases, those scripts don't work at all. The fix is simple: include
`gradlew` in your repository and fix Gradle version, but this is so(!)
different compared to Maven! Let me explain the problem:
* Follow [the
steps|https://github.com/JaroslavTulach/oraclejet4j/blob/master/README.md] and
get the repository, commit
[eee35b7|https://github.com/JaroslavTulach/oraclejet4j/commit/eee35b737795ef03c45028c0809b388aa8552367]
* Usage from command line works, but:
* Open the project in NetBeans. There are errors in {{RootViewModel}} class
My IDE cannot find {{RootViewModelBase}}, {{NavItemBase}}, {{FooterLinkBase}}.
Those classes are generated by annotation processor
(\{{"com.dukescript.api:javafx.beaninfo:0.6"}}). A normal behavior of {{javac}}
is to locate all annotation processors on "compile" class path and use them.
Gradle 4.10 does that. New versions of Gradle don't do that().
I assume NetBeans 12.x is using new version of Gradle internally and as such,
it doesn't find the annotation processor. As such the code is rendered as
broken. Can we fix that somehow (without rewriting the project to Maven ;))?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4845) javaee.wildfly cannot be built without access to network
Jaroslav Tulach created NETBEANS-4845:
-
Summary: javaee.wildfly cannot be built without access to network
Key: NETBEANS-4845
URL: https://issues.apache.org/jira/browse/NETBEANS-4845
Project: NetBeans
Issue Type: Bug
Components: serverplugins - WildFly
Affects Versions: 12.0, 12.1
Reporter: Jaroslav Tulach
Assignee: Emmanuel Hugonnet
Hello Emmanuel,
as noted
[PR-2000|https://github.com/apache/netbeans/pull/2000#issuecomment-675890873] I
have troubles building *wildfly* support behind corporate proxy. Probably the
goal of "Removing external downloads and updating schemas" wasn't fully
fulfilled. My proxy says that [http://java.sun.com/xml/ns/javaee/javaee_6.xsd]
doesn't exists. When I replace:
{code:java}
---
a/enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/jboss-common_6_0_1.xsd
+++
b/enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/jboss-common_6_0_1.xsd
@@ -61,7 +61,7 @@
consistency with the Servlet API.
- http://java.sun.com/xml/ns/javaee";
schemaLocation="http://java.sun.com/xml/ns/javaee/javaee_6.xsd"/>
+ http://java.sun.com/xml/ns/javaee";
schemaLocation="javaee_6.xsd"/>
{code}
Then my build succeeds. Btw. I did a grep and there are more places that would
deserve replacement:
{code:java}
netbeans$ grep -r xsd.import.*namespace enterprise/javaee.wildfly/src/
enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/javaee_6.xsd:
http://www.w3.org/XML/1998/namespace";
enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/jboss-web_14_1.xsd:
http://xmlns.jcp.org/xml/ns/javaee";
schemaLocation="http://www.jboss.org/schema/jbossas/web-app_4_0.xsd"/>
enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/jboss-common_6_0_1.xsd:
http://java.sun.com/xml/ns/javaee";
schemaLocation="javaee_6.xsd"/>
enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/jboss-common_8_1.xsd:
http://xmlns.jcp.org/xml/ns/javaee";
schemaLocation="http://www.jboss.org/schema/jbossas/javaee_8.xsd"/>
enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/javaee_8.xsd:
http://www.w3.org/XML/1998/namespace";
enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/jboss-web_7_3_1.xsd:
http://java.sun.com/xml/ns/javaee";
schemaLocation="http://www.jboss.org/schema/jbossas/web-app_3_0.xsd"/>
{code}
however when I tried to replace the other, I got missing file errors like
{{FileNotFoundException:
netbeans/enterprise/javaee.wildfly/src/org/netbeans/modules/javaee/wildfly/resources/web-common_4_0.xsd}}
- I guess there are additional transitive dependencies that need to be fixed.
As such I decided to leave a note here rather than fixing just the one xsd file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Closed] (NETBEANSINFRA-12) NetBeans Platform Cluster pom.xml RELEASE120 has broken dependencies!
[
https://issues.apache.org/jira/browse/NETBEANSINFRA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach closed NETBEANSINFRA-12.
Thanks.
> NetBeans Platform Cluster pom.xml RELEASE120 has broken dependencies!
> -
>
> Key: NETBEANSINFRA-12
> URL: https://issues.apache.org/jira/browse/NETBEANSINFRA-12
> Project: Apache NetBeans Infra
> Issue Type: Bug
> Components: MU - Apache NetBeans nb repository plugin
>Reporter: Jaroslav Tulach
>Assignee: Eric Barboni
>Priority: Blocker
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> While working on https://github.com/apache/netbeans/pull/1738 I realized that
> the Maven name given to org.netbeans.external:net.java.html:1.7 is wrong and
> it needlessly complicates the integration with rest of the utilities that
> rely on upstream org.netbeans.html:net.java.html:1.7 name.
> There is a code that tries to {{findExternal}} in Maven Utilities module:
> https://github.com/apache/netbeans-mavenutils-nb-repository-plugin/blob/master/src/main/java/org/apache/netbeans/nbm/repository/PopulateRepositoryMojo.java#L426
> However it is not yet implemented. Anyway, many of our OSGi bundles come from
> Maven central and they should be referenced with their real Maven
> co-ordinates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4821) Cannot attach sources to Gradle library
[
https://issues.apache.org/jira/browse/NETBEANS-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198914#comment-17198914
]
Jaroslav Tulach commented on NETBEANS-4821:
---
Thanks Laszlo. I have to correct my claim that it works in Maven. It doesn't
work either. The reason is that
[https://repo1.maven.org/maven2/com/dukescript/api/junit-browser-runner/1.0/]
seems to be missing the source JAR all together!
(how could Toni upload a project without sources to Maven central is a mistery,
I thought it cannot pass Nexus checks without sources!)
Maybe a better indication of what the IDE tried and failed would be good. But
otherwise my report is certainly not of any high priority. Maybe for
[~monacotoni] to fix the artifact...
> Cannot attach sources to Gradle library
> ---
>
> Key: NETBEANS-4821
> URL: https://issues.apache.org/jira/browse/NETBEANS-4821
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.1
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Minor
> Attachments: image-2020-09-20-08-06-46-654.png
>
>
> I am developing a sample demo using Gradle and I am unable to debug into a
> library used in a test, as the source isn't available. To try:
> {code:java}
> $ git clone --single-branch --branch react4jdemo
> https://github.com/jtulach/netbeans-html4j react4jdemo
> $ cd react4jdemo
> # following identifies the exact version I have on local disk:
> react4jdemo$ git log | head -n5
> commit 1e18917d0be1fc090cc9500c8286119710a29fde
> Author: Jaroslav Tulach
> Date: Sun Sep 20 07:50:11 2020 +0200Verify component class is
> accessible before generating subclass{code}
> and open that and its {{api}} subproject in NetBeans 12.1. The following
> picture... !image-2020-09-20-08-06-46-654.png! ... shows what I did:
> * expand the API's project junit-browser-runner library
> * select BrowserRunner.class file
> * right click, Open => opens the bytecode
> * click "Attach Sources" and "Download"
> * an error is shown
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4821) Cannot attach sources to Gradle library
[
https://issues.apache.org/jira/browse/NETBEANS-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-4821:
--
Priority: Trivial (was: Minor)
> Cannot attach sources to Gradle library
> ---
>
> Key: NETBEANS-4821
> URL: https://issues.apache.org/jira/browse/NETBEANS-4821
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.1
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Trivial
> Attachments: image-2020-09-20-08-06-46-654.png
>
>
> I am developing a sample demo using Gradle and I am unable to debug into a
> library used in a test, as the source isn't available. To try:
> {code:java}
> $ git clone --single-branch --branch react4jdemo
> https://github.com/jtulach/netbeans-html4j react4jdemo
> $ cd react4jdemo
> # following identifies the exact version I have on local disk:
> react4jdemo$ git log | head -n5
> commit 1e18917d0be1fc090cc9500c8286119710a29fde
> Author: Jaroslav Tulach
> Date: Sun Sep 20 07:50:11 2020 +0200Verify component class is
> accessible before generating subclass{code}
> and open that and its {{api}} subproject in NetBeans 12.1. The following
> picture... !image-2020-09-20-08-06-46-654.png! ... shows what I did:
> * expand the API's project junit-browser-runner library
> * select BrowserRunner.class file
> * right click, Open => opens the bytecode
> * click "Attach Sources" and "Download"
> * an error is shown
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4821) Cannot attach sources to Gradle library
[
https://issues.apache.org/jira/browse/NETBEANS-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-4821:
--
Description:
I am developing a sample demo using Gradle and I am unable to debug into a
library used in a test, as the source isn't available. To try:
{code:java}
$ git clone --single-branch --branch react4jdemo
https://github.com/jtulach/netbeans-html4j react4jdemo
$ cd react4jdemo
# following identifies the exact version I have on local disk:
react4jdemo$ git log | head -n5
commit 1e18917d0be1fc090cc9500c8286119710a29fde
Author: Jaroslav Tulach
Date: Sun Sep 20 07:50:11 2020 +0200Verify component class is accessible
before generating subclass{code}
and open that and its {{api}} subproject in NetBeans 12.1. The following
picture... !image-2020-09-20-08-06-46-654.png! ... shows what I did:
* expand the API's project junit-browser-runner library
* select BrowserRunner.class file
* right click, Open => opens the bytecode
* click "Attach Sources" and "Download"
* an error is shown
was:
I am developing a sample demo using Gradle and I am unable to debug into a
library used in a test, as the source isn't available. To try:
{code:java}
$ git clone --single-branch --branch react4jdemo
https://github.com/jtulach/netbeans-html4j react4jdemo
$ cd react4jdemo
# following identifies the exact version I have on local disk:
react4jdemo$ git log | head -n5
commit 1e18917d0be1fc090cc9500c8286119710a29fde
Author: Jaroslav Tulach
Date: Sun Sep 20 07:50:11 2020 +0200Verify component class is accessible
before generating subclass{code}
and open that and its {{api}} subproject in NetBeans 12.1. The following
picture... !image-2020-09-20-08-06-46-654.png! ... shows what I did:
* expand the API's project junit-browser-runner library
* select BrowserRunner.class file
* right click, Open => opens the bytecode
* click "Attach Sources" and "Download"
* an error is shown
I am pretty sure the above workflow would work in a Maven project.
> Cannot attach sources to Gradle library
> ---
>
> Key: NETBEANS-4821
> URL: https://issues.apache.org/jira/browse/NETBEANS-4821
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.1
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Minor
> Attachments: image-2020-09-20-08-06-46-654.png
>
>
> I am developing a sample demo using Gradle and I am unable to debug into a
> library used in a test, as the source isn't available. To try:
> {code:java}
> $ git clone --single-branch --branch react4jdemo
> https://github.com/jtulach/netbeans-html4j react4jdemo
> $ cd react4jdemo
> # following identifies the exact version I have on local disk:
> react4jdemo$ git log | head -n5
> commit 1e18917d0be1fc090cc9500c8286119710a29fde
> Author: Jaroslav Tulach
> Date: Sun Sep 20 07:50:11 2020 +0200Verify component class is
> accessible before generating subclass{code}
> and open that and its {{api}} subproject in NetBeans 12.1. The following
> picture... !image-2020-09-20-08-06-46-654.png! ... shows what I did:
> * expand the API's project junit-browser-runner library
> * select BrowserRunner.class file
> * right click, Open => opens the bytecode
> * click "Attach Sources" and "Download"
> * an error is shown
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4821) Cannot attach sources to Gradle library
[
https://issues.apache.org/jira/browse/NETBEANS-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-4821:
--
Description:
I am developing a sample demo using Gradle and I am unable to debug into a
library used in a test, as the source isn't available. To try:
{code:java}
$ git clone --single-branch --branch react4jdemo
https://github.com/jtulach/netbeans-html4j react4jdemo
$ cd react4jdemo
# following identifies the exact version I have on local disk:
react4jdemo$ git log | head -n5
commit 1e18917d0be1fc090cc9500c8286119710a29fde
Author: Jaroslav Tulach
Date: Sun Sep 20 07:50:11 2020 +0200Verify component class is accessible
before generating subclass{code}
and open that and its {{api}} subproject in NetBeans 12.1. The following
picture... !image-2020-09-20-08-06-46-654.png! ... shows what I did:
* expand the API's project junit-browser-runner library
* select BrowserRunner.class file
* right click, Open => opens the bytecode
* click "Attach Sources" and "Download"
* an error is shown
I am pretty sure the above workflow would work in a Maven project.
was:
I am developing a sample demo using Gradle and I am unable to debug into a
library used in a test, as the source isn't available. To try:
{code:java}
$ git clone --single-branch --branch react4jdemo
https://github.com/jtulach/netbeans-html4j react4jdemo
$ cd react4jdemo{code}
and open that and its {{api}} subproject in NetBeans 12.1. The following
picture... !image-2020-09-20-08-06-46-654.png! ... shows what I did:
* expand the API's project junit-browser-runner library
* select BrowserRunner.class file
* right click, Open => opens the bytecode
* click "Attach Sources" and "Download"
* an error is shown
I am pretty sure the above workflow would work in a Maven project.
> Cannot attach sources to Gradle library
> ---
>
> Key: NETBEANS-4821
> URL: https://issues.apache.org/jira/browse/NETBEANS-4821
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.1
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Minor
> Attachments: image-2020-09-20-08-06-46-654.png
>
>
> I am developing a sample demo using Gradle and I am unable to debug into a
> library used in a test, as the source isn't available. To try:
> {code:java}
> $ git clone --single-branch --branch react4jdemo
> https://github.com/jtulach/netbeans-html4j react4jdemo
> $ cd react4jdemo
> # following identifies the exact version I have on local disk:
> react4jdemo$ git log | head -n5
> commit 1e18917d0be1fc090cc9500c8286119710a29fde
> Author: Jaroslav Tulach
> Date: Sun Sep 20 07:50:11 2020 +0200Verify component class is
> accessible before generating subclass{code}
> and open that and its {{api}} subproject in NetBeans 12.1. The following
> picture... !image-2020-09-20-08-06-46-654.png! ... shows what I did:
> * expand the API's project junit-browser-runner library
> * select BrowserRunner.class file
> * right click, Open => opens the bytecode
> * click "Attach Sources" and "Download"
> * an error is shown
> I am pretty sure the above workflow would work in a Maven project.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4821) Cannot attach sources to Gradle library
[
https://issues.apache.org/jira/browse/NETBEANS-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-4821:
--
Description:
I am developing a sample demo using Gradle and I am unable to debug into a
library used in a test, as the source isn't available. To try:
{code:java}
$ git clone --single-branch --branch react4jdemo
https://github.com/jtulach/netbeans-html4j react4jdemo
$ cd react4jdemo{code}
and open that and its {{api}} subproject in NetBeans 12.1. The following
picture... !image-2020-09-20-08-06-46-654.png! ... shows what I did:
* expand the API's project junit-browser-runner library
* select BrowserRunner.class file
* right click, Open => opens the bytecode
* click "Attach Sources" and "Download"
* an error is shown
I am pretty sure the above workflow would work in a Maven project.
was:
I am developing a sample demo using Gradle and I am unable to debug into a
library used in a test, as the source isn't available. To try:
{code:java}
$ git clone --single-branch --branch react4jdemo
https://github.com/jtulach/netbeans-html4j react4jdemo
$ cd react4jdemo{code}
and open that and its {{api}} subproject in NetBeans 12.1. The attached picture
shows what I did:
* expand the API's project junit-browser-runner library
* select BrowserRunner.class file
* right click, Open => opens the bytecode
* click "Attach Sources" and "Download"
* an error is shown
I am pretty sure the above workflow would work in a Maven project.
> Cannot attach sources to Gradle library
> ---
>
> Key: NETBEANS-4821
> URL: https://issues.apache.org/jira/browse/NETBEANS-4821
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.1
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Minor
> Attachments: image-2020-09-20-08-06-46-654.png
>
>
> I am developing a sample demo using Gradle and I am unable to debug into a
> library used in a test, as the source isn't available. To try:
> {code:java}
> $ git clone --single-branch --branch react4jdemo
> https://github.com/jtulach/netbeans-html4j react4jdemo
> $ cd react4jdemo{code}
> and open that and its {{api}} subproject in NetBeans 12.1. The following
> picture... !image-2020-09-20-08-06-46-654.png! ... shows what I did:
> * expand the API's project junit-browser-runner library
> * select BrowserRunner.class file
> * right click, Open => opens the bytecode
> * click "Attach Sources" and "Download"
> * an error is shown
> I am pretty sure the above workflow would work in a Maven project.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4821) Cannot attach sources to Gradle library
Jaroslav Tulach created NETBEANS-4821:
-
Summary: Cannot attach sources to Gradle library
Key: NETBEANS-4821
URL: https://issues.apache.org/jira/browse/NETBEANS-4821
Project: NetBeans
Issue Type: Bug
Components: projects - Gradle
Affects Versions: 12.1
Reporter: Jaroslav Tulach
Assignee: Laszlo Kishalmi
Attachments: image-2020-09-20-08-06-46-654.png
I am developing a sample demo using Gradle and I am unable to debug into a
library used in a test, as the source isn't available. To try:
{code:java}
$ git clone --single-branch --branch react4jdemo
https://github.com/jtulach/netbeans-html4j react4jdemo
$ cd react4jdemo{code}
and open that and its {{api}} subproject in NetBeans 12.1. The attached picture
shows what I did:
* expand the API's project junit-browser-runner library
* select BrowserRunner.class file
* right click, Open => opens the bytecode
* click "Attach Sources" and "Download"
* an error is shown
I am pretty sure the above workflow would work in a Maven project.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4765) module-info utilities for common usage
[
https://issues.apache.org/jira/browse/NETBEANS-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193999#comment-17193999
]
Jaroslav Tulach edited comment on NETBEANS-4765 at 9/11/20, 5:40 AM:
-
Right, you can only eliminate the duplicities by introducing an API, CCing
Tomáš Zezula.
was (Author: jtulach):
Right you can only eliminate the duplicities by introducing an API, CCing Tomáš
Zezula.
> module-info utilities for common usage
> --
>
> Key: NETBEANS-4765
> URL: https://issues.apache.org/jira/browse/NETBEANS-4765
> Project: NetBeans
> Issue Type: Improvement
> Components: java - Platform
>Reporter: Ernie Rael
>Priority: Major
>
> The only common api I've seen for working with module-info is
> {code:java}
> org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
> {code}
> There are several other things that need to be done with module-info. For
> example, adding a package for fxml access, or for refactoring when moving an
> exported java class to a different package.
> There are module-info utilities scattered throughout the netbeans codebase.
> For example
> {code:java}
> ./maven/src/org/netbeans/modules/maven/api/ModuleInfoUtils.java
> ./maven/src/org/netbeans/modules/maven/ModuleInfoSupport.java
> {code}
> and there's a pending fix for NETBEANS-4718 which adds a local
> "hasModuleInfo".
> And notice sitting in .../netbeans/java there are 64 files given by
> {code}
> srcgrep -l module-info | grep -E -v '/test/|/build/'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4765) module-info utilities for common usage
[
https://issues.apache.org/jira/browse/NETBEANS-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193999#comment-17193999
]
Jaroslav Tulach commented on NETBEANS-4765:
---
Right you can only eliminate the duplicities by introducing an API, CCing Tomáš
Zezula.
> module-info utilities for common usage
> --
>
> Key: NETBEANS-4765
> URL: https://issues.apache.org/jira/browse/NETBEANS-4765
> Project: NetBeans
> Issue Type: Improvement
> Components: java - Platform
>Reporter: Ernie Rael
>Priority: Major
>
> The only common api I've seen for working with module-info is
> {code:java}
> org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
> {code}
> There are several other things that need to be done with module-info. For
> example, adding a package for fxml access, or for refactoring when moving an
> exported java class to a different package.
> There are module-info utilities scattered throughout the netbeans codebase.
> For example
> {code:java}
> ./maven/src/org/netbeans/modules/maven/api/ModuleInfoUtils.java
> ./maven/src/org/netbeans/modules/maven/ModuleInfoSupport.java
> {code}
> and there's a pending fix for NETBEANS-4718 which adds a local
> "hasModuleInfo".
> And notice sitting in .../netbeans/java there are 64 files given by
> {code}
> srcgrep -l module-info | grep -E -v '/test/|/build/'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4746) Running test in Maven is slower than in Ant
[
https://issues.apache.org/jira/browse/NETBEANS-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191189#comment-17191189
]
Jaroslav Tulach commented on NETBEANS-4746:
---
Comments from:
*
[Jesse|http://mail-archives.apache.org/mod_mbox/netbeans-dev/202009.mbox/%3CCAPFHdOu6fxOm%3DsKdOb-brHf8D9PHYVwDWRsdn0LEjpknmu-Ksg%40mail.gmail.com%3E]
- cold JVM is a problem
*
[Tim|http://mail-archives.apache.org/mod_mbox/netbeans-dev/202009.mbox/%3CCA%2BqecROFK1o1uNoPgUgW-_PKfP5Fouy4bJerLhOeNqdNmbsgtA%40mail.gmail.com%3E]
- I/O is the problem for large projects
Thank you guys.
> Running test in Maven is slower than in Ant
> ---
>
> Key: NETBEANS-4746
> URL: https://issues.apache.org/jira/browse/NETBEANS-4746
> Project: NetBeans
> Issue Type: Task
> Components: projects - Maven
>Affects Versions: 12.0
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Minor
> Attachments: justtest.diff, preexec-6.patch
>
>
> NetBeans users has just recently complained that Maven support is slower than
> Ant - some even claimed they [rather maintain dual Ant script
> support|http://mail-archives.apache.org/mod_mbox//netbeans-dev/202008.mbox/browser]
> than wait for Maven to launch. I've created this issue to investigate the
> problem.
> First of all we need a sample project: [^justtest.diff] - apply it {{patch
> -p1 it with Maven:
> {code:java}
> $ time JAVA_HOME=~/bin/jdk-8/ mvn -quiet
> -Dtest=com.mycompany.justtest.MainTest process-test-classes surefire:test
> ---
> T E S T S
> ---
> Running com.mycompany.justtest.MainTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.071 sec
> Results :Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> real0m2,633s
> user0m6,986s
> sys 0m0,257s
> {code}
> and you can also run it with Ant:
> {code:java}
> time JAVA_HOME=~/bin/jdk-8/ ant -q test-single
> -Djavac.includes=com/mycompany/justtest/MainTest.java
> -Dtest.includes=com/mycompany/justtest/MainTest.java
> BUILD SUCCESSFUL
> Total time: 1 second
> real0m1,899s
> user0m4,250s
> sys 0m0,244s
> {code}
> 2.6s vs. 1.9s! Really? Is that the problem? Probably not, I guess the
> difference is the integration into the IDE then.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4746) Running test in Maven is slower than in Ant
[
https://issues.apache.org/jira/browse/NETBEANS-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-4746:
--
Attachment: preexec-6.patch
> Running test in Maven is slower than in Ant
> ---
>
> Key: NETBEANS-4746
> URL: https://issues.apache.org/jira/browse/NETBEANS-4746
> Project: NetBeans
> Issue Type: Task
> Components: projects - Maven
>Affects Versions: 12.0
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Minor
> Attachments: justtest.diff, preexec-6.patch
>
>
> NetBeans users has just recently complained that Maven support is slower than
> Ant - some even claimed they [rather maintain dual Ant script
> support|http://mail-archives.apache.org/mod_mbox//netbeans-dev/202008.mbox/browser]
> than wait for Maven to launch. I've created this issue to investigate the
> problem.
> First of all we need a sample project: [^justtest.diff] - apply it {{patch
> -p1 it with Maven:
> {code:java}
> $ time JAVA_HOME=~/bin/jdk-8/ mvn -quiet
> -Dtest=com.mycompany.justtest.MainTest process-test-classes surefire:test
> ---
> T E S T S
> ---
> Running com.mycompany.justtest.MainTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.071 sec
> Results :Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> real0m2,633s
> user0m6,986s
> sys 0m0,257s
> {code}
> and you can also run it with Ant:
> {code:java}
> time JAVA_HOME=~/bin/jdk-8/ ant -q test-single
> -Djavac.includes=com/mycompany/justtest/MainTest.java
> -Dtest.includes=com/mycompany/justtest/MainTest.java
> BUILD SUCCESSFUL
> Total time: 1 second
> real0m1,899s
> user0m4,250s
> sys 0m0,244s
> {code}
> 2.6s vs. 1.9s! Really? Is that the problem? Probably not, I guess the
> difference is the integration into the IDE then.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4746) Running test in Maven is slower than in Ant
[
https://issues.apache.org/jira/browse/NETBEANS-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190531#comment-17190531
]
Jaroslav Tulach commented on NETBEANS-4746:
---
[^preexec-6.patch] is a patch that creates the zombie instance of Maven process
and uses it when user invokes an action.
> Running test in Maven is slower than in Ant
> ---
>
> Key: NETBEANS-4746
> URL: https://issues.apache.org/jira/browse/NETBEANS-4746
> Project: NetBeans
> Issue Type: Task
> Components: projects - Maven
>Affects Versions: 12.0
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Minor
> Attachments: justtest.diff, preexec-6.patch
>
>
> NetBeans users has just recently complained that Maven support is slower than
> Ant - some even claimed they [rather maintain dual Ant script
> support|http://mail-archives.apache.org/mod_mbox//netbeans-dev/202008.mbox/browser]
> than wait for Maven to launch. I've created this issue to investigate the
> problem.
> First of all we need a sample project: [^justtest.diff] - apply it {{patch
> -p1 it with Maven:
> {code:java}
> $ time JAVA_HOME=~/bin/jdk-8/ mvn -quiet
> -Dtest=com.mycompany.justtest.MainTest process-test-classes surefire:test
> ---
> T E S T S
> ---
> Running com.mycompany.justtest.MainTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.071 sec
> Results :Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> real0m2,633s
> user0m6,986s
> sys 0m0,257s
> {code}
> and you can also run it with Ant:
> {code:java}
> time JAVA_HOME=~/bin/jdk-8/ ant -q test-single
> -Djavac.includes=com/mycompany/justtest/MainTest.java
> -Dtest.includes=com/mycompany/justtest/MainTest.java
> BUILD SUCCESSFUL
> Total time: 1 second
> real0m1,899s
> user0m4,250s
> sys 0m0,244s
> {code}
> 2.6s vs. 1.9s! Really? Is that the problem? Probably not, I guess the
> difference is the integration into the IDE then.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4769) Opening OutputTab instantiates PauseInGraalVM & co.
Jaroslav Tulach created NETBEANS-4769:
-
Summary: Opening OutputTab instantiates PauseInGraalVM & co.
Key: NETBEANS-4769
URL: https://issues.apache.org/jira/browse/NETBEANS-4769
Project: NetBeans
Issue Type: Bug
Components: platform - Actions
Reporter: Jaroslav Tulach
Assignee: Svata Dedic
While debugging GraalVM support I realized that "Pause in GraalVM Script"
action is being created even it shouldn't be. The problem is in Output window.
It asks for a shortcut for some action (copy-to-clipboard) and that triggers
instantiation of many other unrelated actions like the "Pause in GraalVM
Script". This is the stacktraces I have seen in debugger:
{code:java}
PauseInGraalScriptActionProvider.createAction:174
Hidden Source Calls
Method.invoke:498
BinaryFS$AttrImpl$MethodAndParams.invoke:730
BinaryFS$AttrImpl.getValue:660
BinaryFS$BFSBase.getAttribute:506
MultiFileObject.getAttribute:918
MultiFileObject.getAttribute:851
MultiFileObject.getAttribute:914
MultiFileObject.getAttribute:851
MultiFileObject.getAttribute:772
InstanceDataObject$Ser.instanceCreate:1407
InstanceDataObject.instanceCreate:821
LayersBridge.createAction:772
LayersBridge.initActions:206
LayersBridge.initActions:165
LayersBridge.getActions:133
KeymapModel$AL.run:178
KeymapModel.waitFinished:743
KeymapModel.ensureActionsLoaded:714
KeymapModel.isDuplicateId:365
ShortcutsFinderImpl.findActionForId:92
KeyStrokeUtils.getKeyStrokesForAction:216
OutputTab$TabAction.getAcceleratorsFor:1001
OutputTab$TabAction.:951
OutputTab.createActions:904
Loading frame description...
Loading frame description...
Loading frame description...
Loading frame description...
Loading frame description...
Loading frame description... {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[
https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189141#comment-17189141
]
Jaroslav Tulach commented on NETBEANS-4696:
---
-1 to removing {{org.netbeans.module.html.knockout}} module. HTML/Java supports
depends on it.
> NetBeans 12.1-beta1 sometimes hangs on open
> ---
>
> Key: NETBEANS-4696
> URL: https://issues.apache.org/jira/browse/NETBEANS-4696
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance
>Affects Versions: 12.1
> Environment: Linux (Debian "Buster")
> OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)
>Reporter: Glenn Holmer
>Priority: Major
> Attachments: 12.1-vc1-thread-dump-orac.txt,
> nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt,
> netbeans-12.1-thread-dump.txt
>
>
>
> NetBeans sometimes hangs on startup; the symptom is a stalled "Opening
> Projects" progress bar. I haven't been able to find a repro case, but I'm
> attaching a thread dump (from VisualVM) and screen shot.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[
https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189010#comment-17189010
]
Jaroslav Tulach edited comment on NETBEANS-4696 at 9/2/20, 6:20 AM:
The general rule to fight with deadlocks in an API is [never hold a lock when
calling foreign code|http://wiki.apidesign.org/wiki/Deadlock]. However in this
case it is not that easy to find out who's an API and who's the client. What
can help is to topologically sort and layer the modules according to their
runtime dependencies - the ones below are an API, the ones above are clients.
Then a callback from below to above which holds a lock would be problematic.
Such a callback is happening in the deadlock:
{code:java}
org.netbeans.modules.html.knockout.KOHtmlExtension.isCustomTag(KOHtmlExtension.java:302)
is being called by "lower" module:
org.netbeans.modules.html.editor.gsf.HtmlGSFParser$1.isCustomTag(HtmlGSFParser.java:109)
is being called by "lower" module:
org.netbeans.modules.html.editor.lib.api.SyntaxAnalyzerResult.doParseHtml(SyntaxAnalyzerResult.java:259)
is being called by "lower" module:
org.netbeans.modules.csl.navigation.ElementScanningTask$1.run(ElementScanningTask.java:149)
is being called by "lower" module:
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask {code}
Parsing API doesn't really hold a "lock", but it only runs in a single
dedicated thread (which is a shared, spare resource too). Can we avoid that?
Too hard, right [~tomas_zezula] & [~zezulato...@gmail.com] & [~tzezula]? This
is a core of the indexing infrastructure. We don't want to touch it. Who else
to blame?
Let's make a rule: Whoever registers an indexer, isn't allowed to make a call
to modules "above" Parsing API.
With such rule, it is clear that {{KOHtmlExtension}} breaks it by calling into
Project UI API . Take a look at [four deadlock
conditions|http://wiki.apidesign.org/wiki/Deadlock_conditions] and select one
to break the deadlock the simplest way. This would do it:
{code:java}
---
a/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
+++
b/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
@@ -27,6 +27,8 @@
import java.util.Map;
import java.util.WeakHashMap;
import java.util.concurrent.ExecutionException;
+import java.util.concurrent.TimeUnit;
+import java.util.concurrent.TimeoutException;
import java.util.logging.Logger;
import org.netbeans.api.project.Project;
import org.netbeans.api.project.ui.OpenProjects;
@@ -57,8 +59,8 @@
if (!areProjectsOpen) {
try {
// just be sure that the projects are open
-OpenProjects.getDefault().openProjects().get();
-} catch (InterruptedException | ExecutionException ex) {
+OpenProjects.getDefault().openProjects().get(10,
TimeUnit.SECONDS);
+} catch (InterruptedException | ExecutionException |
TimeoutException ex) {
Exceptions.printStackTrace(ex);
} finally {
areProjectsOpen = true; {code}
e.g. don't wait indefinitely. However given [Roman Svitanič's
comment|https://github.com/emilianbold/netbeans-releases/commit/30092308c4fef#diff-b6844ad6d2c225bbb1c8d6c0287d6a6cR80]
"just be sure that the projects are open" - I'd suggest to delete the whole
{{areProjectsOpen}} check. This shouldn't be here at all. If the dependency of
{{javascript2.knockout}} module on Project UI API can be removed, then even
better!
If you need a hotfix for 12.1, then I'd go with the 10s timeout shown above. In
the long term I suggest to apply following fix...
{code:java}
webcommon/javascript2.knockout$ git diff .
diff --git a/webcommon/javascript2.knockout/nbproject/project.xml
b/webcommon/javascript2.knockout/nbproject/project.xml
index 3f6fae4f8de0..47a191a3496d 100644
--- a/webcommon/javascript2.knockout/nbproject/project.xml
+++ b/webcommon/javascript2.knockout/nbproject/project.xml
@@ -96,15 +96,6 @@
1.61
-
-
org.netbeans.modules.projectuiapi.base
-
-
-
-1
-1.78
-
-
org.openide.filesystems
diff --git
a/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
b/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
index eec45ef5b673..42676c1e14d4 100644
---
a/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index
[jira] [Comment Edited] (NETBEANS-4696) NetBeans 12.1-beta1 sometimes hangs on open
[
https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189010#comment-17189010
]
Jaroslav Tulach edited comment on NETBEANS-4696 at 9/2/20, 6:17 AM:
The general rule to fight with deadlocks in an API is [never hold a lock when
calling foreign code|http://wiki.apidesign.org/wiki/Deadlock]. However in this
case it is not that easy to find out who's an API and who's the client. What
can help is to topologically sort and layer the modules according to their
runtime dependencies - the ones below are an API, the ones above are clients.
Then a callback from below to above which holds a lock would be problematic.
Such a callback is happening in the deadlock:
{code:java}
org.netbeans.modules.html.knockout.KOHtmlExtension.isCustomTag(KOHtmlExtension.java:302)
is being called by "lower" module:
org.netbeans.modules.html.editor.gsf.HtmlGSFParser$1.isCustomTag(HtmlGSFParser.java:109)
is being called by "lower" module:
org.netbeans.modules.html.editor.lib.api.SyntaxAnalyzerResult.doParseHtml(SyntaxAnalyzerResult.java:259)
is being called by "lower" module:
org.netbeans.modules.csl.navigation.ElementScanningTask$1.run(ElementScanningTask.java:149)
is being called by "lower" module:
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask {code}
Parsing API doesn't really hold a "lock", but it only runs in a single
dedicated thread (which is a shared, spare resource too). Can we avoid that?
Too hard, right [~tomas_zezula] & [~zezulato...@gmail.com] & [~tzezula]? This
is a core of the indexing infrastructure. We don't want to touch it. Who else
to blame?
Let's make a rule: Whoever registers an indexer, isn't allowed to make a call
to modules "above" Parsing API.
With such rule, it is clear that {{KOHtmlExtension}} breaks it by calling into
Project UI API . Take a look at [four deadlock
conditions|http://wiki.apidesign.org/wiki/Deadlock_conditions] and select one
to break the deadlock the simplest way. This would do it:
{code:java}
---
a/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
+++
b/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
@@ -27,6 +27,8 @@
import java.util.Map;
import java.util.WeakHashMap;
import java.util.concurrent.ExecutionException;
+import java.util.concurrent.TimeUnit;
+import java.util.concurrent.TimeoutException;
import java.util.logging.Logger;
import org.netbeans.api.project.Project;
import org.netbeans.api.project.ui.OpenProjects;
@@ -57,8 +59,8 @@
if (!areProjectsOpen) {
try {
// just be sure that the projects are open
-OpenProjects.getDefault().openProjects().get();
-} catch (InterruptedException | ExecutionException ex) {
+OpenProjects.getDefault().openProjects().get(10,
TimeUnit.SECONDS);
+} catch (InterruptedException | ExecutionException |
TimeoutException ex) {
Exceptions.printStackTrace(ex);
} finally {
areProjectsOpen = true; {code}
e.g. don't wait indefinitely. However given [Roman Svitanič's
comment|https://github.com/emilianbold/netbeans-releases/commit/30092308c4fef#diff-b6844ad6d2c225bbb1c8d6c0287d6a6cR80]
"just be sure that the projects are open" - I'd suggest to delete the whole
{{areProjectsOpen}} check. This shouldn't be here at all. If the dependency of
{{javascript2.knockout}} module on Project UI API can be removed, then even
better!
If you need a hotfix for 12.1, then I'd go with the 10s timeout shown above. In
the long term I suggest to apply following fix:
{code:java}
webcommon/javascript2.knockout$ git diff .
diff --git a/webcommon/javascript2.knockout/nbproject/project.xml
b/webcommon/javascript2.knockout/nbproject/project.xml
index 3f6fae4f8de0..47a191a3496d 100644
--- a/webcommon/javascript2.knockout/nbproject/project.xml
+++ b/webcommon/javascript2.knockout/nbproject/project.xml
@@ -96,15 +96,6 @@
1.61
-
-
org.netbeans.modules.projectuiapi.base
-
-
-
-1
-1.78
-
-
org.openide.filesystems
diff --git
a/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
b/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
index eec45ef5b673..42676c1e14d4 100644
---
a/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/K
[jira] [Comment Edited] (NETBEANS-4696) NetBeans 12.1-beta1 sometimes hangs on open
[
https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189010#comment-17189010
]
Jaroslav Tulach edited comment on NETBEANS-4696 at 9/2/20, 6:14 AM:
The general rule to fight with deadlocks in an API is [never hold a lock when
calling foreign code|http://wiki.apidesign.org/wiki/Deadlock]. However in this
case it is not that easy to find out who's an API and who's the client. What
can help is to topologically sort and layer the modules according to their
runtime dependencies - the ones below are an API, the ones above are clients.
Then a callback from below to above which holds a lock would be problematic.
Such a callback is happening in the deadlock:
{code:java}
org.netbeans.modules.html.knockout.KOHtmlExtension.isCustomTag(KOHtmlExtension.java:302)
is being called by "lower" module:
org.netbeans.modules.html.editor.gsf.HtmlGSFParser$1.isCustomTag(HtmlGSFParser.java:109)
is being called by "lower" module:
org.netbeans.modules.html.editor.lib.api.SyntaxAnalyzerResult.doParseHtml(SyntaxAnalyzerResult.java:259)
is being called by "lower" module:
org.netbeans.modules.csl.navigation.ElementScanningTask$1.run(ElementScanningTask.java:149)
is being called by "lower" module:
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask {code}
Parsing API doesn't really hold a "lock", but it only runs in a single
dedicated thread (which is a shared, spare resource too). Can we avoid that?
Too hard, right [~tomas_zezula] & [~zezulato...@gmail.com] & [~tzezula]? This
is a core of the indexing infrastructure. We don't want to touch it. Who else
to blame?
Let's make a rule: Whoever registers an indexer, isn't allowed to make a call
to modules "above" Parsing API.
With such rule, it is clear that {{KOHtmlExtension}} breaks it by calling into
Project UI API . Take a look at [four deadlock
conditions|http://wiki.apidesign.org/wiki/Deadlock_conditions] and select one
to break the deadlock the simplest way. This would do it:
{code:java}
---
a/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
+++
b/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
@@ -27,6 +27,8 @@
import java.util.Map;
import java.util.WeakHashMap;
import java.util.concurrent.ExecutionException;
+import java.util.concurrent.TimeUnit;
+import java.util.concurrent.TimeoutException;
import java.util.logging.Logger;
import org.netbeans.api.project.Project;
import org.netbeans.api.project.ui.OpenProjects;
@@ -57,8 +59,8 @@
if (!areProjectsOpen) {
try {
// just be sure that the projects are open
-OpenProjects.getDefault().openProjects().get();
-} catch (InterruptedException | ExecutionException ex) {
+OpenProjects.getDefault().openProjects().get(10,
TimeUnit.SECONDS);
+} catch (InterruptedException | ExecutionException |
TimeoutException ex) {
Exceptions.printStackTrace(ex);
} finally {
areProjectsOpen = true; {code}
e.g. don't wait indefinitely. However given [Roman Svitanič's
comment|https://github.com/emilianbold/netbeans-releases/commit/30092308c4fef#diff-b6844ad6d2c225bbb1c8d6c0287d6a6cR80]
"just be sure that the projects are open" - I'd suggest to delete the whole
{{areProjectsOpen}} check. This shouldn't be here at all. If the dependency of
{{javascript2.knockout}} module on Project UI API can be removed, then even
better!
This would be my recommended fix of the deadlock, unless it is known to cause
troubles somewhere (in unit tests?):
{code:java}
webcommon/javascript2.knockout$ git diff .
diff --git a/webcommon/javascript2.knockout/nbproject/project.xml
b/webcommon/javascript2.knockout/nbproject/project.xml
index 3f6fae4f8de0..47a191a3496d 100644
--- a/webcommon/javascript2.knockout/nbproject/project.xml
+++ b/webcommon/javascript2.knockout/nbproject/project.xml
@@ -96,15 +96,6 @@
1.61
-
-
org.netbeans.modules.projectuiapi.base
-
-
-
-1
-1.78
-
-
org.openide.filesystems
diff --git
a/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
b/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
index eec45ef5b673..42676c1e14d4 100644
---
a/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.
[jira] [Commented] (NETBEANS-4696) NetBeans 12.1-beta1 sometimes hangs on open
[
https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189010#comment-17189010
]
Jaroslav Tulach commented on NETBEANS-4696:
---
The general rule to fight with deadlocks in an API is [never hold a lock when
calling foreign code|http://wiki.apidesign.org/wiki/Deadlock]. However in this
case it is not that easy to find out who's an API and who's the client. What
can help is to topologically sort and layer the modules according to their
runtime dependencies - the ones below are an API, the ones above are clients.
Then a callback from below to above which holds a lock would be problematic.
Such a callback is happening in the deadlock:
{code:java}
org.netbeans.modules.html.knockout.KOHtmlExtension.isCustomTag(KOHtmlExtension.java:302)
is being called by "lower" module:
org.netbeans.modules.html.editor.gsf.HtmlGSFParser$1.isCustomTag(HtmlGSFParser.java:109)
is being called by "lower" module:
org.netbeans.modules.html.editor.lib.api.SyntaxAnalyzerResult.doParseHtml(SyntaxAnalyzerResult.java:259)
is being called by "lower" module:
org.netbeans.modules.csl.navigation.ElementScanningTask$1.run(ElementScanningTask.java:149)
is being called by "lower" module:
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask {code}
Parsing API doesn't really hold a "lock", but it only runs in a single
dedicated thread (which is a shared, spare resource too). Can we avoid that?
Too hard, right [~tomas_zezula] & [~zezulato...@gmail.com] & [~tzezula]? This
is a core of the indexing infrastructure. We don't want to touch it. Who else
to blame?
Let's make a rule: Whoever registers an indexer, isn't allowed to make a call
to modules "above" Parsing API.
With such rule, it is clear that {{KOHtmlExtension}} breaks it by calling into
Project UI API . Take a look at [four deadlock
conditions|http://wiki.apidesign.org/wiki/Deadlock_conditions] and select one
to break the deadlock the simplest way. This would do it:
{code:java}
---
a/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
+++
b/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
@@ -27,6 +27,8 @@
import java.util.Map;
import java.util.WeakHashMap;
import java.util.concurrent.ExecutionException;
+import java.util.concurrent.TimeUnit;
+import java.util.concurrent.TimeoutException;
import java.util.logging.Logger;
import org.netbeans.api.project.Project;
import org.netbeans.api.project.ui.OpenProjects;
@@ -57,8 +59,8 @@
if (!areProjectsOpen) {
try {
// just be sure that the projects are open
-OpenProjects.getDefault().openProjects().get();
-} catch (InterruptedException | ExecutionException ex) {
+OpenProjects.getDefault().openProjects().get(10,
TimeUnit.SECONDS);
+} catch (InterruptedException | ExecutionException |
TimeoutException ex) {
Exceptions.printStackTrace(ex);
} finally {
areProjectsOpen = true; {code}
e.g. don't wait indefinitely. However given [Roman Svitanič's
comment|https://github.com/emilianbold/netbeans-releases/commit/30092308c4fef#diff-b6844ad6d2c225bbb1c8d6c0287d6a6cR80]
"just be sure that the projects are open" - I'd suggest to delete the whole
{{areProjectsOpen}} check. This shouldn't be here at all. If the dependency of
{{javascript2.knockout}} module on Project UI API can be removed, then even
better!
> NetBeans 12.1-beta1 sometimes hangs on open
> ---
>
> Key: NETBEANS-4696
> URL: https://issues.apache.org/jira/browse/NETBEANS-4696
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance
>Affects Versions: 12.1
> Environment: Linux (Debian "Buster")
> OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)
>Reporter: Glenn Holmer
>Priority: Major
> Attachments: 12.1-vc1-thread-dump-orac.txt,
> nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt,
> netbeans-12.1-thread-dump.txt
>
>
>
> NetBeans sometimes hangs on startup; the symptom is a stalled "Opening
> Projects" progress bar. I haven't been able to find a repro case, but I'm
> attaching a thread dump (from VisualVM) and screen shot.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4746) Running test in Maven is slower than in Ant
Jaroslav Tulach created NETBEANS-4746:
-
Summary: Running test in Maven is slower than in Ant
Key: NETBEANS-4746
URL: https://issues.apache.org/jira/browse/NETBEANS-4746
Project: NetBeans
Issue Type: Task
Components: projects - Maven
Affects Versions: 12.0
Reporter: Jaroslav Tulach
Assignee: Jaroslav Tulach
Attachments: justtest.diff
NetBeans users has just recently complained that Maven support is slower than
Ant - some even claimed they [rather maintain dual Ant script
support|http://mail-archives.apache.org/mod_mbox//netbeans-dev/202008.mbox/browser]
than wait for Maven to launch. I've created this issue to investigate the
problem.
First of all we need a sample project: [^justtest.diff] - apply it {{patch -p1
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Reopened] (NETBEANS-3101) Can't launch (and connect) NetBeans from node
[
https://issues.apache.org/jira/browse/NETBEANS-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach reopened NETBEANS-3101:
---
Assignee: Jaroslav Tulach
At the end the fix may be needed for the [VSCode
extension|https://github.com/apache/netbeans/tree/master/java/java.lsp.server/vscode]
running on GraalVM/JDK8. It is [launching NetBeans from
code|https://github.com/apache/netbeans/commit/fa22d9c0508e6b8a15a2dfb07ee8c4b7ef6c1a99#diff-7eb3c296ad0e55de616ce54ff7993a4aL63].
It cannot use the {{[ignore, ignore, ignore]}} trick as the LSP client needs
stdio to talk to the server.
As such I [integrated the here in proposed
patch|https://github.com/apache/netbeans/commit/005d869d0d47afac38dbfca6c244a2054e98a9a9]
into the {{java-lsp-server-debugging-attempt2}} branch. Now the GraalVM/JDK8
support is working.
> Can't launch (and connect) NetBeans from node
> -
>
> Key: NETBEANS-3101
> URL: https://issues.apache.org/jira/browse/NETBEANS-3101
> Project: NetBeans
> Issue Type: Bug
> Components: platform - Launchers&CLI
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Minor
>
>
> I am trying to connect to a *NetBeans* based application from _Visual Studio_
> - aka _Electron_ - aka *node*. Somehow the *node* mangles network setup and
> the InetAddress.getHostAddress() isn't the same. To reproduce create
> following structure of files:
> {code:java}
> $ ls -l | cut -c50-
> dump.hprof
> nb.js
> nb.sh
> netbeans -> /home/devel/bin/netbeans/bin/netbeans
> $ cat nb.sh
> ./netbeans 'dump.hprof'
> $ cat nb.js
> var exec = require("child_process").execFile;
> let path = './netbeans';let vvm = exec(path, [ 'dump.hprof' ]){code}
> Then start *./netbeans* on background and wait for the GUI to launch. Then do
> following from command line:
> {code:java}
> ./jvm.sh
> {code}
> The dump.hprof file opens in the the GUI. Close it and try the same via
> *node.js*:
> {code:java}
> node ./jvm.js
> {code}
> The heap dump isn't shown (on my computer), rather a warning dialog appears.
> Result of node and shell script disagreeing on what is local host address.
> One is using IPv6 and one IPv4.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4699) Make it easy to create dynamically updated ProxyLookup
[ https://issues.apache.org/jira/browse/NETBEANS-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-4699: -- Fix Version/s: (was: 12.2) 12.1 > Make it easy to create dynamically updated ProxyLookup > -- > > Key: NETBEANS-4699 > URL: https://issues.apache.org/jira/browse/NETBEANS-4699 > Project: NetBeans > Issue Type: Improvement > Components: platform - Lookup >Affects Versions: 12.0 >Reporter: Jaroslav Tulach >Assignee: Tim Boudreau >Priority: Major > Fix For: 12.1 > > > One of the most common uses of ProxyLookup is to dynamically change the set > of lookups being delegated to. The objection to exposing the > setLookups() method is straightforward it would be inviting > clients of such a Lookup to call it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-4699) Make it easy to create dynamically updated ProxyLookup
Jaroslav Tulach created NETBEANS-4699: - Summary: Make it easy to create dynamically updated ProxyLookup Key: NETBEANS-4699 URL: https://issues.apache.org/jira/browse/NETBEANS-4699 Project: NetBeans Issue Type: Improvement Components: platform - Lookup Affects Versions: 12.0 Reporter: Jaroslav Tulach Assignee: Tim Boudreau Fix For: 12.2 One of the most common uses of ProxyLookup is to dynamically change the set of lookups being delegated to. The objection to exposing the setLookups() method is straightforward it would be inviting clients of such a Lookup to call it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-3910) FlatLaF doesn't work for HTML components
[ https://issues.apache.org/jira/browse/NETBEANS-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach resolved NETBEANS-3910. --- Fix Version/s: 12.1 Resolution: Fixed The most critical problem mitigated with https://github.com/apache/netbeans/commit/ab3823033a3978f834b7c72de57ac46d49fefb31 > FlatLaF doesn't work for HTML components > > > Key: NETBEANS-3910 > URL: https://issues.apache.org/jira/browse/NETBEANS-3910 > Project: NetBeans > Issue Type: Bug > Components: ide - UI >Reporter: Jaroslav Tulach >Assignee: Karl Tauber >Priority: Major > Fix For: 12.1 > > > While testing NetBeans 11.3 I have found out that dark FlatLaF isn't working > for HTML components. To reproduce: > * start NetBeans, select Dark FlatLaF and restart > * choose New Project/Java with Maven/Java Frontend Application > * go through the wizard to "Choose Platforms Page" > you'll see that the color of the font and background doesn't match the > surrounding L&F colors. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-4618) HeapFactory cannot process multi heap segment files
[
https://issues.apache.org/jira/browse/NETBEANS-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163193#comment-17163193
]
Jaroslav Tulach commented on NETBEANS-4618:
---
The root cause of the exception is the {{TagBounds[] tagBounds = new
TagBounds[0xff];}} array which assumes that each segment appears there only
one. When multiple heap dump segments (id {{0x1C}}) are present, the
{{tagBound.start}} is set to beginning of the first segment, but the
{{tagBound.end}} is set to the end of the last segment. The {{readDumpTag}}
code then tries to process everything from start to end and gets confused by
other, non-heap data in between. In the particular case of
[^multiheapsegment.hprof] a definition of {{STACK_FRAME}} is treated as
{{ROOT_NATIVE_STACK}} and then an exception is thrown.
> HeapFactory cannot process multi heap segment files
> ---
>
> Key: NETBEANS-4618
> URL: https://issues.apache.org/jira/browse/NETBEANS-4618
> Project: NetBeans
> Issue Type: Bug
> Components: profiler - Base
>Affects Versions: 12.0, 12.0.1
>Reporter: Jaroslav Tulach
>Priority: Major
> Attachments: multiheapsegment.hprof, singleheapsegment.hprof
>
>
> I am trying to generate {{.hprof}} file according to the [Java Profile
> 1.0.2|http://hg.openjdk.java.net/jdk6/jdk6/jdk/raw-file/tip/src/share/demo/jvmti/hprof/manual.html#mozTocId848088]
> specification. I believe I am fully following the specification (which
> allows multiple heap segments), but NetBeans Profiler library chokes up on my
> file and yields following exception:
> {code:java}
> java.lang.IllegalArgumentException: Invalid dump tag 0 at position 1415
> at
> org.netbeans.lib.profiler.heap.HprofHeap.readDumpTag(HprofHeap.java:1138)
> at
> org.netbeans.lib.profiler.heap.HprofHeap.fillHeapTagBounds(HprofHeap.java:1215)
> at org.netbeans.lib.profiler.heap.HprofHeap.(HprofHeap.java:140)
> at
> org.netbeans.lib.profiler.heap.HeapFactory.createHeap(HeapFactory.java:80)
> at
> org.netbeans.lib.profiler.heap.HeapFactory.createHeap(HeapFactory.java:49)
> {code}
> I am able to generate the file with a single heap segment (see
> [^singleheapsegment.hprof]) as well as multiple heap segments (see
> [^multiheapsegment.hprof]). The first one can be opened by NetBeans 12.x, the
> latter cannot.
>
> In my usecase I'd like to generate the file incrementally while my
> application is running. As such it is essential to flush the heap segments
> multiple times, otherwise I may run out of memory. It would be fantastic if
> the NetBeans heap profiler library could be enhanced to work with
> multiheapsegment files properly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4618) HeapFactory cannot process multi heap segment files
Jaroslav Tulach created NETBEANS-4618:
-
Summary: HeapFactory cannot process multi heap segment files
Key: NETBEANS-4618
URL: https://issues.apache.org/jira/browse/NETBEANS-4618
Project: NetBeans
Issue Type: Bug
Components: profiler - Base
Affects Versions: 12.0, 12.0.1
Reporter: Jaroslav Tulach
Attachments: multiheapsegment.hprof, singleheapsegment.hprof
I am trying to generate {{.hprof}} file according to the [Java Profile
1.0.2|http://hg.openjdk.java.net/jdk6/jdk6/jdk/raw-file/tip/src/share/demo/jvmti/hprof/manual.html#mozTocId848088]
specification. I believe I am fully following the specification (which allows
multiple heap segments), but NetBeans Profiler library chokes up on my file and
yields following exception:
{code:java}
java.lang.IllegalArgumentException: Invalid dump tag 0 at position 1415
at
org.netbeans.lib.profiler.heap.HprofHeap.readDumpTag(HprofHeap.java:1138)
at
org.netbeans.lib.profiler.heap.HprofHeap.fillHeapTagBounds(HprofHeap.java:1215)
at org.netbeans.lib.profiler.heap.HprofHeap.(HprofHeap.java:140)
at
org.netbeans.lib.profiler.heap.HeapFactory.createHeap(HeapFactory.java:80)
at
org.netbeans.lib.profiler.heap.HeapFactory.createHeap(HeapFactory.java:49)
{code}
I am able to generate the file with a single heap segment (see
[^singleheapsegment.hprof]) as well as multiple heap segments (see
[^multiheapsegment.hprof]). The first one can be opened by NetBeans 12.x, the
latter cannot.
In my usecase I'd like to generate the file incrementally while my application
is running. As such it is essential to flush the heap segments multiple times,
otherwise I may run out of memory. It would be fantastic if the NetBeans heap
profiler library could be enhanced to work with multiheapsegment files properly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] (NETBEANSINFRA-12) NetBeans Platform Cluster pom.xml RELEASE120 has broken dependencies!
[
https://issues.apache.org/jira/browse/NETBEANSINFRA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149593#comment-17149593
]
Jaroslav Tulach commented on NETBEANSINFRA-12:
--
I see. I can confirm, that
{code:xml}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
org.apidesign.test
VerifyHtmlUI
1.0-SNAPSHOT
nbm-application
UTF-8
8
8
org.netbeans.cluster
platform
RELEASE120-1
pom
org.apache.netbeans.utilities
nbm-maven-plugin
4.3
true
test
{code}
e.g. using {{RELEASE120-1}} artifacts builds without problems. Thank you.
> NetBeans Platform Cluster pom.xml RELEASE120 has broken dependencies!
> -
>
> Key: NETBEANSINFRA-12
> URL: https://issues.apache.org/jira/browse/NETBEANSINFRA-12
> Project: Apache NetBeans Infra
> Issue Type: Bug
> Components: MU - Apache NetBeans nb repository plugin
>Reporter: Jaroslav Tulach
>Assignee: Eric Barboni
>Priority: Blocker
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> While working on https://github.com/apache/netbeans/pull/1738 I realized that
> the Maven name given to org.netbeans.external:net.java.html:1.7 is wrong and
> it needlessly complicates the integration with rest of the utilities that
> rely on upstream org.netbeans.html:net.java.html:1.7 name.
> There is a code that tries to {{findExternal}} in Maven Utilities module:
> https://github.com/apache/netbeans-mavenutils-nb-repository-plugin/blob/master/src/main/java/org/apache/netbeans/nbm/repository/PopulateRepositoryMojo.java#L426
> However it is not yet implemented. Anyway, many of our OSGi bundles come from
> Maven central and they should be referenced with their real Maven
> co-ordinates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] (NETBEANSINFRA-12) NetBeans Platform Cluster pom.xml RELEASE120 has broken dependencies!
[
https://issues.apache.org/jira/browse/NETBEANSINFRA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANSINFRA-12:
-
Summary: NetBeans Platform Cluster pom.xml RELEASE120 has broken
dependencies! (was: NetBeans Platform Cluster pom.xml has broken dependencies!)
> NetBeans Platform Cluster pom.xml RELEASE120 has broken dependencies!
> -
>
> Key: NETBEANSINFRA-12
> URL: https://issues.apache.org/jira/browse/NETBEANSINFRA-12
> Project: Apache NetBeans Infra
> Issue Type: Bug
> Components: MU - Apache NetBeans nb repository plugin
>Reporter: Jaroslav Tulach
>Assignee: Eric Barboni
>Priority: Blocker
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> While working on https://github.com/apache/netbeans/pull/1738 I realized that
> the Maven name given to org.netbeans.external:net.java.html:1.7 is wrong and
> it needlessly complicates the integration with rest of the utilities that
> rely on upstream org.netbeans.html:net.java.html:1.7 name.
> There is a code that tries to {{findExternal}} in Maven Utilities module:
> https://github.com/apache/netbeans-mavenutils-nb-repository-plugin/blob/master/src/main/java/org/apache/netbeans/nbm/repository/PopulateRepositoryMojo.java#L426
> However it is not yet implemented. Anyway, many of our OSGi bundles come from
> Maven central and they should be referenced with their real Maven
> co-ordinates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] (NETBEANSINFRA-12) NetBeans Platform Cluster pom.xml has broken dependencies!
[
https://issues.apache.org/jira/browse/NETBEANSINFRA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149522#comment-17149522
]
Jaroslav Tulach commented on NETBEANSINFRA-12:
--
I've just tried to use the 12.0 Maven artifacts and it doesn't work. Try
following pom:
{code:xml}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
org.apidesign.test
VerifyHtmlUI
1.0-SNAPSHOT
nbm-application
UTF-8
8
8
org.netbeans.cluster
platform
RELEASE120
pom
org.apache.netbeans.utilities
nbm-maven-plugin
4.3
true
test
{code}
e.g. to build an empty project with just
{{org.netbeans.cluster:platform:RELEASE12}} - it doesn't work:
{code}
Failed to execute goal on project VerifyHtmlUI: Could not resolve dependencies
for project org.apidesign.test:VerifyHtmlUI:nbm-application:1.0-SNAPSHOT: The
following artifacts could not be resolved: org.ow2.asm:asm-7.2:jar:7.2,
org.ow2.asm:asm-commons-7.2:jar:7.2, org.ow2.asm:asm-tree-7.2:jar:7.2,
org.netbeans.html:net-java-html-boot-fx:jar:1.7,
org.netbeans.html:net-java-html-boot-script:jar:1.7,
org.netbeans.html:net-java-html-boot:jar:1.7,
org.netbeans.html:net-java-html-geo:jar:1.7,
org.netbeans.html:net-java-html-json:jar:1.7,
org.netbeans.html:net-java-html-sound:jar:1.7,
org.netbeans.html:net-java-html:jar:1.7,
commons-io:org-apache-commons-io:jar:2.6,
org.netbeans.html:org-netbeans-html-ko4j:jar:1.7,
org.netbeans.html:org-netbeans-html-xhr4j:jar:1.7: Failure to find
org.ow2.asm:asm-7.2:jar:7.2 in https://repo.maven.apache.org/maven2 was cached
in the local repository, resolution will not be reattempted until the update
interval of central has elapsed or updates are forced -> [Help 1]
{code}
Can we please start to treat this seriously and fix it before 12.0-u1 Maven
artifacts are out?
> NetBeans Platform Cluster pom.xml has broken dependencies!
> --
>
> Key: NETBEANSINFRA-12
> URL: https://issues.apache.org/jira/browse/NETBEANSINFRA-12
> Project: Apache NetBeans Infra
> Issue Type: Bug
> Components: MU - Apache NetBeans nb repository plugin
>Reporter: Jaroslav Tulach
>Assignee: Eric Barboni
>Priority: Blocker
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> While working on https://github.com/apache/netbeans/pull/1738 I realized that
> the Maven name given to org.netbeans.external:net.java.html:1.7 is wrong and
> it needlessly complicates the integration with rest of the utilities that
> rely on upstream org.netbeans.html:net.java.html:1.7 name.
> There is a code that tries to {{findExternal}} in Maven Utilities module:
> https://github.com/apache/netbeans-mavenutils-nb-repository-plugin/blob/master/src/main/java/org/apache/netbeans/nbm/repository/PopulateRepositoryMojo.java#L426
> However it is not yet implemented. Anyway, many of our OSGi bundles come from
> Maven central and they should be referenced with their real Maven
> co-ordinates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] (NETBEANSINFRA-12) org.netbeans.external:net.java.html & co. have wrong groupId/artifactId
[
https://issues.apache.org/jira/browse/NETBEANSINFRA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANSINFRA-12:
-
Fix Version/s: (was: NB Repository Plugin 1.6)
> org.netbeans.external:net.java.html & co. have wrong groupId/artifactId
> ---
>
> Key: NETBEANSINFRA-12
> URL: https://issues.apache.org/jira/browse/NETBEANSINFRA-12
> Project: Apache NetBeans Infra
> Issue Type: Bug
> Components: MU - Apache NetBeans nb repository plugin
>Reporter: Jaroslav Tulach
>Assignee: Eric Barboni
>Priority: Blocker
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> While working on https://github.com/apache/netbeans/pull/1738 I realized that
> the Maven name given to org.netbeans.external:net.java.html:1.7 is wrong and
> it needlessly complicates the integration with rest of the utilities that
> rely on upstream org.netbeans.html:net.java.html:1.7 name.
> There is a code that tries to {{findExternal}} in Maven Utilities module:
> https://github.com/apache/netbeans-mavenutils-nb-repository-plugin/blob/master/src/main/java/org/apache/netbeans/nbm/repository/PopulateRepositoryMojo.java#L426
> However it is not yet implemented. Anyway, many of our OSGi bundles come from
> Maven central and they should be referenced with their real Maven
> co-ordinates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] (NETBEANSINFRA-12) NetBeans Platform Cluster pom.xml has broken dependencies!
[
https://issues.apache.org/jira/browse/NETBEANSINFRA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANSINFRA-12:
-
Summary: NetBeans Platform Cluster pom.xml has broken dependencies! (was:
org.netbeans.external:net.java.html & co. have wrong groupId/artifactId)
> NetBeans Platform Cluster pom.xml has broken dependencies!
> --
>
> Key: NETBEANSINFRA-12
> URL: https://issues.apache.org/jira/browse/NETBEANSINFRA-12
> Project: Apache NetBeans Infra
> Issue Type: Bug
> Components: MU - Apache NetBeans nb repository plugin
>Reporter: Jaroslav Tulach
>Assignee: Eric Barboni
>Priority: Blocker
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> While working on https://github.com/apache/netbeans/pull/1738 I realized that
> the Maven name given to org.netbeans.external:net.java.html:1.7 is wrong and
> it needlessly complicates the integration with rest of the utilities that
> rely on upstream org.netbeans.html:net.java.html:1.7 name.
> There is a code that tries to {{findExternal}} in Maven Utilities module:
> https://github.com/apache/netbeans-mavenutils-nb-repository-plugin/blob/master/src/main/java/org/apache/netbeans/nbm/repository/PopulateRepositoryMojo.java#L426
> However it is not yet implemented. Anyway, many of our OSGi bundles come from
> Maven central and they should be referenced with their real Maven
> co-ordinates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] (NETBEANSINFRA-12) org.netbeans.external:net.java.html & co. have wrong groupId/artifactId
[
https://issues.apache.org/jira/browse/NETBEANSINFRA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANSINFRA-12:
-
Priority: Blocker (was: Minor)
> org.netbeans.external:net.java.html & co. have wrong groupId/artifactId
> ---
>
> Key: NETBEANSINFRA-12
> URL: https://issues.apache.org/jira/browse/NETBEANSINFRA-12
> Project: Apache NetBeans Infra
> Issue Type: Bug
> Components: MU - Apache NetBeans nb repository plugin
>Reporter: Jaroslav Tulach
>Assignee: Eric Barboni
>Priority: Blocker
> Labels: pull-request-available
> Fix For: NB Repository Plugin 1.6
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> While working on https://github.com/apache/netbeans/pull/1738 I realized that
> the Maven name given to org.netbeans.external:net.java.html:1.7 is wrong and
> it needlessly complicates the integration with rest of the utilities that
> rely on upstream org.netbeans.html:net.java.html:1.7 name.
> There is a code that tries to {{findExternal}} in Maven Utilities module:
> https://github.com/apache/netbeans-mavenutils-nb-repository-plugin/blob/master/src/main/java/org/apache/netbeans/nbm/repository/PopulateRepositoryMojo.java#L426
> However it is not yet implemented. Anyway, many of our OSGi bundles come from
> Maven central and they should be referenced with their real Maven
> co-ordinates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4222) Open up more of APIs in Node and PropertySheet
[
https://issues.apache.org/jira/browse/NETBEANS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach resolved NETBEANS-4222.
---
Fix Version/s: 12.0
Resolution: Won't Fix
I guess I scared the reporter enough... Sorry for that, I hope you will not
give up on NetBeans, Markus.
> Open up more of APIs in Node and PropertySheet
> --
>
> Key: NETBEANS-4222
> URL: https://issues.apache.org/jira/browse/NETBEANS-4222
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Explorer, platform - Nodes
>Reporter: Markus Sunela
>Assignee: Jaroslav Tulach
>Priority: Minor
> Fix For: 12.0
>
>
> Currently it is hard to customize Node, Explorer and PropertySheet behavior,
> because there are too many private instead of protected methods, package
> private and final classes in the API.
> Some examples I have stumbled on include
> * private doSetNodes method in PropertySheet (no way to override the use of
> ProxyNodes)
> * final and package private ProxyNode class
> * package private constructor in ProxyNode
> * package private getOriginalNodes method in ProxyNode
> * package private and final {color:#00}ProxyProperty{color} class in
> ProxyNode
> * final Sheet class and its inner class Sheet.Set
> * most private methods in Sheet and Sheet.Set should be protected instead
> * PropertySupport.Reflection class should have getters for read and write
> methods
> I wonder, what is the rationale for so strict and static API design? I would
> assume the performance gains from these limitations are meager. Opening these
> classes for sub-classing and modifications would result in much more flexible
> system with much less code duplication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4222) Open up more of APIs in Node and PropertySheet
[
https://issues.apache.org/jira/browse/NETBEANS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach reassigned NETBEANS-4222:
-
Assignee: Jaroslav Tulach
> Open up more of APIs in Node and PropertySheet
> --
>
> Key: NETBEANS-4222
> URL: https://issues.apache.org/jira/browse/NETBEANS-4222
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Explorer, platform - Nodes
>Reporter: Markus Sunela
>Assignee: Jaroslav Tulach
>Priority: Minor
>
> Currently it is hard to customize Node, Explorer and PropertySheet behavior,
> because there are too many private instead of protected methods, package
> private and final classes in the API.
> Some examples I have stumbled on include
> * private doSetNodes method in PropertySheet (no way to override the use of
> ProxyNodes)
> * final and package private ProxyNode class
> * package private constructor in ProxyNode
> * package private getOriginalNodes method in ProxyNode
> * package private and final {color:#00}ProxyProperty{color} class in
> ProxyNode
> * final Sheet class and its inner class Sheet.Set
> * most private methods in Sheet and Sheet.Set should be protected instead
> * PropertySupport.Reflection class should have getters for read and write
> methods
> I wonder, what is the rationale for so strict and static API design? I would
> assume the performance gains from these limitations are meager. Opening these
> classes for sub-classing and modifications would result in much more flexible
> system with much less code duplication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4222) Open up more of APIs in Node and PropertySheet
[
https://issues.apache.org/jira/browse/NETBEANS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093050#comment-17093050
]
Jaroslav Tulach commented on NETBEANS-4222:
---
Thanks for providing the use-case. First and foremost there is
[PropertySheet|https://bits.netbeans.org/dev/javadoc/org-openide-explorer/org/openide/explorer/propertysheet/PropertySheet.html]{{.setNodes}}
method. Why can't you use that one? Obtain your nodes, do as much filtering as
you want, create suitable {{ownRepresentingNode}} node and
{{sheet.setNodes(ownRepresentingNode)}}. It's going to render what you provide
and the performance will be completely under your control.
Second, if you really want to reuse the code from {{ProxyNode}} (what's the
biggest motivation?) then: Would it be enough to add a single method to
{{PropertySheetView.setFinalNodeFilter(Function
proxyNodeToCleanupNode)}} to do additional post processing?
Re. your comments about "rigidity, severely limits & co.":
[PropertySheet|https://bits.netbeans.org/dev/javadoc/org-openide-explorer/org/openide/explorer/propertysheet/PropertySheet.html]
API is an excellent example where making everything public leads. Look at the
list of deprecated methods in there! Once upon a time there was a guy who
thought exposing everything is a good idea. Then there was a guy who needed to
change the implementation to look completely different, but do the same (e.g.
display & edit properties of nodes). However the previous implementation was
leaking out. As a result of that there is more deprecated methods than not
deprecated ones.
It is not very likely someone is going to reimplement {{PropertySheet}}
internals again, but I am not willing to repeat similar mistake. It is
perfectly valid to request the "API to be more flexible", but that shall not be
achieving by making implementation public. API shall be designed, not created
ad-hoc by making parts of implementation public!
Last, but not least: You complain about poor performance of {{ProxyNode}} - do
you have an analysis? Wouldn't it be possible to improve it without changing
the API at all?
> Open up more of APIs in Node and PropertySheet
> --
>
> Key: NETBEANS-4222
> URL: https://issues.apache.org/jira/browse/NETBEANS-4222
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Explorer, platform - Nodes
>Reporter: Markus Sunela
>Priority: Minor
>
> Currently it is hard to customize Node, Explorer and PropertySheet behavior,
> because there are too many private instead of protected methods, package
> private and final classes in the API.
> Some examples I have stumbled on include
> * private doSetNodes method in PropertySheet (no way to override the use of
> ProxyNodes)
> * final and package private ProxyNode class
> * package private constructor in ProxyNode
> * package private getOriginalNodes method in ProxyNode
> * package private and final {color:#00}ProxyProperty{color} class in
> ProxyNode
> * final Sheet class and its inner class Sheet.Set
> * most private methods in Sheet and Sheet.Set should be protected instead
> * PropertySupport.Reflection class should have getters for read and write
> methods
> I wonder, what is the rationale for so strict and static API design? I would
> assume the performance gains from these limitations are meager. Opening these
> classes for sub-classing and modifications would result in much more flexible
> system with much less code duplication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4222) Open up more of APIs in Node and PropertySheet
[
https://issues.apache.org/jira/browse/NETBEANS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091530#comment-17091530
]
Jaroslav Tulach commented on NETBEANS-4222:
---
I tried to summarize the rationale in my [Practical API
Design|http://practical.apidesign.org/] book. There is even a story where a
colleague of mine wanted to make {{Node.getChildren()}} method overridable in
subclasses and why it is still {{final}}. In short: there has to be a balance
between freedom of API users and freedom of API maintainers. Btw. there is a
[freedom chapter in the 20 API Paradoxes e-book|http://buy.apidesign.org/].
Chapter 16 of the [Practical API Design|http://practical.apidesign.org/] book
contains a section _"Accepting API Patches"_. Reading it I can say that your
proposal removes our freedom because:
* Your patch restricts future evolution
* You have provided completely underdocumented patch
** the classes/methods you make public aren't document
** but worse: the overall use-case isn't explained
* You want to make API changes without any test coverage
* You API changes aren't versioned
I am not convinced it is enough justified to give up the NetBeans API evolution
freedom by accepting your changes at current state.
> Open up more of APIs in Node and PropertySheet
> --
>
> Key: NETBEANS-4222
> URL: https://issues.apache.org/jira/browse/NETBEANS-4222
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Explorer, platform - Nodes
>Reporter: Markus Sunela
>Priority: Minor
>
> Currently it is hard to customize Node, Explorer and PropertySheet behavior,
> because there are too many private instead of protected methods, package
> private and final classes in the API.
> Some examples I have stumbled on include
> * private doSetNodes method in PropertySheet (no way to override the use of
> ProxyNodes)
> * final and package private ProxyNode class
> * package private constructor in ProxyNode
> * package private getOriginalNodes method in ProxyNode
> * package private and final {color:#00}ProxyProperty{color} class in
> ProxyNode
> * final Sheet class and its inner class Sheet.Set
> * most private methods in Sheet and Sheet.Set should be protected instead
> * PropertySupport.Reflection class should have getters for read and write
> methods
> I wonder, what is the rationale for so strict and static API design? I would
> assume the performance gains from these limitations are meager. Opening these
> classes for sub-classing and modifications would result in much more flexible
> system with much less code duplication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4078) Can't create new Java project without installing nb-javac while running JDK 11
[ https://issues.apache.org/jira/browse/NETBEANS-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075703#comment-17075703 ] Jaroslav Tulach commented on NETBEANS-4078: --- The fix in [PR-2062|https://github.com/apache/netbeans/pull/2062] seems to do the trick. Test, integrate and resolve at your will. > Can't create new Java project without installing nb-javac while running JDK 11 > -- > > Key: NETBEANS-4078 > URL: https://issues.apache.org/jira/browse/NETBEANS-4078 > Project: NetBeans > Issue Type: Bug >Reporter: John McDonnell >Assignee: Anton Epple >Priority: Major > Labels: pull-request-available > Attachments: Screenshot 2020-03-29 at 07.38.33.png, Screenshot > 2020-03-29 at 07.48.32.png > > Time Spent: 10m > Remaining Estimate: 0h > > *Steps to reproduce* > 1. With JDK 11 (probably really JDK 8+), run Apache NetBeans 12 beta-2 > 2. Attempt to create a new Java/Maven project > 3. On the Finding Feature page, do not select the option "The nb-javac Java > editing support library" > !Screenshot 2020-03-29 at 07.38.33.png|width=544,height=386! > 4. Click Download and Activate > !Screenshot 2020-03-29 at 07.48.32.png|width=571,height=513! > Since I'm running JDK 11 I would expect that nb-javac isn't mandatory, and as > its not checked it shouldn't be included in the list of plugins to install > > *Environment* > *Product Version:* Apache NetBeans IDE 12.0-beta2 > *Java:* 11.0.5; OpenJDK 64-Bit Server VM 11.0.5+10-LTS > *Runtime:* OpenJDK Runtime Environment 11.0.5+10-LTS > *System:* Mac OS X version 10.15.3 running on x86_64; UTF-8; en_GB (nb) > *User directory:* /Users/john/Library/Application Support/NetBeans/12.0-beta2 > *Cache directory:* /Users/john/Library/Caches/NetBeans/12.0-beta2 -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-4110) Find usages doesn't find method references in libraries
Jaroslav Tulach created NETBEANS-4110:
-
Summary: Find usages doesn't find method references in libraries
Key: NETBEANS-4110
URL: https://issues.apache.org/jira/browse/NETBEANS-4110
Project: NetBeans
Issue Type: Bug
Components: editor - Parsing & Indexing
Reporter: Jaroslav Tulach
Assignee: Jan Lahoda
I have problems using "Find Usages" on method references in binaries. Imagine
you have a library with class:
{code:java}
class X {
X() {
}
} {code}
which also references its constructor as {{X:new}} somewhere. If I try to find
all usages of the constructor, the {{X::new}} isn't found.
The problem is only when working on {{.class}} file, when working on sources,
the reference is found without problems.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4078) Can't create new Java project without installing nb-javac while running JDK 11
[
https://issues.apache.org/jira/browse/NETBEANS-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073984#comment-17073984
]
Jaroslav Tulach edited comment on NETBEANS-4078 at 4/3/20, 5:10 AM:
Toni has added these checkboxes. The fix is going to be somewhere along these
lines, but I haven't had enough time to find the correct solution:
{code:java}
netbeans$ git diff
diff --git a/ergonomics/ide.ergonomics/java.properties
b/ergonomics/ide.ergonomics/java.properties
index c7c7252c4096..d4041e4dd0ff 100644
--- a/ergonomics/ide.ergonomics/java.properties
+++ b/ergonomics/ide.ergonomics/java.properties
@@ -20,7 +20,7 @@
project.file.../java.base/share/classes/java/lang/Object.java=org.netbeans.modul
projectImporter=Eclipse
mainModule=org.netbeans.modules.java.kit
-extra.modules=org.netbeans.modules.nbjavac
+extra.modules=org.netbeans.modules.nbjavac.*
extra.modules.recommended.min.jdk=9
extra.modules.1=org\\.netbeans\\.libs\\.javafx\\.(linux|win|macosx)
extra.modules.1.recommended.max.jdk=11
diff --git
a/ergonomics/ide.ergonomics/src/org/netbeans/modules/ide/ergonomics/fod/ConfigurationPanel.java
b/ergonomics/ide.ergonomics/src/org/netbeans/modules/ide/ergonomics/fod/ConfigurationPanel.java
index be78b576f36a..d10ff6e38a1b 100644
---
a/ergonomics/ide.ergonomics/src/org/netbeans/modules/ide/ergonomics/fod/ConfigurationPanel.java
+++
b/ergonomics/ide.ergonomics/src/org/netbeans/modules/ide/ergonomics/fod/ConfigurationPanel.java
@@ -27,6 +27,7 @@ import java.io.IOException;
import java.util.Collection;
import java.util.Collections;
import java.util.HashSet;
+import java.util.Iterator;
import java.util.Map;
import java.util.Set;
import java.util.concurrent.Callable;
@@ -353,11 +354,25 @@ public class ConfigurationPanel extends JPanel implements
Runnable {
}//GEN-LAST:event_activateButtonActionPerformed
private void downloadButtonActionPerformed(ActionEvent evt)
{//GEN-FIRST:event_downloadButtonActionPerformed
-OperationContainer op =
OperationContainer.createForInstall();
-op.add(featureInstall);
-if (PluginManager.openInstallWizard(op)) {
-activateButtonActionPerformed(null);
+Set install = new HashSet<>(featureInstall);
+Iterator it = install.iterator();
+KEEP: while (it.hasNext()) {
+UpdateElement ue = it.next();
+for (FeatureInfo.ExtraModuleInfo f : extrasFilter) {
+if (f.matches(ue.getCodeName())) {
+continue KEEP;
+}
+}
+it.remove();
+}
+if (!install.isEmpty()) {
+OperationContainer op =
OperationContainer.createForInstall();
+op.add(install);
+if (!PluginManager.openInstallWizard(op)) {
+return;
+}
}
+activateButtonActionPerformed(null);
}//GEN-LAST:event_downloadButtonActionPerformed
// Variables declaration - do not modify//GEN-BEGIN:variables
{code}
was (Author: jtulach):
Toni was adding these checkboxes. The fix is going to be somewhere along these
lines, but I haven't had enough time to find it:
{code:java}
netbeans$ git diff
diff --git a/ergonomics/ide.ergonomics/java.properties
b/ergonomics/ide.ergonomics/java.properties
index c7c7252c4096..d4041e4dd0ff 100644
--- a/ergonomics/ide.ergonomics/java.properties
+++ b/ergonomics/ide.ergonomics/java.properties
@@ -20,7 +20,7 @@
project.file.../java.base/share/classes/java/lang/Object.java=org.netbeans.modul
projectImporter=Eclipse
mainModule=org.netbeans.modules.java.kit
-extra.modules=org.netbeans.modules.nbjavac
+extra.modules=org.netbeans.modules.nbjavac.*
extra.modules.recommended.min.jdk=9
extra.modules.1=org\\.netbeans\\.libs\\.javafx\\.(linux|win|macosx)
extra.modules.1.recommended.max.jdk=11
diff --git
a/ergonomics/ide.ergonomics/src/org/netbeans/modules/ide/ergonomics/fod/ConfigurationPanel.java
b/ergonomics/ide.ergonomics/src/org/netbeans/modules/ide/ergonomics/fod/ConfigurationPanel.java
index be78b576f36a..d10ff6e38a1b 100644
---
a/ergonomics/ide.ergonomics/src/org/netbeans/modules/ide/ergonomics/fod/ConfigurationPanel.java
+++
b/ergonomics/ide.ergonomics/src/org/netbeans/modules/ide/ergonomics/fod/ConfigurationPanel.java
@@ -27,6 +27,7 @@ import java.io.IOException;
import java.util.Collection;
import java.util.Collections;
import java.util.HashSet;
+import java.util.Iterator;
import java.util.Map;
import java.util.Set;
import java.util.concurrent.Callable;
@@ -353,11 +354,25 @@ public class ConfigurationPanel extends JPanel implements
Runnable {
}//GEN-LAST:event_activateButtonActionPerformed
private void downloadButtonActionPerformed(ActionEvent evt)
{//GEN-FIRST:event_downloadButtonActionPerformed
-OperationContainer op =
OperationContainer.createForInstall();
-op.add
