[jira] [Updated] (NETBEANS-6201) Duplicate jars for each module depending on the same library

2021-11-12 Thread matteodg (Jira)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg updated NETBEANS-6201:
---
Description: 
Attached example of a very simple suite (issuesuite) with two modules (modulea 
and moduleb): both depend on Apache commons-lang library and in the cluster 
folder produced by nbm:cluster from the suite this is the folder structure:
 * issuesuite
 ** target
 *** netbeans_clusters
  issuesuite
 * modules
 ** ext
 *** org.example.modulea
  commons-lang
 * *commons-lang.jar <<<*
 *** org.example.moduleb
  commons-lang
 * *commons-lang.jar <<<*

It ended up packaging twice the *commons-lang.jar* library.
I have many external library dependencies, if this is the behavior, I will end 
up with a LOT of redundant files...

How to fix this? Or is it the intended behavior?
Thanks!

  was:
Attached example of a very simple suite (issuesuite) with two modules (modulea 
and moduleb): both depend on Apache commons-lang library and in the cluster 
folder produced by nbm:cluster from the suite this is the folder structure:
 * issuesuite
 ** target
 *** netbeans_clusters
  issuesuite
 * modules
 ** ext
 *** org.example.modulea
  commons-lang
 * *commons-lang.jar <<<*
 *** org.example.moduleb
  commons-lang
 * *commons-lang.jar <<<*

It ended up packaging twice the *commons-lang.jar* library.
I have many external libraries dependencies, if this is the behavior, I will 
end up with a LOT of redundant files...

How to fix this? Or is it the intended behavior?
Thanks!


> Duplicate jars for each module depending on the same library
> 
>
> Key: NETBEANS-6201
> URL: https://issues.apache.org/jira/browse/NETBEANS-6201
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 11.3, 12.3, 12.5
>Reporter: matteodg
>Priority: Major
> Attachments: issuesuite.zip
>
>
> Attached example of a very simple suite (issuesuite) with two modules 
> (modulea and moduleb): both depend on Apache commons-lang library and in the 
> cluster folder produced by nbm:cluster from the suite this is the folder 
> structure:
>  * issuesuite
>  ** target
>  *** netbeans_clusters
>   issuesuite
>  * modules
>  ** ext
>  *** org.example.modulea
>   commons-lang
>  * *commons-lang.jar <<<*
>  *** org.example.moduleb
>   commons-lang
>  * *commons-lang.jar <<<*
> It ended up packaging twice the *commons-lang.jar* library.
> I have many external library dependencies, if this is the behavior, I will 
> end up with a LOT of redundant files...
> How to fix this? Or is it the intended behavior?
> Thanks!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
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-6201) Duplicate jars for each module depending on the same library

2021-11-12 Thread matteodg (Jira)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg updated NETBEANS-6201:
---
Description: 
Attached example of a very simple suite (issuesuite) with two modules (modulea 
and moduleb): both depend on Apache commons-lang library and in the cluster 
folder produced by nbm:cluster from the suite this is the folder structure:
 * issuesuite
 ** target
 *** netbeans_clusters
  issuesuite
 * modules
 ** ext
 *** org.example.modulea
  commons-lang
 * *commons-lang.jar <<<*
 *** org.example.moduleb
  commons-lang
 * *commons-lang.jar <<<*

It ended up packaging twice the *commons-lang.jar* library.
I have many external libraries dependencies, if this is the behavior, I will 
end up with a LOT of redundant files...

How to fix this? Or is it the intended behavior?
Thanks!

  was:
Attached example of a very simple suite (issuesuite) with two modules (modulea 
and moduleb): both depend on Apache commons-lang library and in the cluster 
folder produced by nbm:cluster from the suite this is the folder structure:

issuesuite
- target
  - netbeans_clusters
- issuesuite
  - modules
 - ext
- org.example.modulea
   - commons-lang
  - commons-lang.jar  <<<
- org.example.moduleb
   - commons-lang
  - commons-lang.jar <<<

It ended up packaging twice the commons-lang.jar library.
I have many external libraries dependencies, if this is the behavior, I will 
end up with a LOT of redundant files...

How to fix this? Or is it the intended behavior?
Thanks!






> Duplicate jars for each module depending on the same library
> 
>
> Key: NETBEANS-6201
> URL: https://issues.apache.org/jira/browse/NETBEANS-6201
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 11.3, 12.3, 12.5
>Reporter: matteodg
>Priority: Major
> Attachments: issuesuite.zip
>
>
> Attached example of a very simple suite (issuesuite) with two modules 
> (modulea and moduleb): both depend on Apache commons-lang library and in the 
> cluster folder produced by nbm:cluster from the suite this is the folder 
> structure:
>  * issuesuite
>  ** target
>  *** netbeans_clusters
>   issuesuite
>  * modules
>  ** ext
>  *** org.example.modulea
>   commons-lang
>  * *commons-lang.jar <<<*
>  *** org.example.moduleb
>   commons-lang
>  * *commons-lang.jar <<<*
> It ended up packaging twice the *commons-lang.jar* library.
> I have many external libraries dependencies, if this is the behavior, I will 
> end up with a LOT of redundant files...
> How to fix this? Or is it the intended behavior?
> Thanks!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
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-6201) Duplicate jars for each module depending on the same library

2021-11-12 Thread matteodg (Jira)
matteodg created NETBEANS-6201:
--

 Summary: Duplicate jars for each module depending on the same 
library
 Key: NETBEANS-6201
 URL: https://issues.apache.org/jira/browse/NETBEANS-6201
 Project: NetBeans
  Issue Type: Bug
  Components: apisupport - Maven
Affects Versions: 12.5, 12.3, 11.3
Reporter: matteodg
 Attachments: issuesuite.zip

Attached example of a very simple suite (issuesuite) with two modules (modulea 
and moduleb): both depend on Apache commons-lang library and in the cluster 
folder produced by nbm:cluster from the suite this is the folder structure:

issuesuite
- target
  - netbeans_clusters
- issuesuite
  - modules
 - ext
- org.example.modulea
   - commons-lang
  - commons-lang.jar  <<<
- org.example.moduleb
   - commons-lang
  - commons-lang.jar <<<

It ended up packaging twice the commons-lang.jar library.
I have many external libraries dependencies, if this is the behavior, I will 
end up with a LOT of redundant files...

How to fix this? Or is it the intended behavior?
Thanks!







--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
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-5417) Add MIMEResolver annotation to register a mime-type based on regex

2021-03-05 Thread matteodg (Jira)
matteodg created NETBEANS-5417:
--

 Summary: Add MIMEResolver annotation to register a mime-type based 
on regex
 Key: NETBEANS-5417
 URL: https://issues.apache.org/jira/browse/NETBEANS-5417
 Project: NetBeans
  Issue Type: Improvement
  Components: platform - Filesystems
Affects Versions: 12.4
Reporter: matteodg


Adding {{MIMEResolver.PatternRegistration}} annotation to help users register a 
mime-type using regex and flags for {{java.util.regex.Pattern}} to match the 
filename.
Integrating using the same existing approach (see 
{{MIMEResolver.ExtensionRegistration}}) and related classes.



--
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-4128) Code completion slow - taken profiler snapshot

2020-04-19 Thread matteodg (Jira)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg updated NETBEANS-4128:
---
Attachment: codecompletion-very-slow3.npss
codecompletion-very-slow2.npss

> Code completion slow - taken profiler snapshot
> --
>
> Key: NETBEANS-4128
> URL: https://issues.apache.org/jira/browse/NETBEANS-4128
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.3
>Reporter: matteodg
>Priority: Major
> Fix For: 12.0
>
> Attachments: codecompletion-very-slow.npss, 
> codecompletion-very-slow2.npss, codecompletion-very-slow3.npss
>
>
> We have a pretty big NetBeans Platform Application (~180 modules and 5 
> suites) and when pressing CTRL+SPACE for code completion it is very slow.
> It seems the calls boil down to the filesystem calling Files.listFiles() a 
> lot.
> I'm running on the branch release113 compiled locally with both the patches 
> from [~jtulach] and [~jlahoda] for NETBEANS-4037 (not sure whether that's 
> important, but just wanted to be clear).



--
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-4037) Debugger slow - taken profiler snapshots

2020-04-19 Thread matteodg (Jira)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg updated NETBEANS-4037:
---
Attachment: 4037-only-jtulach-patch.npss

> Debugger slow - taken profiler snapshots
> 
>
> Key: NETBEANS-4037
> URL: https://issues.apache.org/jira/browse/NETBEANS-4037
> Project: NetBeans
>  Issue Type: Bug
>  Components: debugger - Java
>Affects Versions: 8.2, 11.1, 11.2, 11.3
>Reporter: matteodg
>Assignee: Jan Lahoda
>Priority: Major
>  Labels: performance, pull-request-available
> Fix For: 12.0
>
> Attachments: 4037-only-jtulach-patch.npss, 
> org.netbeans.modules.debugger.jpda.ui.SourcePath.annotate.npss, 
> org.netbeans.modules.debugger.jpda.ui.SourcePath.getURL.npss
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We have a pretty big NetBeans Platform Application (~180 modules and 5 
> suites) and when the debugger reaches the first breakpoint it got stuck: the 
> tabs Debugging, Variables, Breakpoints, etc. are all with a "Please wait..." 
> node and with the NetBeans sampler I took a few snapshots highlighting it is 
> spending a lot of time on calls like:
>  * {{org.netbeans.modules.debugger.jpda.ui.SourcePath.getURL()}}
>  * {{org.netbeans.modules.debugger.jpda.ui.SourcePath.annotate()}}
> which at the end boil down to a lot of calls like:
>  * java.util.concurrent.CopyOnWriteArrayList.remove()
>  * java.io.File.isFile()
> Attached the snapshots.
> Then if I press Continue the debugger remain stuck: now Pause and Continue 
> buttons in the toolbar are disabled...
> I kept close and restarting NetBeans but no luck... I remember got this 
> behavior even with NB 8.2, sometimes though it goes through and I'm able to 
> debug, but very rarely!
>  



--
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-4037) Debugger slow - taken profiler snapshots

2020-04-19 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087053#comment-17087053
 ] 

matteodg commented on NETBEANS-4037:


Hey I'm working with patched 11.3 and it really improved the performance when 
debugging!

One thing though I took a snapshot when using 11.3 patched with only [~jtulach] 
code because it seems not improving at full speed. See here 
[^4037-only-jtulach-patch.npss]

Thus I think [~jlahoda] patch is needed as well.

> Debugger slow - taken profiler snapshots
> 
>
> Key: NETBEANS-4037
> URL: https://issues.apache.org/jira/browse/NETBEANS-4037
> Project: NetBeans
>  Issue Type: Bug
>  Components: debugger - Java
>Affects Versions: 8.2, 11.1, 11.2, 11.3
>Reporter: matteodg
>Assignee: Jan Lahoda
>Priority: Major
>  Labels: performance, pull-request-available
> Fix For: 12.0
>
> Attachments: 4037-only-jtulach-patch.npss, 
> org.netbeans.modules.debugger.jpda.ui.SourcePath.annotate.npss, 
> org.netbeans.modules.debugger.jpda.ui.SourcePath.getURL.npss
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We have a pretty big NetBeans Platform Application (~180 modules and 5 
> suites) and when the debugger reaches the first breakpoint it got stuck: the 
> tabs Debugging, Variables, Breakpoints, etc. are all with a "Please wait..." 
> node and with the NetBeans sampler I took a few snapshots highlighting it is 
> spending a lot of time on calls like:
>  * {{org.netbeans.modules.debugger.jpda.ui.SourcePath.getURL()}}
>  * {{org.netbeans.modules.debugger.jpda.ui.SourcePath.annotate()}}
> which at the end boil down to a lot of calls like:
>  * java.util.concurrent.CopyOnWriteArrayList.remove()
>  * java.io.File.isFile()
> Attached the snapshots.
> Then if I press Continue the debugger remain stuck: now Pause and Continue 
> buttons in the toolbar are disabled...
> I kept close and restarting NetBeans but no luck... I remember got this 
> behavior even with NB 8.2, sometimes though it goes through and I'm able to 
> debug, but very rarely!
>  



--
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-4037) Debugger slow - taken profiler snapshots

2020-04-07 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077370#comment-17077370
 ] 

matteodg edited comment on NETBEANS-4037 at 4/7/20, 5:30 PM:
-

Thanks [~jtulach] and [~jlahoda]! I'm testing both patches based on release113 
branch (as it is the more stable) and it has improved) not found. Next I'm 
going to check separately them and get some snapshot if I have still some 
slowness.


was (Author: matte...@infinito.it):
Thanks [~jtulach] and [~jlahoda]!! I'm testing both patches based on release113 
branch (as it is the more stable) and it has improved! Next I'm going to check 
separately them and get some snapshot if I have still some slowness.

> Debugger slow - taken profiler snapshots
> 
>
> Key: NETBEANS-4037
> URL: https://issues.apache.org/jira/browse/NETBEANS-4037
> Project: NetBeans
>  Issue Type: Bug
>  Components: debugger - Java
>Affects Versions: 8.2, 11.1, 11.2, 11.3
>Reporter: matteodg
>Assignee: Jan Lahoda
>Priority: Major
>  Labels: performance
> Fix For: 12.0
>
> Attachments: 
> org.netbeans.modules.debugger.jpda.ui.SourcePath.annotate.npss, 
> org.netbeans.modules.debugger.jpda.ui.SourcePath.getURL.npss
>
>
> We have a pretty big NetBeans Platform Application (~180 modules and 5 
> suites) and when the debugger reaches the first breakpoint it got stuck: the 
> tabs Debugging, Variables, Breakpoints, etc. are all with a "Please wait..." 
> node and with the NetBeans sampler I took a few snapshots highlighting it is 
> spending a lot of time on calls like:
>  * {{org.netbeans.modules.debugger.jpda.ui.SourcePath.getURL()}}
>  * {{org.netbeans.modules.debugger.jpda.ui.SourcePath.annotate()}}
> which at the end boil down to a lot of calls like:
>  * java.util.concurrent.CopyOnWriteArrayList.remove()
>  * java.io.File.isFile()
> Attached the snapshots.
> Then if I press Continue the debugger remain stuck: now Pause and Continue 
> buttons in the toolbar are disabled...
> I kept close and restarting NetBeans but no luck... I remember got this 
> behavior even with NB 8.2, sometimes though it goes through and I'm able to 
> debug, but very rarely!
>  



--
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-4128) Code completion slow - taken profiler snapshot

2020-04-07 Thread matteodg (Jira)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg updated NETBEANS-4128:
---
Description: 
We have a pretty big NetBeans Platform Application (~180 modules and 5 suites) 
and when pressing CTRL+SPACE for code completion it is very slow.

It seems the calls boil down to the filesystem calling Files.listFiles() a lot.

I'm running on the branch release113 compiled locally with both the patches 
from [~jtulach] and [~jlahoda] for NETBEANS-4037 (not sure whether that's 
important, but just wanted to be clear).

  was:
We have a pretty big NetBeans Platform Application (~180 modules and 5 suites) 
and when pressing CTRL+SPACE for code completion it is very slow.

It seems the calls are going down to the filesystem calling Files.listFiles() a 
lot.

I'm running on the branch release113 compiled locally with both the patches 
from [~jtulach] and [~jlahoda] for NETBEANS-4037 (not sure whether that's 
important, but just wanted to be clear).


> Code completion slow - taken profiler snapshot
> --
>
> Key: NETBEANS-4128
> URL: https://issues.apache.org/jira/browse/NETBEANS-4128
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.3
>Reporter: matteodg
>Priority: Major
> Fix For: 12.0
>
> Attachments: codecompletion-very-slow.npss
>
>
> We have a pretty big NetBeans Platform Application (~180 modules and 5 
> suites) and when pressing CTRL+SPACE for code completion it is very slow.
> It seems the calls boil down to the filesystem calling Files.listFiles() a 
> lot.
> I'm running on the branch release113 compiled locally with both the patches 
> from [~jtulach] and [~jlahoda] for NETBEANS-4037 (not sure whether that's 
> important, but just wanted to be clear).



--
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-4128) Code completion slow - taken profiler snapshot

2020-04-07 Thread matteodg (Jira)
matteodg created NETBEANS-4128:
--

 Summary: Code completion slow - taken profiler snapshot
 Key: NETBEANS-4128
 URL: https://issues.apache.org/jira/browse/NETBEANS-4128
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 11.3
Reporter: matteodg
 Fix For: 12.0
 Attachments: codecompletion-very-slow.npss

We have a pretty big NetBeans Platform Application (~180 modules and 5 suites) 
and when pressing CTRL+SPACE for code completion it is very slow.

It seems the calls are going down to the filesystem calling Files.listFiles() a 
lot.

I'm running on the branch release113 compiled locally with both the patches 
from [~jtulach] and [~jlahoda] for NETBEANS-4037 (not sure whether that's 
important, but just wanted to be clear).



--
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-4037) Debugger slow - taken profiler snapshots

2020-04-07 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077370#comment-17077370
 ] 

matteodg commented on NETBEANS-4037:


Thanks [~jtulach] and [~jlahoda]!! I'm testing both patches based on release113 
branch (as it is the more stable) and it has improved! Next I'm going to check 
separately them and get some snapshot if I have still some slowness.

> Debugger slow - taken profiler snapshots
> 
>
> Key: NETBEANS-4037
> URL: https://issues.apache.org/jira/browse/NETBEANS-4037
> Project: NetBeans
>  Issue Type: Bug
>  Components: debugger - Java
>Affects Versions: 8.2, 11.1, 11.2, 11.3
>Reporter: matteodg
>Assignee: Jan Lahoda
>Priority: Major
>  Labels: performance
> Fix For: 12.0
>
> Attachments: 
> org.netbeans.modules.debugger.jpda.ui.SourcePath.annotate.npss, 
> org.netbeans.modules.debugger.jpda.ui.SourcePath.getURL.npss
>
>
> We have a pretty big NetBeans Platform Application (~180 modules and 5 
> suites) and when the debugger reaches the first breakpoint it got stuck: the 
> tabs Debugging, Variables, Breakpoints, etc. are all with a "Please wait..." 
> node and with the NetBeans sampler I took a few snapshots highlighting it is 
> spending a lot of time on calls like:
>  * {{org.netbeans.modules.debugger.jpda.ui.SourcePath.getURL()}}
>  * {{org.netbeans.modules.debugger.jpda.ui.SourcePath.annotate()}}
> which at the end boil down to a lot of calls like:
>  * java.util.concurrent.CopyOnWriteArrayList.remove()
>  * java.io.File.isFile()
> Attached the snapshots.
> Then if I press Continue the debugger remain stuck: now Pause and Continue 
> buttons in the toolbar are disabled...
> I kept close and restarting NetBeans but no luck... I remember got this 
> behavior even with NB 8.2, sometimes though it goes through and I'm able to 
> debug, but very rarely!
>  



--
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-4037) Debugger slow - taken profiler snapshots

2020-03-18 Thread matteodg (Jira)
matteodg created NETBEANS-4037:
--

 Summary: Debugger slow - taken profiler snapshots
 Key: NETBEANS-4037
 URL: https://issues.apache.org/jira/browse/NETBEANS-4037
 Project: NetBeans
  Issue Type: Bug
  Components: debugger - Java
Affects Versions: 11.2, 11.1, 8.2, 11.3
Reporter: matteodg
 Fix For: 12.0
 Attachments: 
org.netbeans.modules.debugger.jpda.ui.SourcePath.annotate.npss, 
org.netbeans.modules.debugger.jpda.ui.SourcePath.getURL.npss

We have a pretty big NetBeans Platform Application (~180 modules and 5 suites) 
and when the debugger reaches the first breakpoint it got stuck: the tabs 
Debugging, Variables, Breakpoints, etc. are all with a "Please wait..." node 
and with the NetBeans sampler I took a few snapshots highlighting it is 
spending a lot of time on calls like:
 * {{org.netbeans.modules.debugger.jpda.ui.SourcePath.getURL()}}
 * {{org.netbeans.modules.debugger.jpda.ui.SourcePath.annotate()}}

which at the end boil down to a lot of calls like:
 * java.util.concurrent.CopyOnWriteArrayList.remove()
 * java.io.File.isFile()

Attached the snapshots.

Then if I press Continue the debugger remain stuck: now Pause and Continue 
buttons in the toolbar are disabled...

I kept close and restarting NetBeans but no luck... I remember got this 
behavior even with NB 8.2, sometimes though it goes through and I'm able to 
debug, but very rarely!

 



--
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-3896) Profiling method calls does not work with JDK newer than 1.8

2020-02-26 Thread matteodg (Jira)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg closed NETBEANS-3896.
--
Resolution: Duplicate

> Profiling method calls does not work with JDK newer than 1.8
> 
>
> Key: NETBEANS-3896
> URL: https://issues.apache.org/jira/browse/NETBEANS-3896
> Project: NetBeans
>  Issue Type: Bug
>  Components: profiler - Base
>Affects Versions: 11.2, 11.3
>Reporter: matteodg
>Priority: Critical
> Fix For: 12.0
>
> Attachments: AdoptOpenJDK-11.0.6.10-hotspot-hs_err_pid9856.log, 
> AdoptOpenJDK-11.0.6.10-hotspot.txt, AdoptOpenJDK-11.0.6.10-openj9-0.18.1.txt, 
> AdoptOpenJDK-13.0.2.8-hotspot-hs_err_pid16960.log, 
> AdoptOpenJDK-13.0.2_8_hotspot.txt, AdoptOpenJDK-13.0.2_8_openj9-0.18.0.txt, 
> OpenJDK-11+28-hs_err_pid9260.log, OpenJDK-11+28.txt, 
> OpenJDK-13.0.2-hs_err_pid9892.log, OpenJDK-13.0.2.txt
>
>
> Profiling methods calls a Java application (and even a Netbeans Platform 
> Application) with a JDK newer than 1.8 does not work.
> I collected different results using:
>  * OpenJDK 11+28
>  * OpenJDK 13.0.2
>  * AdoptOpenJDK 11.0.6_10-hotspot
>  * AdoptOpenJDK 11.0.6_10-openJ9-0.18.1
>  * AdoptOpenJDK 13.0.2_8-hotspot
>  * AdoptOpenJDK 13.0.2_8-openJ9-0.18.0
> and all fail (different error between hotspot-based and openJ9-based). I'm 
> going to attach all outputs from those JDKs.
> I tested with NetBeans 11.2 and 11.3-beta3 as well.
> Profiling with object memory does work instead.
>  



--
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-3896) Profiling method calls does not work with JDK newer than 1.8

2020-02-26 Thread matteodg (Jira)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg updated NETBEANS-3896:
---
Priority: Critical  (was: Major)

> Profiling method calls does not work with JDK newer than 1.8
> 
>
> Key: NETBEANS-3896
> URL: https://issues.apache.org/jira/browse/NETBEANS-3896
> Project: NetBeans
>  Issue Type: Bug
>  Components: profiler - Base
>Affects Versions: 11.2, 11.3
>Reporter: matteodg
>Priority: Critical
> Fix For: 12.0
>
> Attachments: AdoptOpenJDK-11.0.6.10-hotspot-hs_err_pid9856.log, 
> AdoptOpenJDK-11.0.6.10-hotspot.txt, AdoptOpenJDK-11.0.6.10-openj9-0.18.1.txt, 
> AdoptOpenJDK-13.0.2.8-hotspot-hs_err_pid16960.log, 
> AdoptOpenJDK-13.0.2_8_hotspot.txt, AdoptOpenJDK-13.0.2_8_openj9-0.18.0.txt, 
> OpenJDK-11+28-hs_err_pid9260.log, OpenJDK-11+28.txt, 
> OpenJDK-13.0.2-hs_err_pid9892.log, OpenJDK-13.0.2.txt
>
>
> Profiling methods calls a Java application (and even a Netbeans Platform 
> Application) with a JDK newer than 1.8 does not work.
> I collected different results using:
>  * OpenJDK 11+28
>  * OpenJDK 13.0.2
>  * AdoptOpenJDK 11.0.6_10-hotspot
>  * AdoptOpenJDK 11.0.6_10-openJ9-0.18.1
>  * AdoptOpenJDK 13.0.2_8-hotspot
>  * AdoptOpenJDK 13.0.2_8-openJ9-0.18.0
> and all fail (different error between hotspot-based and openJ9-based). I'm 
> going to attach all outputs from those JDKs.
> I tested with NetBeans 11.2 and 11.3-beta3 as well.
> Profiling with object memory does work instead.
>  



--
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-3896) Profiling method calls does not work with JDK newer than 1.8

2020-02-26 Thread matteodg (Jira)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg updated NETBEANS-3896:
---
Fix Version/s: (was: 11.3)
   12.0

> Profiling method calls does not work with JDK newer than 1.8
> 
>
> Key: NETBEANS-3896
> URL: https://issues.apache.org/jira/browse/NETBEANS-3896
> Project: NetBeans
>  Issue Type: Bug
>  Components: profiler - Base
>Affects Versions: 11.2, 11.3
>Reporter: matteodg
>Priority: Major
> Fix For: 12.0
>
> Attachments: AdoptOpenJDK-11.0.6.10-hotspot-hs_err_pid9856.log, 
> AdoptOpenJDK-11.0.6.10-hotspot.txt, AdoptOpenJDK-11.0.6.10-openj9-0.18.1.txt, 
> AdoptOpenJDK-13.0.2.8-hotspot-hs_err_pid16960.log, 
> AdoptOpenJDK-13.0.2_8_hotspot.txt, AdoptOpenJDK-13.0.2_8_openj9-0.18.0.txt, 
> OpenJDK-11+28-hs_err_pid9260.log, OpenJDK-11+28.txt, 
> OpenJDK-13.0.2-hs_err_pid9892.log, OpenJDK-13.0.2.txt
>
>
> Profiling methods calls a Java application (and even a Netbeans Platform 
> Application) with a JDK newer than 1.8 does not work.
> I collected different results using:
>  * OpenJDK 11+28
>  * OpenJDK 13.0.2
>  * AdoptOpenJDK 11.0.6_10-hotspot
>  * AdoptOpenJDK 11.0.6_10-openJ9-0.18.1
>  * AdoptOpenJDK 13.0.2_8-hotspot
>  * AdoptOpenJDK 13.0.2_8-openJ9-0.18.0
> and all fail (different error between hotspot-based and openJ9-based). I'm 
> going to attach all outputs from those JDKs.
> I tested with NetBeans 11.2 and 11.3-beta3 as well.
> Profiling with object memory does work instead.
>  



--
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-3896) Profiling method calls does not work with JDK newer than 1.8

2020-02-18 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039455#comment-17039455
 ] 

matteodg edited comment on NETBEANS-3896 at 2/18/20 9:11 PM:
-

I got the hs_err_pid*.log files for hotspot VMs, but when I run with 
AdoptOpenJDK with OpenJ9, it does not create similar log files. 


was (Author: matte...@infinito.it):
I got the hs_err_pid*.log files for hotspot VMs, but when I run with 
AdoptOpenJDK with OpenJ9, it does not created similar log files. 

> Profiling method calls does not work with JDK newer than 1.8
> 
>
> Key: NETBEANS-3896
> URL: https://issues.apache.org/jira/browse/NETBEANS-3896
> Project: NetBeans
>  Issue Type: Bug
>  Components: profiler - Base
>Affects Versions: 11.2, 11.3
>Reporter: matteodg
>Priority: Major
> Fix For: 11.3
>
> Attachments: AdoptOpenJDK-11.0.6.10-hotspot-hs_err_pid9856.log, 
> AdoptOpenJDK-11.0.6.10-hotspot.txt, AdoptOpenJDK-11.0.6.10-openj9-0.18.1.txt, 
> AdoptOpenJDK-13.0.2.8-hotspot-hs_err_pid16960.log, 
> AdoptOpenJDK-13.0.2_8_hotspot.txt, AdoptOpenJDK-13.0.2_8_openj9-0.18.0.txt, 
> OpenJDK-11+28-hs_err_pid9260.log, OpenJDK-11+28.txt, 
> OpenJDK-13.0.2-hs_err_pid9892.log, OpenJDK-13.0.2.txt
>
>
> Profiling methods calls a Java application (and even a Netbeans Platform 
> Application) with a JDK newer than 1.8 does not work.
> I collected different results using:
>  * OpenJDK 11+28
>  * OpenJDK 13.0.2
>  * AdoptOpenJDK 11.0.6_10-hotspot
>  * AdoptOpenJDK 11.0.6_10-openJ9-0.18.1
>  * AdoptOpenJDK 13.0.2_8-hotspot
>  * AdoptOpenJDK 13.0.2_8-openJ9-0.18.0
> and all fail (different error between hotspot-based and openJ9-based). I'm 
> going to attach all outputs from those JDKs.
> I tested with NetBeans 11.2 and 11.3-beta3 as well.
> Profiling with object memory does work instead.
>  



--
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-3896) Profiling method calls does not work with JDK newer than 1.8

2020-02-18 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039455#comment-17039455
 ] 

matteodg commented on NETBEANS-3896:


I got the hs_err_pid*.log files for hotspot VM, but when I run with 
AdoptOpenJDK with OpenJ9, it does not created similar log files. 

> Profiling method calls does not work with JDK newer than 1.8
> 
>
> Key: NETBEANS-3896
> URL: https://issues.apache.org/jira/browse/NETBEANS-3896
> Project: NetBeans
>  Issue Type: Bug
>  Components: profiler - Base
>Affects Versions: 11.2, 11.3
>Reporter: matteodg
>Priority: Major
> Fix For: 11.3
>
> Attachments: AdoptOpenJDK-11.0.6.10-hotspot-hs_err_pid9856.log, 
> AdoptOpenJDK-11.0.6.10-hotspot.txt, AdoptOpenJDK-11.0.6.10-openj9-0.18.1.txt, 
> AdoptOpenJDK-13.0.2.8-hotspot-hs_err_pid16960.log, 
> AdoptOpenJDK-13.0.2_8_hotspot.txt, AdoptOpenJDK-13.0.2_8_openj9-0.18.0.txt, 
> OpenJDK-11+28-hs_err_pid9260.log, OpenJDK-11+28.txt, 
> OpenJDK-13.0.2-hs_err_pid9892.log, OpenJDK-13.0.2.txt
>
>
> Profiling methods calls a Java application (and even a Netbeans Platform 
> Application) with a JDK newer than 1.8 does not work.
> I collected different results using:
>  * OpenJDK 11+28
>  * OpenJDK 13.0.2
>  * AdoptOpenJDK 11.0.6_10-hotspot
>  * AdoptOpenJDK 11.0.6_10-openJ9-0.18.1
>  * AdoptOpenJDK 13.0.2_8-hotspot
>  * AdoptOpenJDK 13.0.2_8-openJ9-0.18.0
> and all fail (different error between hotspot-based and openJ9-based). I'm 
> going to attach all outputs from those JDKs.
> I tested with NetBeans 11.2 and 11.3-beta3 as well.
> Profiling with object memory does work instead.
>  



--
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-3896) Profiling method calls does not work with JDK newer than 1.8

2020-02-18 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039455#comment-17039455
 ] 

matteodg edited comment on NETBEANS-3896 at 2/18/20 9:02 PM:
-

I got the hs_err_pid*.log files for hotspot VMs, but when I run with 
AdoptOpenJDK with OpenJ9, it does not created similar log files. 


was (Author: matte...@infinito.it):
I got the hs_err_pid*.log files for hotspot VM, but when I run with 
AdoptOpenJDK with OpenJ9, it does not created similar log files. 

> Profiling method calls does not work with JDK newer than 1.8
> 
>
> Key: NETBEANS-3896
> URL: https://issues.apache.org/jira/browse/NETBEANS-3896
> Project: NetBeans
>  Issue Type: Bug
>  Components: profiler - Base
>Affects Versions: 11.2, 11.3
>Reporter: matteodg
>Priority: Major
> Fix For: 11.3
>
> Attachments: AdoptOpenJDK-11.0.6.10-hotspot-hs_err_pid9856.log, 
> AdoptOpenJDK-11.0.6.10-hotspot.txt, AdoptOpenJDK-11.0.6.10-openj9-0.18.1.txt, 
> AdoptOpenJDK-13.0.2.8-hotspot-hs_err_pid16960.log, 
> AdoptOpenJDK-13.0.2_8_hotspot.txt, AdoptOpenJDK-13.0.2_8_openj9-0.18.0.txt, 
> OpenJDK-11+28-hs_err_pid9260.log, OpenJDK-11+28.txt, 
> OpenJDK-13.0.2-hs_err_pid9892.log, OpenJDK-13.0.2.txt
>
>
> Profiling methods calls a Java application (and even a Netbeans Platform 
> Application) with a JDK newer than 1.8 does not work.
> I collected different results using:
>  * OpenJDK 11+28
>  * OpenJDK 13.0.2
>  * AdoptOpenJDK 11.0.6_10-hotspot
>  * AdoptOpenJDK 11.0.6_10-openJ9-0.18.1
>  * AdoptOpenJDK 13.0.2_8-hotspot
>  * AdoptOpenJDK 13.0.2_8-openJ9-0.18.0
> and all fail (different error between hotspot-based and openJ9-based). I'm 
> going to attach all outputs from those JDKs.
> I tested with NetBeans 11.2 and 11.3-beta3 as well.
> Profiling with object memory does work instead.
>  



--
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-3896) Profiling method calls does not work with JDK newer than 1.8

2020-02-18 Thread matteodg (Jira)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg updated NETBEANS-3896:
---
Attachment: OpenJDK-13.0.2-hs_err_pid9892.log
OpenJDK-11+28-hs_err_pid9260.log
AdoptOpenJDK-13.0.2.8-hotspot-hs_err_pid16960.log
AdoptOpenJDK-11.0.6.10-hotspot-hs_err_pid9856.log

> Profiling method calls does not work with JDK newer than 1.8
> 
>
> Key: NETBEANS-3896
> URL: https://issues.apache.org/jira/browse/NETBEANS-3896
> Project: NetBeans
>  Issue Type: Bug
>  Components: profiler - Base
>Affects Versions: 11.2, 11.3
>Reporter: matteodg
>Priority: Major
> Fix For: 11.3
>
> Attachments: AdoptOpenJDK-11.0.6.10-hotspot-hs_err_pid9856.log, 
> AdoptOpenJDK-11.0.6.10-hotspot.txt, AdoptOpenJDK-11.0.6.10-openj9-0.18.1.txt, 
> AdoptOpenJDK-13.0.2.8-hotspot-hs_err_pid16960.log, 
> AdoptOpenJDK-13.0.2_8_hotspot.txt, AdoptOpenJDK-13.0.2_8_openj9-0.18.0.txt, 
> OpenJDK-11+28-hs_err_pid9260.log, OpenJDK-11+28.txt, 
> OpenJDK-13.0.2-hs_err_pid9892.log, OpenJDK-13.0.2.txt
>
>
> Profiling methods calls a Java application (and even a Netbeans Platform 
> Application) with a JDK newer than 1.8 does not work.
> I collected different results using:
>  * OpenJDK 11+28
>  * OpenJDK 13.0.2
>  * AdoptOpenJDK 11.0.6_10-hotspot
>  * AdoptOpenJDK 11.0.6_10-openJ9-0.18.1
>  * AdoptOpenJDK 13.0.2_8-hotspot
>  * AdoptOpenJDK 13.0.2_8-openJ9-0.18.0
> and all fail (different error between hotspot-based and openJ9-based). I'm 
> going to attach all outputs from those JDKs.
> I tested with NetBeans 11.2 and 11.3-beta3 as well.
> Profiling with object memory does work instead.
>  



--
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-3896) Profiling method calls does not work with JDK newer than 1.8

2020-02-18 Thread matteodg (Jira)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg updated NETBEANS-3896:
---
Description: 
Profiling methods calls a Java application (and even a Netbeans Platform 
Application) with a JDK newer than 1.8 does not work.

I collected different results using:
 * OpenJDK 11+28
 * OpenJDK 13.0.2
 * AdoptOpenJDK 11.0.6_10-hotspot
 * AdoptOpenJDK 11.0.6_10-openJ9-0.18.1
 * AdoptOpenJDK 13.0.2_8-hotspot
 * AdoptOpenJDK 13.0.2_8-openJ9-0.18.0

and all fail (different error between hotspot-based and openJ9-based). I'm 
going to attach all outputs from those JDKs.

I tested with NetBeans 11.2 and 11.3-beta3 as well.

Profiling with object memory does work instead.

 

  was:
Profiling a Java application (and even a Netbeans Platform Application) with a 
JDK newer than 1.8 does not work.

I collected different results using:
 * OpenJDK 11+28
 * OpenJDK 13.0.2
 * AdoptOpenJDK 11.0.6_10-hotspot
 * AdoptOpenJDK 11.0.6_10-openJ9-0.18.1
 * AdoptOpenJDK 13.0.2_8-hotspot
 * AdoptOpenJDK 13.0.2_8-openJ9-0.18.0

and all fail (different error between hotspot-based and openJ9-based). I'm 
going to attach all outputs from those JDKs.

I tested with NetBeans 11.2 and 11.3-beta3 as well.

 

Summary: Profiling method calls does not work with JDK newer than 1.8  
(was: Profiler does not work with JDK11+)

> Profiling method calls does not work with JDK newer than 1.8
> 
>
> Key: NETBEANS-3896
> URL: https://issues.apache.org/jira/browse/NETBEANS-3896
> Project: NetBeans
>  Issue Type: Bug
>  Components: profiler - Base
>Affects Versions: 11.2, 11.3
>Reporter: matteodg
>Priority: Major
> Fix For: 11.3
>
> Attachments: AdoptOpenJDK-11.0.6.10-hotspot.txt, 
> AdoptOpenJDK-11.0.6.10-openj9-0.18.1.txt, AdoptOpenJDK-13.0.2_8_hotspot.txt, 
> AdoptOpenJDK-13.0.2_8_openj9-0.18.0.txt, OpenJDK-11+28.txt, OpenJDK-13.0.2.txt
>
>
> Profiling methods calls a Java application (and even a Netbeans Platform 
> Application) with a JDK newer than 1.8 does not work.
> I collected different results using:
>  * OpenJDK 11+28
>  * OpenJDK 13.0.2
>  * AdoptOpenJDK 11.0.6_10-hotspot
>  * AdoptOpenJDK 11.0.6_10-openJ9-0.18.1
>  * AdoptOpenJDK 13.0.2_8-hotspot
>  * AdoptOpenJDK 13.0.2_8-openJ9-0.18.0
> and all fail (different error between hotspot-based and openJ9-based). I'm 
> going to attach all outputs from those JDKs.
> I tested with NetBeans 11.2 and 11.3-beta3 as well.
> Profiling with object memory does work instead.
>  



--
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-3896) Profiler does not work with JDK11+

2020-02-18 Thread matteodg (Jira)
matteodg created NETBEANS-3896:
--

 Summary: Profiler does not work with JDK11+
 Key: NETBEANS-3896
 URL: https://issues.apache.org/jira/browse/NETBEANS-3896
 Project: NetBeans
  Issue Type: Bug
  Components: profiler - Base
Affects Versions: 11.2, 11.3
Reporter: matteodg
 Fix For: 11.3
 Attachments: AdoptOpenJDK-11.0.6.10-hotspot.txt, 
AdoptOpenJDK-11.0.6.10-openj9-0.18.1.txt, AdoptOpenJDK-13.0.2_8_hotspot.txt, 
AdoptOpenJDK-13.0.2_8_openj9-0.18.0.txt, OpenJDK-11+28.txt, OpenJDK-13.0.2.txt

Profiling a Java application (and even a Netbeans Platform Application) with a 
JDK newer than 1.8 does not work.

I collected different results using:
 * OpenJDK 11+28
 * OpenJDK 13.0.2
 * AdoptOpenJDK 11.0.6_10-hotspot
 * AdoptOpenJDK 11.0.6_10-openJ9-0.18.1
 * AdoptOpenJDK 13.0.2_8-hotspot
 * AdoptOpenJDK 13.0.2_8-openJ9-0.18.0

and all fail (different error between hotspot-based and openJ9-based). I'm 
going to attach all outputs from those JDKs.

I tested with NetBeans 11.2 and 11.3-beta3 as well.

 



--
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-3798) MultiViewCloneableEditor.canCloseElement() does not call the DataEditor.canClose()

2020-02-06 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031829#comment-17031829
 ] 

matteodg commented on NETBEANS-3798:


Actually the same behavior with .properties text editor and visual editor is in 
NB8.2 as well.

> MultiViewCloneableEditor.canCloseElement()  does not call the 
> DataEditor.canClose()
> ---
>
> Key: NETBEANS-3798
> URL: https://issues.apache.org/jira/browse/NETBEANS-3798
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Window System
>Affects Versions: 11.1, 11.2, 11.3
> Environment: Windows 10 and JDK 13
>Reporter: Enrico Scantamburlo
>Priority: Major
>
> We moved our RCP application from NetBeans 8.1 to NB 11.1 .
> We wanted to add the history tab to our files when they are open in the 
> editor. 
>  One of the problems we found is that the
> {{MultiViewCloneableEditor.canCloseElement()}}
> does not keep into account the
> {{DataEditor.canClose()}}
> method that was previously customized by us.



--
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-3798) MultiViewCloneableEditor.canCloseElement() does not call the DataEditor.canClose()

2020-02-06 Thread matteodg (Jira)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg updated NETBEANS-3798:
---
Affects Version/s: 8.2

> MultiViewCloneableEditor.canCloseElement()  does not call the 
> DataEditor.canClose()
> ---
>
> Key: NETBEANS-3798
> URL: https://issues.apache.org/jira/browse/NETBEANS-3798
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Window System
>Affects Versions: 8.2, 11.1, 11.2, 11.3
> Environment: Windows 10 and JDK 13
>Reporter: Enrico Scantamburlo
>Priority: Major
>
> We moved our RCP application from NetBeans 8.1 to NB 11.1 .
> We wanted to add the history tab to our files when they are open in the 
> editor. 
>  One of the problems we found is that the
> {{MultiViewCloneableEditor.canCloseElement()}}
> does not keep into account the
> {{DataEditor.canClose()}}
> method that was previously customized by us.



--
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-3798) MultiViewCloneableEditor.canCloseElement() does not call the DataEditor.canClose()

2020-02-06 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031688#comment-17031688
 ] 

matteodg commented on NETBEANS-3798:


It is also reproducible in NetBeans by opening a properties file using Open 
(opens a visual editor) and Edit (opens the text editor) actions.

> MultiViewCloneableEditor.canCloseElement()  does not call the 
> DataEditor.canClose()
> ---
>
> Key: NETBEANS-3798
> URL: https://issues.apache.org/jira/browse/NETBEANS-3798
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Window System
>Affects Versions: 11.1, 11.2, 11.3
> Environment: Windows 10 and JDK 13
>Reporter: Enrico Scantamburlo
>Priority: Major
>
> We moved our RCP application from NetBeans 8.1 to NB 11.1 .
> We wanted to add the history tab to our files when they are open in the 
> editor. 
>  One of the problems we found is that the
> {{MultiViewCloneableEditor.canCloseElement()}}
> does not keep into account the
> {{DataEditor.canClose()}}
> method that was previously customized by us.



--
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-3725) Not honoring containerDelegate in BeanInfo

2020-01-22 Thread matteodg (Jira)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg closed NETBEANS-3725.
--

> Not honoring containerDelegate in BeanInfo
> --
>
> Key: NETBEANS-3725
> URL: https://issues.apache.org/jira/browse/NETBEANS-3725
> Project: NetBeans
>  Issue Type: Bug
>  Components: guibuilder - Code
>Affects Versions: 11.1, 11.2
>Reporter: matteodg
>Assignee: matteodg
>Priority: Major
> Fix For: 11.3
>
> Attachments: ContainerDelegateExample.zip
>
>
> We are using a custom GUI bean (SectionPanel) whose containerDelegate has 
> been set in the SectionPanelBeanInfo not being the SectionPanel itself but an 
> inner panel:
> {code:java}
> BeanDescriptor beanDescriptor = new BeanDescriptor(SectionPanel.class , null);
> beanDescriptor.setValue("containerDelegate", "getInnerPanel");{code}
> In NB 8.2 that was honored by Matisse allowing to use SectionPanel as a 
> component container, but since NB 11.1+ that is not honored anymore... 
> Matisse does not pick up the containerDelegate, not allowing to use the 
> SectionPanel as a container anymore.
>  
> Attached an example that works with NB8.2: the Java code generated by Matisse 
> calls getInnerPanel() method allowing to put a JSlider inside the 
> SectionPanel in the MainFrame example, whereas in NB11.1 the Java code 
> generated by Matisse does not call that method anymore.



--
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-3725) Not honoring containerDelegate in BeanInfo

2020-01-22 Thread matteodg (Jira)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg resolved NETBEANS-3725.

  Assignee: matteodg
Resolution: Invalid

See last comment: I recreated the SectionPanelBeanInfo with new JDK I used in 
NB11.1+, and that fixed the problem.

> Not honoring containerDelegate in BeanInfo
> --
>
> Key: NETBEANS-3725
> URL: https://issues.apache.org/jira/browse/NETBEANS-3725
> Project: NetBeans
>  Issue Type: Bug
>  Components: guibuilder - Code
>Affects Versions: 11.1, 11.2
>Reporter: matteodg
>Assignee: matteodg
>Priority: Major
> Fix For: 11.3
>
> Attachments: ContainerDelegateExample.zip
>
>
> We are using a custom GUI bean (SectionPanel) whose containerDelegate has 
> been set in the SectionPanelBeanInfo not being the SectionPanel itself but an 
> inner panel:
> {code:java}
> BeanDescriptor beanDescriptor = new BeanDescriptor(SectionPanel.class , null);
> beanDescriptor.setValue("containerDelegate", "getInnerPanel");{code}
> In NB 8.2 that was honored by Matisse allowing to use SectionPanel as a 
> component container, but since NB 11.1+ that is not honored anymore... 
> Matisse does not pick up the containerDelegate, not allowing to use the 
> SectionPanel as a container anymore.
>  
> Attached an example that works with NB8.2: the Java code generated by Matisse 
> calls getInnerPanel() method allowing to put a JSlider inside the 
> SectionPanel in the MainFrame example, whereas in NB11.1 the Java code 
> generated by Matisse does not call that method anymore.



--
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-3725) Not honoring containerDelegate in BeanInfo

2020-01-22 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17021556#comment-17021556
 ] 

matteodg commented on NETBEANS-3725:


Actually I find out it was only matter to recreate the SectionPanelBeanInfo 
when running NetBeans with the new JDK (forgot to mention that that was another 
difference between NB8.2 vs NB11.1+). It seems the javax.swing.JPanel has 
different methods/fields in betweek JDK1.8 and OpenJDK13, and that cause the 
problem in Matisse not recognizing some of the methods/fields declared in the 
BeanInfo.

 

I'm closing this.

> Not honoring containerDelegate in BeanInfo
> --
>
> Key: NETBEANS-3725
> URL: https://issues.apache.org/jira/browse/NETBEANS-3725
> Project: NetBeans
>  Issue Type: Bug
>  Components: guibuilder - Code
>Affects Versions: 11.1, 11.2
>Reporter: matteodg
>Priority: Major
> Fix For: 11.3
>
> Attachments: ContainerDelegateExample.zip
>
>
> We are using a custom GUI bean (SectionPanel) whose containerDelegate has 
> been set in the SectionPanelBeanInfo not being the SectionPanel itself but an 
> inner panel:
> {code:java}
> BeanDescriptor beanDescriptor = new BeanDescriptor(SectionPanel.class , null);
> beanDescriptor.setValue("containerDelegate", "getInnerPanel");{code}
> In NB 8.2 that was honored by Matisse allowing to use SectionPanel as a 
> component container, but since NB 11.1+ that is not honored anymore... 
> Matisse does not pick up the containerDelegate, not allowing to use the 
> SectionPanel as a container anymore.
>  
> Attached an example that works with NB8.2: the Java code generated by Matisse 
> calls getInnerPanel() method allowing to put a JSlider inside the 
> SectionPanel in the MainFrame example, whereas in NB11.1 the Java code 
> generated by Matisse does not call that method anymore.



--
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-3725) Not honoring containerDelegate in BeanInfo

2020-01-21 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17020511#comment-17020511
 ] 

matteodg commented on NETBEANS-3725:


I looked for the class reading the "containerDelegate" and I found it in 

[https://github.com/apache/netbeans/blob/accdbada0a9c5105bd3f06e435024230c1618316/java/form/src/org/netbeans/modules/form/RADVisualContainer.java]

But there has not be any changes lately as far as I can tell that could have 
broken the functionality... Any hint?

> Not honoring containerDelegate in BeanInfo
> --
>
> Key: NETBEANS-3725
> URL: https://issues.apache.org/jira/browse/NETBEANS-3725
> Project: NetBeans
>  Issue Type: Bug
>  Components: guibuilder - Code
>Affects Versions: 11.1, 11.2
>Reporter: matteodg
>Priority: Major
> Fix For: 11.3
>
> Attachments: ContainerDelegateExample.zip
>
>
> We are using a custom GUI bean (SectionPanel) whose containerDelegate has 
> been set in the SectionPanelBeanInfo not being the SectionPanel itself but an 
> inner panel:
> {code:java}
> BeanDescriptor beanDescriptor = new BeanDescriptor(SectionPanel.class , null);
> beanDescriptor.setValue("containerDelegate", "getInnerPanel");{code}
> In NB 8.2 that was honored by Matisse allowing to use SectionPanel as a 
> component container, but since NB 11.1+ that is not honored anymore... 
> Matisse does not pick up the containerDelegate, not allowing to use the 
> SectionPanel as a container anymore.
>  
> Attached an example that works with NB8.2: the Java code generated by Matisse 
> calls getInnerPanel() method allowing to put a JSlider inside the 
> SectionPanel in the MainFrame example, whereas in NB11.1 the Java code 
> generated by Matisse does not call that method anymore.



--
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-3725) Not honoring containerDelegate in BeanInfo

2020-01-21 Thread matteodg (Jira)
matteodg created NETBEANS-3725:
--

 Summary: Not honoring containerDelegate in BeanInfo
 Key: NETBEANS-3725
 URL: https://issues.apache.org/jira/browse/NETBEANS-3725
 Project: NetBeans
  Issue Type: Bug
  Components: guibuilder - Code
Affects Versions: 11.2, 11.1
Reporter: matteodg
 Fix For: 11.3
 Attachments: ContainerDelegateExample.zip

We are using a custom GUI bean (SectionPanel) whose containerDelegate has been 
set in the SectionPanelBeanInfo not being the SectionPanel itself but an inner 
panel:
{code:java}
BeanDescriptor beanDescriptor = new BeanDescriptor(SectionPanel.class , null);
beanDescriptor.setValue("containerDelegate", "getInnerPanel");{code}
In NB 8.2 that was honored by Matisse allowing to use SectionPanel as a 
component container, but since NB 11.1+ that is not honored anymore... Matisse 
does not pick up the containerDelegate, not allowing to use the SectionPanel as 
a container anymore.

 

Attached an example that works with NB8.2: the Java code generated by Matisse 
calls getInnerPanel() method allowing to put a JSlider inside the SectionPanel 
in the MainFrame example, whereas in NB11.1 the Java code generated by Matisse 
does not call that method anymore.



--
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-3278) NetBeans Platform Application only compiles with default JDK

2019-10-24 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959060#comment-16959060
 ] 

matteodg commented on NETBEANS-3278:


Thanks for the AdoptOpenJDK 8 link!

We are switching from Java 1.8 to Java 13, so for the moment we are running NB 
11.1 with OpenJDK 13 to allow us to compile our RCP app with the same JDK.

> NetBeans Platform Application only compiles with default JDK
> 
>
> Key: NETBEANS-3278
> URL: https://issues.apache.org/jira/browse/NETBEANS-3278
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Harness
>Affects Versions: 11.0, 11.1, 11.2
> Environment: Windows 10
>Reporter: matteodg
>Priority: Major
>
> I created from scratch a simple NetBeans Platform Application with a single 
> module and I would like to use a Java Platform different than the default 
> one, but I can't because I got this error while building the application:
> {noformat}
> module.taskdefs:
> module.common-init:
> Warning: nbjdk.active=OpenJDK13 or nbjdk.home=D:\Java\OpenJDK\jdk-13.0.1 is 
> an invalid Java platform; ignoring and using D:\Java\OpenJDK
> module.projectized-common.basic-init:
> module.basic-init:
> {noformat}
> I'm launching NetBeans IDE with Oracle JDK 13 (default JDK) but I would like 
> to compile and run with OpenJDK 13 (which I properly configured in 
> Tools->Java Platforms).
> I checked and this bug is present in NB 11.0, 11.1 and 11.2-beta3 as well



--
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-3290) Cannot compile NB module with layer.xml

2019-10-24 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959055#comment-16959055
 ] 

matteodg commented on NETBEANS-3290:


I cannot reproduce in 11.1, it works fine there.

Also I already started a thread in dev mailing list (but with all latest issues 
I found: 
[https://lists.apache.org/thread.html/8d08ff9c44ff8baa9eac5cdb7a6d67f3a1cbbca788e68c7953e767e9@%3Cdev.netbeans.apache.org%3E])

> Cannot compile NB module with layer.xml
> ---
>
> Key: NETBEANS-3290
> URL: https://issues.apache.org/jira/browse/NETBEANS-3290
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Project
>Affects Versions: 11.2
>Reporter: matteodg
>Priority: Major
> Attachments: module1.zip
>
>
> I created a simple NetBeans module (see attachment) then I added layer.xml 
> and I got this error when compiling:
> {code:java}
> ant -f C:\\Users\\matteo\\Documents\\NetBeansProjects\\module1 
> -Dcontinue.after.failing.tests=true -Ddo.not.clean.module.config.xml=true 
> clean build
> ...
> verify-class-linkage:
> C:\Users\matteo\Documents\NetBeansProjects\module1\src\module1\layer.xml:3:14:
>  Element type "filesystem" must be declared.
> C:\Program Files\NetBeans 11.2-beta3\harness\common.xml:335: 
> C:\Users\matteo\Documents\NetBeansProjects\module1\src\module1\layer.xml is 
> not a valid XML document.
> BUILD FAILED (total time: 0 seconds){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-3289) Find Usages caused AssertionError while parsing a Java file

2019-10-24 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959057#comment-16959057
 ] 

matteodg commented on NETBEANS-3289:


OK, I uninstalled nb-javac and I got it working, thanks!

> Find Usages caused AssertionError while parsing a Java file
> ---
>
> Key: NETBEANS-3289
> URL: https://issues.apache.org/jira/browse/NETBEANS-3289
> Project: NetBeans
>  Issue Type: Bug
>  Components: editor - Parsing  Indexing
>Affects Versions: 11.2
>Reporter: matteodg
>Priority: Major
> Attachments: EclipseStreamlinesDataProvider.dump
>
>
> Trying to use Find Usages in NB 11.2beta3 and I got this error that stops the 
> whole list of usages
> This works fine in NB 11.1



--
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-3278) NetBeans Platform Application only compiles with default JDK

2019-10-24 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959049#comment-16959049
 ] 

matteodg commented on NETBEANS-3278:


I tried with Oracle, because I cannot find an OpenJDK 1.8 for Windows right now.

> NetBeans Platform Application only compiles with default JDK
> 
>
> Key: NETBEANS-3278
> URL: https://issues.apache.org/jira/browse/NETBEANS-3278
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Harness
>Affects Versions: 11.0, 11.1, 11.2
> Environment: Windows 10
>Reporter: matteodg
>Priority: Major
>
> I created from scratch a simple NetBeans Platform Application with a single 
> module and I would like to use a Java Platform different than the default 
> one, but I can't because I got this error while building the application:
> {noformat}
> module.taskdefs:
> module.common-init:
> Warning: nbjdk.active=OpenJDK13 or nbjdk.home=D:\Java\OpenJDK\jdk-13.0.1 is 
> an invalid Java platform; ignoring and using D:\Java\OpenJDK
> module.projectized-common.basic-init:
> module.basic-init:
> {noformat}
> I'm launching NetBeans IDE with Oracle JDK 13 (default JDK) but I would like 
> to compile and run with OpenJDK 13 (which I properly configured in 
> Tools->Java Platforms).
> I checked and this bug is present in NB 11.0, 11.1 and 11.2-beta3 as well



--
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-3278) NetBeans Platform Application only compiles with default JDK

2019-10-24 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959045#comment-16959045
 ] 

matteodg commented on NETBEANS-3278:


With Oracle JDK 1.8 this works: I guess it is because the new JDKs (since 9) 
are missing "lib/tools.jar" (that's what it seems from a shallow look at 
harness/jdk.xml).

> NetBeans Platform Application only compiles with default JDK
> 
>
> Key: NETBEANS-3278
> URL: https://issues.apache.org/jira/browse/NETBEANS-3278
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Harness
>Affects Versions: 11.0, 11.1, 11.2
> Environment: Windows 10
>Reporter: matteodg
>Priority: Major
>
> I created from scratch a simple NetBeans Platform Application with a single 
> module and I would like to use a Java Platform different than the default 
> one, but I can't because I got this error while building the application:
> {noformat}
> module.taskdefs:
> module.common-init:
> Warning: nbjdk.active=OpenJDK13 or nbjdk.home=D:\Java\OpenJDK\jdk-13.0.1 is 
> an invalid Java platform; ignoring and using D:\Java\OpenJDK
> module.projectized-common.basic-init:
> module.basic-init:
> {noformat}
> I'm launching NetBeans IDE with Oracle JDK 13 (default JDK) but I would like 
> to compile and run with OpenJDK 13 (which I properly configured in 
> Tools->Java Platforms).
> I checked and this bug is present in NB 11.0, 11.1 and 11.2-beta3 as well



--
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-3290) Cannot compile NB module with layer.xml

2019-10-24 Thread matteodg (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959033#comment-16959033
 ] 

matteodg commented on NETBEANS-3290:


That was just a small test case created to allow you to easily reproduce the 
problem.

The real problem is that we have hundreds of modules in our RCP app that still 
use layer.xml and it seems we cannot compile our app in 11.2-beta3 due to this 
problem.

> Cannot compile NB module with layer.xml
> ---
>
> Key: NETBEANS-3290
> URL: https://issues.apache.org/jira/browse/NETBEANS-3290
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Project
>Affects Versions: 11.2
>Reporter: matteodg
>Priority: Major
> Attachments: module1.zip
>
>
> I created a simple NetBeans module (see attachment) then I added layer.xml 
> and I got this error when compiling:
> {code:java}
> ant -f C:\\Users\\matteo\\Documents\\NetBeansProjects\\module1 
> -Dcontinue.after.failing.tests=true -Ddo.not.clean.module.config.xml=true 
> clean build
> ...
> verify-class-linkage:
> C:\Users\matteo\Documents\NetBeansProjects\module1\src\module1\layer.xml:3:14:
>  Element type "filesystem" must be declared.
> C:\Program Files\NetBeans 11.2-beta3\harness\common.xml:335: 
> C:\Users\matteo\Documents\NetBeansProjects\module1\src\module1\layer.xml is 
> not a valid XML document.
> BUILD FAILED (total time: 0 seconds){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] [Created] (NETBEANS-3290) Cannot compile NB module with layer.xml

2019-10-24 Thread matteodg (Jira)
matteodg created NETBEANS-3290:
--

 Summary: Cannot compile NB module with layer.xml
 Key: NETBEANS-3290
 URL: https://issues.apache.org/jira/browse/NETBEANS-3290
 Project: NetBeans
  Issue Type: Bug
  Components: apisupport - Project
Affects Versions: 11.2
Reporter: matteodg
 Attachments: module1.zip

I created a simple NetBeans module (see attachment) then I added layer.xml and 
I got this error when compiling:
{code:java}
ant -f C:\\Users\\matteo\\Documents\\NetBeansProjects\\module1 
-Dcontinue.after.failing.tests=true -Ddo.not.clean.module.config.xml=true clean 
build
...
verify-class-linkage:
C:\Users\matteo\Documents\NetBeansProjects\module1\src\module1\layer.xml:3:14: 
Element type "filesystem" must be declared.
C:\Program Files\NetBeans 11.2-beta3\harness\common.xml:335: 
C:\Users\matteo\Documents\NetBeansProjects\module1\src\module1\layer.xml is not 
a valid XML document.
BUILD FAILED (total time: 0 seconds){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] [Created] (NETBEANS-3289) Find Usages caused AssertionError while parsing a Java file

2019-10-24 Thread matteodg (Jira)
matteodg created NETBEANS-3289:
--

 Summary: Find Usages caused AssertionError while parsing a Java 
file
 Key: NETBEANS-3289
 URL: https://issues.apache.org/jira/browse/NETBEANS-3289
 Project: NetBeans
  Issue Type: Bug
  Components: editor - Parsing  Indexing
Affects Versions: 11.2
Reporter: matteodg
 Attachments: EclipseStreamlinesDataProvider.dump

Trying to use Find Usages in NB 11.2beta3 and I got this error that stops the 
whole list of usages

This works fine in NB 11.1



--
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-3278) NetBeans Platform Application only compiles with default JDK

2019-10-22 Thread matteodg (Jira)
matteodg created NETBEANS-3278:
--

 Summary: NetBeans Platform Application only compiles with default 
JDK
 Key: NETBEANS-3278
 URL: https://issues.apache.org/jira/browse/NETBEANS-3278
 Project: NetBeans
  Issue Type: Bug
  Components: apisupport - Harness
Affects Versions: 11.1, 11.0, 11.2
 Environment: Windows 10
Reporter: matteodg


I created from scratch a simple NetBeans Platform Application with a single 
module and I would like to use a Java Platform different than the default one, 
but I can't because I got this error while building the application:
{noformat}
module.taskdefs:
module.common-init:
Warning: nbjdk.active=OpenJDK13 or nbjdk.home=D:\Java\OpenJDK\jdk-13.0.1 is an 
invalid Java platform; ignoring and using D:\Java\OpenJDK
module.projectized-common.basic-init:
module.basic-init:
{noformat}
I'm launching NetBeans IDE with Oracle JDK 13 (default JDK) but I would like to 
compile and run with OpenJDK 13 (which I properly configured in Tools->Java 
Platforms).

I checked and this bug is present in NB 11.0, 11.1 and 11.2-beta3 as well



--
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-1105) Compiling using NB8.1 as platform does not work in NB9

2019-07-08 Thread matteodg (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg updated NETBEANS-1105:
---
Affects Version/s: 11.0

> Compiling using NB8.1 as platform does not work in NB9
> --
>
> Key: NETBEANS-1105
> URL: https://issues.apache.org/jira/browse/NETBEANS-1105
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Harness
>Affects Versions: 9.0, 11.0
>Reporter: matteodg
>Priority: Major
> Fix For: 9.0
>
> Attachments: application.zip
>
>
> We are going to move to NB9 as our IDE, so we tried to compile our 
> application based on Java8 and NB8.1 in NB9 IDE.
> Successfully set the Java platform to be Java 8 and NB platform+harness to be 
> NB8.1, but when we compile a module containing a @ServiceProvider annotation 
> to inject in the global lookup an implementation of an SPI we get this error:
>  
> {noformat}
> ...
> Compiling 2 source files to D:\code\test\application\module\build\classes
> error: java.nio.file.NoSuchFileException: 
> D:\code\test\application\module\build\classes\META-INF\services\module.SPI
> 1 error
> ...
> {noformat}
>  
> Attached a simple NB rich client application with a single module.
> The problem arises only by using Java8+NB8.1 as platform, whereas using 
> Java10+NB9 as platform it works fine. We also tried to force NB to use Ant 
> from NB8.1 (extide/ant), but nothing changes.
> Something strange is that launching Ant and outputting the environment 
> variables we have this even though we set the JAVA_HOME environment variable 
> to point to Java8:
>  
> {noformat}
> env.JAVA_HOME=C:\Program Files\Java\jdk1.8.0_181
> java.home=C:\Program Files\Java\jdk-10.0.2
> java.version=10.0.2
> java.specification.version=10
> java.runtime.version=10.0.2+13
> java.vm.version=10.0.2+13
> {noformat}
> So we guess the problem is with Java or Ant?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



[jira] [Updated] (NETBEANS-1105) Compiling using NB8.1 as platform does not work in NB9

2018-08-02 Thread matteodg (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

matteodg updated NETBEANS-1105:
---
Description: 
We are going to move to NB9 as our IDE, so we tried to compile our application 
based on Java8 and NB8.1 in NB9 IDE.

Successfully set the Java platform to be Java 8 and NB platform+harness to be 
NB8.1, but when we compile a module containing a @ServiceProvider annotation to 
inject in the global lookup an implementation of an SPI we get this error:

 
{noformat}
...
Compiling 2 source files to D:\code\test\application\module\build\classes
error: java.nio.file.NoSuchFileException: 
D:\code\test\application\module\build\classes\META-INF\services\module.SPI
1 error
...
{noformat}
 

Attached a simple NB rich client application with a single module.

The problem arises only by using Java8+NB8.1 as platform, whereas using 
Java10+NB9 as platform it works fine. We also tried to force NB to use Ant from 
NB8.1 (extide/ant), but nothing changes.

Something strange is that launching Ant and outputting the environment 
variables we have this even though we set the JAVA_HOME environment variable to 
point to Java8:

 
{noformat}
env.JAVA_HOME=C:\Program Files\Java\jdk1.8.0_181
java.home=C:\Program Files\Java\jdk-10.0.2
java.version=10.0.2
java.specification.version=10
java.runtime.version=10.0.2+13
java.vm.version=10.0.2+13
{noformat}
So we guess the problem is with Java or Ant?

  was:
We are going to move to NB9 as our IDE, so we tried to compile our application 
based on Java8 and NB8.1 in NB9 IDE.

Successfully set the Java platform to be Java 8 and NB platform+harness to be 
NB8.1, but when we compile a module containing a @ServiceProvider annotation to 
inject in the global lookup an implementation of an SPI we get this error:

 
{noformat}
...
warning: Supported source version 'RELEASE_7' from annotation processor 
'org.netbeans.modules.openide.util.ServiceProviderProcessor' less than -source 
'8'
error: java.nio.file.NoSuchFileException: 
D:\code\studioSL\trunk\commons\utilities\build\classes\META-INF\services\com.streamsim.utilities.io.WindowsUtilities
...
{noformat}
 

Attached a simple NB rich client application with a single module.

The problem arises only by using Java8+NB8.1 as platform, whereas using 
Java10+NB9 as platform it works fine. We also tried to force NB to use Ant from 
NB8.1 (extide/ant), but nothing changes.

Something strange is that launching Ant and outputting the environment 
variables we have this even though we set the JAVA_HOME environment variable to 
point to Java8:

 
{noformat}
env.JAVA_HOME=C:\Program Files\Java\jdk1.8.0_181
java.home=C:\Program Files\Java\jdk-10.0.2
java.version=10.0.2
java.specification.version=10
java.runtime.version=10.0.2+13
java.vm.version=10.0.2+13
{noformat}
So we guess the problem is with Java or Ant?


> Compiling using NB8.1 as platform does not work in NB9
> --
>
> Key: NETBEANS-1105
> URL: https://issues.apache.org/jira/browse/NETBEANS-1105
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Harness
>Affects Versions: 9.0
>Reporter: matteodg
>Priority: Major
> Fix For: 9.0
>
> Attachments: application.zip
>
>
> We are going to move to NB9 as our IDE, so we tried to compile our 
> application based on Java8 and NB8.1 in NB9 IDE.
> Successfully set the Java platform to be Java 8 and NB platform+harness to be 
> NB8.1, but when we compile a module containing a @ServiceProvider annotation 
> to inject in the global lookup an implementation of an SPI we get this error:
>  
> {noformat}
> ...
> Compiling 2 source files to D:\code\test\application\module\build\classes
> error: java.nio.file.NoSuchFileException: 
> D:\code\test\application\module\build\classes\META-INF\services\module.SPI
> 1 error
> ...
> {noformat}
>  
> Attached a simple NB rich client application with a single module.
> The problem arises only by using Java8+NB8.1 as platform, whereas using 
> Java10+NB9 as platform it works fine. We also tried to force NB to use Ant 
> from NB8.1 (extide/ant), but nothing changes.
> Something strange is that launching Ant and outputting the environment 
> variables we have this even though we set the JAVA_HOME environment variable 
> to point to Java8:
>  
> {noformat}
> env.JAVA_HOME=C:\Program Files\Java\jdk1.8.0_181
> java.home=C:\Program Files\Java\jdk-10.0.2
> java.version=10.0.2
> java.specification.version=10
> java.runtime.version=10.0.2+13
> java.vm.version=10.0.2+13
> {noformat}
> So we guess the problem is with Java or Ant?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 

[jira] [Created] (NETBEANS-1105) Compiling using NB8.1 as platform does not work in NB9

2018-08-02 Thread matteodg (JIRA)
matteodg created NETBEANS-1105:
--

 Summary: Compiling using NB8.1 as platform does not work in NB9
 Key: NETBEANS-1105
 URL: https://issues.apache.org/jira/browse/NETBEANS-1105
 Project: NetBeans
  Issue Type: Bug
  Components: apisupport - Harness
Affects Versions: 9.0
Reporter: matteodg
 Fix For: 9.0
 Attachments: application.zip

We are going to move to NB9 as our IDE, so we tried to compile our application 
based on Java8 and NB8.1 in NB9 IDE.

Successfully set the Java platform to be Java 8 and NB platform+harness to be 
NB8.1, but when we compile a module containing a @ServiceProvider annotation to 
inject in the global lookup an implementation of an SPI we get this error:

 
{noformat}
...
warning: Supported source version 'RELEASE_7' from annotation processor 
'org.netbeans.modules.openide.util.ServiceProviderProcessor' less than -source 
'8'
error: java.nio.file.NoSuchFileException: 
D:\code\studioSL\trunk\commons\utilities\build\classes\META-INF\services\com.streamsim.utilities.io.WindowsUtilities
...
{noformat}
 

Attached a simple NB rich client application with a single module.

The problem arises only by using Java8+NB8.1 as platform, whereas using 
Java10+NB9 as platform it works fine. We also tried to force NB to use Ant from 
NB8.1 (extide/ant), but nothing changes.

Something strange is that launching Ant and outputting the environment 
variables we have this even though we set the JAVA_HOME environment variable to 
point to Java8:

 
{noformat}
env.JAVA_HOME=C:\Program Files\Java\jdk1.8.0_181
java.home=C:\Program Files\Java\jdk-10.0.2
java.version=10.0.2
java.specification.version=10
java.runtime.version=10.0.2+13
java.vm.version=10.0.2+13
{noformat}
So we guess the problem is with Java or Ant?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists