[jira] [Resolved] (NETBEANS-5107) Netbeans 12.2, some directories don't load

2021-01-01 Thread Laszlo Kishalmi (Jira)


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

Laszlo Kishalmi resolved NETBEANS-5107.
---
Resolution: Information Provided

> Netbeans 12.2, some directories don't load
> --
>
> Key: NETBEANS-5107
> URL: https://issues.apache.org/jira/browse/NETBEANS-5107
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Directory Chooser
>Affects Versions: 12.2
>Reporter: Raul Gutierrez Niubo
>Priority: Blocker
> Attachments: NetbeansPic01.png, NetbeansPic02.jpg
>
>
> I recently upgraded to MacOS Big Sur and Netbeans broke. I just Updated to 
> the 12.2 version and now I'm able to open it and it works. However, I can't 
> get any work done because the directories don't load. If I go open a project, 
> I can't because when I get in my computer's folder, nothing shows up inside, 
> so it's like the files are not loading in the directory chooser. In the 
> attached pictures, you can see how when I open up a folder, it shows nothing 
> inside. Please, is there any way to fix this issue?



--
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-5177) Crash: cannot get exclusive access to uihandler.properties

2021-01-01 Thread Laszlo Kishalmi (Jira)


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

Laszlo Kishalmi commented on NETBEANS-5177:
---

Try to use the following command:


restorecon -R -v /home/ulrichmayring/.netbeans

 

if that would help then it would be some SELinux issue

> Crash: cannot get exclusive access to uihandler.properties
> --
>
> Key: NETBEANS-5177
> URL: https://issues.apache.org/jira/browse/NETBEANS-5177
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 12.2
>Reporter: Ulrich Mayring
>Priority: Blocker
> Attachments: sc.png
>
>
> I experienced a number of total freezes after installing NB 12.2 (have been 
> using 12.0 before), but could not get an error message of any sort, since NB 
> was completely unresponsive to keystrokes or mouse. This changed today, I got 
> an error popup, which I attach. NB was again totally unresponsive, but I 
> could make a screenshot of the popup message.
> The black shadow around the error dialog actually is tens or hundreds of the 
> same popup windows behind the first one. They keep piling up at CPU speed 
> until the app runs out of memory or is killed. For a while I could close a 
> few of them, but they kept coming up faster than I could click.
> The file in question (see screenshot) looks normal to me. It has the correct 
> owner and permissions and its content is this:
> count=1000
>  MTTF=71985
>  uihandler.preferences.writable.check=1608633016127
> The crash happened directly after starting the IDE, while it was reading in 
> the last project I worked on. No user interaction was involved.
> Fedora 29 / KDE.



--
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-5206) Enable LazyOpen for Gradle Project by default, deprecate Exerimental settings

2021-01-01 Thread Laszlo Kishalmi (Jira)


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

Laszlo Kishalmi resolved NETBEANS-5206.
---
Fix Version/s: 12.3
   Resolution: Implemented

> Enable LazyOpen for Gradle Project by default, deprecate Exerimental settings
> -
>
> Key: NETBEANS-5206
> URL: https://issues.apache.org/jira/browse/NETBEANS-5206
> Project: NetBeans
>  Issue Type: Improvement
>Reporter: Laszlo Kishalmi
>Assignee: Laszlo Kishalmi
>Priority: Major
>  Labels: pull-request-available
> Fix For: 12.3
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> As the Source Group issue NETBEANS-4938 has been fixed. It is possible to 
> enable the lazy initialization of Gradle project. That means it appears in 
> the project explorer with its heuristic detected state, later on when the 
> project gets loaded it would refresh the project accordingly.
> Also, planning to add more feature flags to the Settings so create an 
> experimental settings fro Gradle project that do not get exposed as SPI would 
> be a good idea.



--
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



[netbeans] branch master updated (cdeb588 -> 7c7c7b6)

2021-01-01 Thread lkishalmi
This is an automated email from the ASF dual-hosted git repository.

lkishalmi pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/netbeans.git.


from cdeb588  Merge pull request #2625 from rs333/NETBEANS-4256
 add 7c7c7b6  [NETBEANS-5206] Enable LazyOpen on Gradle Projects, deprecate 
experimental settings

No new revisions were added by this update.

Summary of changes:
 extide/gradle/apichanges.xml   | 15 +
 .../modules/gradle/NbGradleProjectImpl.java|  4 +-
 .../modules/gradle/cache/AbstractDiskCache.java|  4 +-
 .../gradle/options/GradleExperimentalSettings.java | 64 ++
 .../modules/gradle/options/SettingsPanel.java  | 17 +++---
 .../modules/gradle/spi/GradleSettings.java | 44 +--
 .../gradle/AbstractGradleProjectTestCase.java  |  2 +
 7 files changed, 135 insertions(+), 15 deletions(-)
 create mode 100644 
extide/gradle/src/org/netbeans/modules/gradle/options/GradleExperimentalSettings.java


-
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-5208) Fix for java.io.IOException: CreateProcess error=206, The filename or extension is too long

2021-01-01 Thread B A (Jira)
B A created NETBEANS-5208:
-

 Summary: Fix for java.io.IOException: CreateProcess error=206, The 
filename or extension is too long
 Key: NETBEANS-5208
 URL: https://issues.apache.org/jira/browse/NETBEANS-5208
 Project: NetBeans
  Issue Type: Improvement
Affects Versions: 12.2
 Environment: Windows 10, Java 11.0.1, Netbeans 12.2, maven
Reporter: B A


There are projects that can generate "*java.io.IOException: CreateProcess 
error=206, The filename or extension is too long*" errors when trying to run 
the project.

IntelliJ fixes this with "shorten the command line" option in the 
"configuration" menu for the project.  It utilizes Java 9 (and greater) ability 
to use @argfiles instead of huge list of text as argument to java executables.

As far as I can tell, Netbeans does not have this ability, leaving you with 
options such as renaming or moving directories to make the arguments have fewer 
characters in them, which is a huge pain (and maybe not possible) for huge 
projects made by other people (like dl4j).

I ran into this when running classes out of the Deeplearning4j package.  I was 
following the standard instructions of how to install it and run an example 
class, and it generated the error=206 filename or extension too long.



--
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-5205) xdebug time out errors debugging PHP v8 code

2021-01-01 Thread Jira


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

Tomáš Procházka closed NETBEANS-5205.
-
Resolution: Duplicate

Duplicates NETBEANS-5060.

> xdebug time out errors debugging PHP v8 code
> 
>
> Key: NETBEANS-5205
> URL: https://issues.apache.org/jira/browse/NETBEANS-5205
> Project: NetBeans
>  Issue Type: Bug
>  Components: php - Debugger
>Affects Versions: 12.2
> Environment: Windows 10 using IIS
> xdebug 3.0.1
> PHP 8.0
>Reporter: Dave Power
>Priority: Major
>
> Basically, Netbeans is current unusable for developing and debugging code 
> using PHP 8.0.
> PHP v8.0 requires xdebug v3.0.1   Following the xdebug configuration 
> instructions as follows
> {quote}zend_extension = C:\Program 
> Files\php\8.0\ext\php_xdebug-3.0.1-8.0-vs16-nts-x86_64.dll
> xdebug.mode=debug
> xdebug.remote_enable=on
> xdebug.remote_host=localhost
> {quote}
> I am finding that I receive a large number of xdebug timeout errors linked to 
> the connection between the IDE and webbrowser.
> {quote}[01-Jan-2021 11:31:36 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:31:36 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:31:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:31:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:32:36 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:32:36 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:32:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:32:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:34:36 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:34:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:34:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:34:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:36:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:36:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:36:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:36:38 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:38:36 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:38:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:38:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 11:38:38 UTC] Xdebug: [Step Debug] Time-out connecting to 
> debugging client, waited: 200 ms. Tried: localhost:9003 (through 
> xdebug.client_host/xdebug.client_port) :-(
> [01-Jan-2021 

[jira] [Commented] (NETBEANS-5195) Change icon for JSON files

2021-01-01 Thread Jira


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

Tomáš Procházka commented on NETBEANS-5195:
---

What about file icon without "paper" background?

Symbol can be slightly bigger and easier to recognize - take a look at icons 
for CSS files or package.json.

I like outlined braces because they will be recognizable also in dark themes 
(FlatLaf Dark).

> Change icon for JSON files
> --
>
> Key: NETBEANS-5195
> URL: https://issues.apache.org/jira/browse/NETBEANS-5195
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Generic Projects UI
>Reporter: Martin H.
>Priority: Minor
> Attachments: json-logo.png, outline-braces.png, regular-braces.png
>
>
> I would like to suggest an alternate icon for the JSON file type, as it is 
> currently denoted by the same icon as JavaScript files. Below are some 
> variants.
>  #  The graphical logo for JSON.
> (See https://en.wikipedia.org/wiki/JSON#/media/File:JSON_vector_logo.svg)
> !json-logo.png!
>  # Curly braces, as in some other IDEs.
> !regular-braces.png!
>  # Outlined curly braces, matching the style of some other NetBeans file 
> icons.
> !outline-braces.png!
>  



--
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-4816) NetBeans database explorer does not handle partitioned tables in PostgreSQL correctly

2021-01-01 Thread Jakub Herkel (Jira)


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

Jakub Herkel updated NETBEANS-4816:
---
Attachment: table_with_partitions.png

> NetBeans database explorer does not handle partitioned tables in PostgreSQL 
> correctly
> -
>
> Key: NETBEANS-4816
> URL: https://issues.apache.org/jira/browse/NETBEANS-4816
> Project: NetBeans
>  Issue Type: Improvement
>  Components: db - Show Data
>Affects Versions: 12.1
>Reporter: Stefan Sonnenberg-Carstens
>Assignee: Jakub Herkel
>Priority: Major
> Attachments: image-2020-09-18-18-55-37-559.png, 
> image-2020-09-18-19-00-36-938.png, table_with_partitions.png
>
>
> To reproduce:
> connect to a PostgreSQL database (in my case 12.4)
> issue the following commands:
> {code:sql}
> DROP TABLE IF EXISTS T1;
> CREATE TABLE T1 (ID INTEGER, MESSAGE TEXT, TIMESTAMP TIMESTAMP) PARTITION BY 
> RANGE (TIMESTAMP); CREATE TABLE T1_2020 PARTITION OF T1 FOR VALUES FROM 
> ('2020-01-01') TO ('2020-12-31'); CREATE TABLE T1_2021 PARTITION OF T1 FOR 
> VALUES FROM ('2021-01-01') TO ('2021-12-31'); CREATE TABLE T1_2022 PARTITION 
> OF T1 FOR VALUES FROM ('2022-01-01') TO ('2022-12-31'); CREATE TABLE T1_2023 
> PARTITION OF T1 FOR VALUES FROM ('2023-01-01') TO ('2023-12-31');{code}
> After successful execution you will see a picture like this below:
> !image-2020-09-18-18-55-37-559.png!
> The base table T1 is not visible at all and the sub-tables are shown as if 
> they were regular tables.
> The same schema will be shown in IntelliJ like this (which is correct imho):
> !image-2020-09-18-19-00-36-938.png!
> T1 will be shown as a regular table and the attached partition tables / 
> sub-tables are shown below it. This makes clear, that t1 is partitioned.
> At least all tables including t1 should be visible.
>  



--
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-4816) NetBeans database explorer does not handle partitioned tables in PostgreSQL correctly

2021-01-01 Thread Jakub Herkel (Jira)


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

Jakub Herkel commented on NETBEANS-4816:


I have prototype for this but it needs more work to be done to make it completed

!table_with_partitions.png!

> NetBeans database explorer does not handle partitioned tables in PostgreSQL 
> correctly
> -
>
> Key: NETBEANS-4816
> URL: https://issues.apache.org/jira/browse/NETBEANS-4816
> Project: NetBeans
>  Issue Type: Improvement
>  Components: db - Show Data
>Affects Versions: 12.1
>Reporter: Stefan Sonnenberg-Carstens
>Assignee: Jakub Herkel
>Priority: Major
> Attachments: image-2020-09-18-18-55-37-559.png, 
> image-2020-09-18-19-00-36-938.png, table_with_partitions.png
>
>
> To reproduce:
> connect to a PostgreSQL database (in my case 12.4)
> issue the following commands:
> {code:sql}
> DROP TABLE IF EXISTS T1;
> CREATE TABLE T1 (ID INTEGER, MESSAGE TEXT, TIMESTAMP TIMESTAMP) PARTITION BY 
> RANGE (TIMESTAMP); CREATE TABLE T1_2020 PARTITION OF T1 FOR VALUES FROM 
> ('2020-01-01') TO ('2020-12-31'); CREATE TABLE T1_2021 PARTITION OF T1 FOR 
> VALUES FROM ('2021-01-01') TO ('2021-12-31'); CREATE TABLE T1_2022 PARTITION 
> OF T1 FOR VALUES FROM ('2022-01-01') TO ('2022-12-31'); CREATE TABLE T1_2023 
> PARTITION OF T1 FOR VALUES FROM ('2023-01-01') TO ('2023-12-31');{code}
> After successful execution you will see a picture like this below:
> !image-2020-09-18-18-55-37-559.png!
> The base table T1 is not visible at all and the sub-tables are shown as if 
> they were regular tables.
> The same schema will be shown in IntelliJ like this (which is correct imho):
> !image-2020-09-18-19-00-36-938.png!
> T1 will be shown as a regular table and the attached partition tables / 
> sub-tables are shown below it. This makes clear, that t1 is partitioned.
> At least all tables including t1 should be visible.
>  



--
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-5114) Generated ui:composition missing xmlns

2021-01-01 Thread Jira


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

Matthias Bläsing commented on NETBEANS-5114:


Please provide a minimal sample project, that reproduces the problem - I 
checked one of my JSF projects and on master removing the namespace declaration 
does not render the xhtml files invalid.

> Generated ui:composition missing xmlns
> --
>
> Key: NETBEANS-5114
> URL: https://issues.apache.org/jira/browse/NETBEANS-5114
> Project: NetBeans
>  Issue Type: Bug
>  Components: javaee - JSF
>Affects Versions: 12.1
> Environment: Windows 10 / Netbeans 12.1
>Reporter: Stephen Brooksbank
>Assignee: Jakub Herkel
>Priority: Minor
>  Labels: pull-request-available
> Attachments: image-2020-12-08-12-10-40-084.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When generating a facelets client page using:
> new --> Facelets Template Client --> ui:composition option
> the generated file is missing:
> {{xmlns="http://www.w3.org/1999/xhtml"; }}
> namespace from the ui:composition header tag:
> !image-2020-12-08-12-10-40-084.png!
>  
> This causes page errors as soon as standard HTML tags are added to the page, 
> such as .
> Please correct the template generation code for this case. Thanks.
>  



--
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-5207) i am make Java EE project but in netbeans webinf not funtioning so servlet class not working i tried but issue not resolved

2021-01-01 Thread suman sahu (Jira)
suman sahu created NETBEANS-5207:


 Summary: i am make Java EE project but in netbeans webinf not 
funtioning so servlet class not working i tried but issue not resolved
 Key: NETBEANS-5207
 URL: https://issues.apache.org/jira/browse/NETBEANS-5207
 Project: NetBeans
  Issue Type: Bug
Reporter: suman sahu






--
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-4256) XML Fonts & Colors reload bug

2021-01-01 Thread R Schultz (Jira)


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

R Schultz resolved NETBEANS-4256.
-
Fix Version/s: Next
   Resolution: Fixed

See Pull Request #2625 for details.

> XML Fonts & Colors reload bug
> -
>
> Key: NETBEANS-4256
> URL: https://issues.apache.org/jira/browse/NETBEANS-4256
> Project: NetBeans
>  Issue Type: Bug
>  Components: editor - Painting & Printing
>Affects Versions: 11.3, 12.2
> Environment: Windows 10 64bits
> Netbeans 11.3/12.x
> Linux
>Reporter: Bruno
>Assignee: R Schultz
>Priority: Minor
>  Labels: pull-request-available
> Fix For: Next
>
> Attachments: xml_problem.diff
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> HI,
> There is a probleme when trying to change de color propoerties in XML language
> If you try to change "pi-content" and "xml-pi-target", it will be saved into 
> the 
> "org-netbeans-modules-editor-settings-CustomFontsColors-tokenColorings.xml" 
> file for the selected profile. It will also be OK in the current session of 
> the NetBeans IDE
> If you close and re open Netbeans IDE, the properties values for "pi-content" 
> and "xml-pi-target" for XML language won't be read back from the config file 
> "org-netbeans-modules-editor-settings-CustomFontsColors-tokenColorings.xml". 
> These two properties will always have [0,0,124] (hex value "ff7c") for 
> all profiles
> So it's impossible to save and read back custom values "pi-content" and 
> "xml-pi-target" for XML language



--
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-5206) Enable LazyOpen for Gradle Project by default, deprecate Exerimental settings

2021-01-01 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot updated NETBEANS-5206:
-
Labels: pull-request-available  (was: )

> Enable LazyOpen for Gradle Project by default, deprecate Exerimental settings
> -
>
> Key: NETBEANS-5206
> URL: https://issues.apache.org/jira/browse/NETBEANS-5206
> Project: NetBeans
>  Issue Type: Improvement
>Reporter: Laszlo Kishalmi
>Assignee: Laszlo Kishalmi
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> As the Source Group issue NETBEANS-4938 has been fixed. It is possible to 
> enable the lazy initialization of Gradle project. That means it appears in 
> the project explorer with its heuristic detected state, later on when the 
> project gets loaded it would refresh the project accordingly.
> Also, planning to add more feature flags to the Settings so create an 
> experimental settings fro Gradle project that do not get exposed as SPI would 
> be a good idea.



--
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-5206) Enable LazyOpen for Gradle Project by default, deprecate Exerimental settings

2021-01-01 Thread Laszlo Kishalmi (Jira)
Laszlo Kishalmi created NETBEANS-5206:
-

 Summary: Enable LazyOpen for Gradle Project by default, deprecate 
Exerimental settings
 Key: NETBEANS-5206
 URL: https://issues.apache.org/jira/browse/NETBEANS-5206
 Project: NetBeans
  Issue Type: Improvement
Reporter: Laszlo Kishalmi
Assignee: Laszlo Kishalmi


As the Source Group issue NETBEANS-4938 has been fixed. It is possible to 
enable the lazy initialization of Gradle project. That means it appears in the 
project explorer with its heuristic detected state, later on when the project 
gets loaded it would refresh the project accordingly.

Also, planning to add more feature flags to the Settings so create an 
experimental settings fro Gradle project that do not get exposed as SPI would 
be a good idea.



--
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-5199) Can't create offscreen surface

2021-01-01 Thread Laszlo Kishalmi (Jira)


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

Laszlo Kishalmi resolved NETBEANS-5199.
---
Resolution: Information Provided

Well it says: java.lang.OutOfMemoryError: Can't create offscreen surface

So either you are running low on some memory, or the used Java 8 has some bug 
in the native GTK rendering.

I'd recommend to try a different JDK and or LookAndFeel or maybe upgrade your 
RAM if needed.

Unfortunately there is nothing else we can do about this issue.

> Can't create offscreen surface
> --
>
> Key: NETBEANS-5199
> URL: https://issues.apache.org/jira/browse/NETBEANS-5199
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 12.2
> Environment:   Operating System= Linux version 
> 5.4.0-59-generic running on amd64
>   Java; VM; Vendor= 1.8.0_275; OpenJDK 64-Bit Server VM 25.275-b01; 
> Private Build
>   Runtime = OpenJDK Runtime Environment 
> 1.8.0_275-8u275-b01-0ubuntu1~20.04-b01
>   Java Home   = /usr/lib/jvm/java-8-openjdk-amd64/jre
>   System Locale; Encoding = nl_NL (nb); UTF-8
>Reporter: Remko de Keijzer
>Priority: Major
>
> 
>  2020-12-30T18:01:39
>  1609347699114
>  42641
>  global
>  1000
>  20
>  
> /home/remko/snap/netbeans/common/data/12.2/var/log/heapdump.hprof
>  
>  java.lang.OutOfMemoryError: Can't create offscreen surface
>  
>  com.sun.java.swing.plaf.gtk.GTKEngine
>  nativeStartPainting
>  ${java.home}lib/rt.jar
>  
>  
>  com.sun.java.swing.plaf.gtk.GTKEngine
>  startPainting
>  576
>  ${java.home}lib/rt.jar
>  
>  
>  com.sun.java.swing.plaf.gtk.GTKPainter
>  paintToolTipBackground
>  1286
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.plaf.synth.SynthToolTipUI
>  update
>  139
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.JComponent
>  paintComponent
>  780
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.JComponent
>  paint
>  1056
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.JComponent
>  paintChildren
>  889
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.JComponent
>  paint
>  1065
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.JComponent
>  paintChildren
>  889
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.JComponent
>  paint
>  1065
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.JLayeredPane
>  paint
>  586
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.JComponent
>  paintChildren
>  889
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.JComponent
>  paintToOffscreen
>  5217
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.RepaintManager$PaintManager
>  paintDoubleBuffered
>  1579
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.RepaintManager$PaintManager
>  paint
>  1502
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.BufferStrategyPaintManager
>  paint
>  306
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.RepaintManager
>  paint
>  1272
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.JComponent
>  paint
>  1042
>  ${java.home}lib/rt.jar
>  
>  
>  java.awt.GraphicsCallback$PaintCallback
>  run
>  39
>  ${java.home}lib/rt.jar
>  
>  
>  sun.awt.SunGraphicsCallback
>  runOneComponent
>  79
>  ${java.home}lib/rt.jar
>  
>  
>  sun.awt.SunGraphicsCallback
>  runComponents
>  116
>  ${java.home}lib/rt.jar
>  
>  
>  java.awt.Container
>  paint
>  1978
>  ${java.home}lib/rt.jar
>  
>  
>  java.awt.Window
>  paint
>  3906
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.RepaintManager$4
>  run
>  842
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.RepaintManager$4
>  run
>  814
>  ${java.home}lib/rt.jar
>  
>  
>  java.security.AccessController
>  doPrivileged
>  ${java.home}lib/rt.jar
>  
>  
>  java.security.ProtectionDomain$JavaSecurityAccessImpl
>  doIntersectionPrivilege
>  74
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.RepaintManager
>  paintDirtyRegions
>  814
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.RepaintManager
>  paintDirtyRegions
>  789
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.RepaintManager
>  prePaintDirtyRegions
>  738
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.RepaintManager
>  access$1200
>  64
>  ${java.home}lib/rt.jar
>  
>  
>  javax.swing.RepaintManager$ProcessingRunnable
>  run
>  1732
>  ${java.home}lib/rt.jar
>  
>  
>  java.awt.event.InvocationEvent
>  dispatch
>  311
>  ${java.home}lib/rt.jar
>  
>  
>  java.awt.EventQueue
>  dispatchEventImpl
>  758
>  ${java.home}lib/rt.jar
>  
>  
>  java.awt.EventQueue
>  access$500
>  97
>  ${java.home}lib/rt.jar
>  
>  
>  java.awt.EventQueue$3
>  run
>  709
>  ${java.home}lib/rt.jar
>  
>  
>  java.awt.EventQueue$3
>  run
>  703
>  ${java.home}lib/rt.jar
>  
>  
>  java.security.AccessController
>  doPrivileged
>  ${java.home}lib/rt.jar
>  
>  
>  java.security.ProtectionDomain$JavaSecurityAccessImpl
>  doIntersectionPrivilege
>  74
>  ${java.home}lib/rt.jar
>  
>  
>  java

[netbeans] branch master updated: [NETBEANS-4256] Fixed inconsistent xml fontcolor tag names.

2021-01-01 Thread matthiasblaesing
This is an automated email from the ASF dual-hosted git repository.

matthiasblaesing pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/netbeans.git


The following commit(s) were added to refs/heads/master by this push:
 new 7974ac5  [NETBEANS-4256] Fixed inconsistent xml fontcolor tag names.
 new cdeb588  Merge pull request #2625 from rs333/NETBEANS-4256
7974ac5 is described below

commit 7974ac5922c7fc0c20c4fd30e2d3e1f0cdb363c2
Author: Robert Schultz 
AuthorDate: Thu Dec 31 11:11:04 2020 -0500

[NETBEANS-4256] Fixed inconsistent xml fontcolor tag names.
---
 .../src/org/netbeans/api/xml/lexer/XMLTokenId.java |   4 +-
 .../modules/xml/text/resources/Bundle.properties   |   4 +-
 .../modules/xml/text/resources/XML-fontsColors.xml |   4 +-
 .../goldenfiles/ColoringTest/testXMLColoring.pass  | 260 ++---
 4 files changed, 136 insertions(+), 136 deletions(-)

diff --git a/ide/xml.lexer/src/org/netbeans/api/xml/lexer/XMLTokenId.java 
b/ide/xml.lexer/src/org/netbeans/api/xml/lexer/XMLTokenId.java
index be0c75b..1e96171 100644
--- a/ide/xml.lexer/src/org/netbeans/api/xml/lexer/XMLTokenId.java
+++ b/ide/xml.lexer/src/org/netbeans/api/xml/lexer/XMLTokenId.java
@@ -67,9 +67,9 @@ public enum XMLTokenId implements TokenId {
 /* PI target  */
 PI_TARGET("xml-pi-target"),
 /* PI conetnt  */
-PI_CONTENT("pi-content"),
+PI_CONTENT("xml-pi-content"),
 /* PI end delimiter  
*/
-PI_END("pi-end"),
+PI_END("xml-pi-end"),
 /** Cdata section including its delimiters. */
 CDATA_SECTION("xml-cdata-section");
 
diff --git 
a/ide/xml.text/src/org/netbeans/modules/xml/text/resources/Bundle.properties 
b/ide/xml.text/src/org/netbeans/modules/xml/text/resources/Bundle.properties
index eb98248..e75c134 100644
--- a/ide/xml.text/src/org/netbeans/modules/xml/text/resources/Bundle.properties
+++ b/ide/xml.text/src/org/netbeans/modules/xml/text/resources/Bundle.properties
@@ -38,8 +38,8 @@ xml-ws=Markup Whitespace
 xml-operator=Operators
 xml-EOL=New Line (deprecated)
 xml-pi-start=PI Start Delimiter
-pi-end=PI End Delimiter
-pi-target=PI Target
+xml-pi-end=PI End Delimiter
+xml-pi-target=PI Target
 xml-pi-content=PI Content
 xml-cdata-section=CDATA Section
 
diff --git 
a/ide/xml.text/src/org/netbeans/modules/xml/text/resources/XML-fontsColors.xml 
b/ide/xml.text/src/org/netbeans/modules/xml/text/resources/XML-fontsColors.xml
index 62dbcab..29d9bb8 100644
--- 
a/ide/xml.text/src/org/netbeans/modules/xml/text/resources/XML-fontsColors.xml
+++ 
b/ide/xml.text/src/org/netbeans/modules/xml/text/resources/XML-fontsColors.xml
@@ -31,8 +31,8 @@
 
 
 
-
-
+
+
 
 
 
diff --git 
a/ide/xml.text/test/qa-functional/src/org/netbeans/modules/xml/text/syntax/data/goldenfiles/ColoringTest/testXMLColoring.pass
 
b/ide/xml.text/test/qa-functional/src/org/netbeans/modules/xml/text/syntax/data/goldenfiles/ColoringTest/testXMLColoring.pass
index 54dace9..757ee3e 100644
--- 
a/ide/xml.text/test/qa-functional/src/org/netbeans/modules/xml/text/syntax/data/goldenfiles/ColoringTest/testXMLColoring.pass
+++ 
b/ide/xml.text/test/qa-functional/src/org/netbeans/modules/xml/text/syntax/data/goldenfiles/ColoringTest/testXMLColoring.pass
@@ -1,168 +1,168 @@
-pi-start: 
-text: 
+xml-pi-start: 
+xml-text: 
 
 
-comment: 
-text: 
+xml-comment: 
+xml-text: 
 
 
-pi-start: 
-text: 
+xml-pi-start: 
+xml-text: 
 
 
-doctype: 
-text:  
-doctype: 
-text: 
+xml-doctype: 
+xml-text:  
+xml-doctype: 
+xml-text: 
 
-doctype: 
-text:   
-doctype: 
-text: 
+xml-doctype: 
+xml-text:   
+xml-doctype: 
+xml-text: 
 
-ref: %states;
-text: 
-doctype: 
-text: 
+xml-ref: %states;
+xml-text: 
+xml-doctype: 
+xml-text: 
 
-doctype: 
-text:  
-pi-start: 
-text: 
+xml-doctype: 
+xml-text:  
+xml-pi-start: 
+xml-text: 
 
-doctype: 
-text: 
-comment: 
-text: 
+xml-doctype: 
+xml-text: 
+xml-comment: 
+xml-text: 
 
-doctype: 
-text:
-doctype: 
-text: 
+xml-doctype: 
+xml-text:
+xml-doctype: 
+xml-text: 
 
-doctype: 
-text: 
+xml-text: 
 
-comment: 
-text:  
-doctype: 
-text: 
+xml-comment: 
+xml-text:  
+xml-doctype: 
+xml-text: 
 
-doctype: 
-text: 
-comment: 
-text: 
+xml-doctype: 
+xml-text: 
+xml-comment: 
+xml-text: 
 
-doctype: 
-comment: 
-text: 
+xml-doctype: 
+xml-comment: 
+xml-text: 

-doctype: 
-doctype: 
+xml-doctype: 
+xml-doctype: 
 ]>
-text: 
+xml-text: 
 
 
-pi-start: 
-text: 
+xml-pi-start: 
+xml-text: 
 
 
-tag: 
-pi-start: 
-text: 
+xml-tag: 
+xml-pi-start: 
+xml-text: 
   
-tag: 
-text: Product 1 - 
-ref: d
-text:  
-ref: >
-text:  
-ref: ™
-text:   
+xml-

[jira] [Commented] (NETBEANS-5195) Change icon for JSON files

2021-01-01 Thread Christian Lenz (Jira)


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

Christian Lenz commented on NETBEANS-5195:
--

Cool suggestions. I like the blue a lot, but I think it is a bit to hard to 
recognize it. So I'm for the regular braces. Also we need to know the exact 
license for the icon.

> Change icon for JSON files
> --
>
> Key: NETBEANS-5195
> URL: https://issues.apache.org/jira/browse/NETBEANS-5195
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Generic Projects UI
>Reporter: Martin H.
>Priority: Minor
> Attachments: json-logo.png, outline-braces.png, regular-braces.png
>
>
> I would like to suggest an alternate icon for the JSON file type, as it is 
> currently denoted by the same icon as JavaScript files. Below are some 
> variants.
>  #  The graphical logo for JSON.
> (See https://en.wikipedia.org/wiki/JSON#/media/File:JSON_vector_logo.svg)
> !json-logo.png!
>  # Curly braces, as in some other IDEs.
> !regular-braces.png!
>  # Outlined curly braces, matching the style of some other NetBeans file 
> icons.
> !outline-braces.png!
>  



--
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-5205) xdebug time out errors debugging PHP v8 code

2021-01-01 Thread Dave Power (Jira)
Dave Power created NETBEANS-5205:


 Summary: xdebug time out errors debugging PHP v8 code
 Key: NETBEANS-5205
 URL: https://issues.apache.org/jira/browse/NETBEANS-5205
 Project: NetBeans
  Issue Type: Bug
  Components: php - Debugger
Affects Versions: 12.2
 Environment: Windows 10 using IIS
xdebug 3.0.1
PHP 8.0
Reporter: Dave Power


Basically, Netbeans is current unusable for developing and debugging code using 
PHP 8.0.

PHP v8.0 requires xdebug v3.0.1   Following the xdebug configuration 
instructions as follows
{quote}zend_extension = C:\Program 
Files\php\8.0\ext\php_xdebug-3.0.1-8.0-vs16-nts-x86_64.dll
xdebug.mode=debug
xdebug.remote_enable=on
xdebug.remote_host=localhost
{quote}
I am finding that I receive a large number of xdebug timeout errors linked to 
the connection between the IDE and webbrowser.

{quote}[01-Jan-2021 11:31:36 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:31:36 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:31:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:31:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:32:36 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:32:36 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:32:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:32:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:34:36 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:34:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:34:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:34:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:36:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:36:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:36:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:36:38 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:38:36 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:38:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:38:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:38:38 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:40:36 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:40:37 UTC] Xdebug: [Step Debug] Time-out connecting to 
debugging client, waited: 200 ms. Tried: localhost:9003 (through 
xdebug.client_host/xdebug.client_port) :-(
[01-Jan-2021 11:40:37 UTC] Xdebug: [Step Debug] Time-ou

[jira] [Commented] (NETBEANS-377) Only underline the non-matching part of namespace

2021-01-01 Thread Jira


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

Tomáš Procházka commented on NETBEANS-377:
--

Here is sample of hint when source file is put into 
"src/MyApp/FirstNs/SomeClass.php".

!image-2021-01-01-14-48-29-774.png!

> Only underline the non-matching part of namespace
> -
>
> Key: NETBEANS-377
> URL: https://issues.apache.org/jira/browse/NETBEANS-377
> Project: NetBeans
>  Issue Type: Improvement
>  Components: php - Editor
>Affects Versions: 8.2
>Reporter: Simon Heimberg
>Assignee: Tomáš Procházka
>Priority: Minor
>  Labels: pull-request-available
> Attachments: image-2021-01-01-14-48-29-774.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When the namespace does not correspondent to the directory structure, the 
> namespace is underlined. Fine!
> But with PSR4 structure, the start of the namespace is often different to the 
> directory structure. But the end should match.
> I suppose to only underline the part of the namespace, which does not match 
> the directory structure. Then the user can determine himself if this part is 
> because of PSR-4 or because of a typo.



--
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-377) Only underline the non-matching part of namespace

2021-01-01 Thread Jira


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

Tomáš Procházka updated NETBEANS-377:
-
Attachment: image-2021-01-01-14-48-29-774.png

> Only underline the non-matching part of namespace
> -
>
> Key: NETBEANS-377
> URL: https://issues.apache.org/jira/browse/NETBEANS-377
> Project: NetBeans
>  Issue Type: Improvement
>  Components: php - Editor
>Affects Versions: 8.2
>Reporter: Simon Heimberg
>Assignee: Tomáš Procházka
>Priority: Minor
>  Labels: pull-request-available
> Attachments: image-2021-01-01-14-48-29-774.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When the namespace does not correspondent to the directory structure, the 
> namespace is underlined. Fine!
> But with PSR4 structure, the start of the namespace is often different to the 
> directory structure. But the end should match.
> I suppose to only underline the part of the namespace, which does not match 
> the directory structure. Then the user can determine himself if this part is 
> because of PSR-4 or because of a typo.



--
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-377) Only underline the non-matching part of namespace

2021-01-01 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot updated NETBEANS-377:

Labels: pull-request-available  (was: )

> Only underline the non-matching part of namespace
> -
>
> Key: NETBEANS-377
> URL: https://issues.apache.org/jira/browse/NETBEANS-377
> Project: NetBeans
>  Issue Type: Improvement
>  Components: php - Editor
>Affects Versions: 8.2
>Reporter: Simon Heimberg
>Assignee: Tomáš Procházka
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When the namespace does not correspondent to the directory structure, the 
> namespace is underlined. Fine!
> But with PSR4 structure, the start of the namespace is often different to the 
> directory structure. But the end should match.
> I suppose to only underline the part of the namespace, which does not match 
> the directory structure. Then the user can determine himself if this part is 
> because of PSR-4 or because of a typo.



--
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-377) Only underline the non-matching part of namespace

2021-01-01 Thread Jira


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

Tomáš Procházka commented on NETBEANS-377:
--

[PSR-4|https://www.php-fig.org/psr/psr-4/] standard is evolution of 
[PSR-0|https://www.php-fig.org/psr/psr-0/] where workarounds for absence of 
namespaces in PHP before 5.3 were removed.
 Most notable changes are:
 * Underscore character is no longer namespace separator in class name in PSR-4.
 * Namespace prefix can be mapped to base directory.
 * Directory of file must match namespace after prefix.

So I think best solution is to prepare separate PSR-4 validations. Current 
PSR-0 validations are good starting point. Future enhancements can add mapping 
from namespace prefix to base directory (manually defined or even read from 
composer.json).


> Only underline the non-matching part of namespace
> -
>
> Key: NETBEANS-377
> URL: https://issues.apache.org/jira/browse/NETBEANS-377
> Project: NetBeans
>  Issue Type: Improvement
>  Components: php - Editor
>Affects Versions: 8.2
>Reporter: Simon Heimberg
>Priority: Minor
>
> When the namespace does not correspondent to the directory structure, the 
> namespace is underlined. Fine!
> But with PSR4 structure, the start of the namespace is often different to the 
> directory structure. But the end should match.
> I suppose to only underline the part of the namespace, which does not match 
> the directory structure. Then the user can determine himself if this part is 
> because of PSR-4 or because of a typo.



--
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-377) Only underline the non-matching part of namespace

2021-01-01 Thread Jira


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

Tomáš Procházka reassigned NETBEANS-377:


Assignee: Tomáš Procházka

> Only underline the non-matching part of namespace
> -
>
> Key: NETBEANS-377
> URL: https://issues.apache.org/jira/browse/NETBEANS-377
> Project: NetBeans
>  Issue Type: Improvement
>  Components: php - Editor
>Affects Versions: 8.2
>Reporter: Simon Heimberg
>Assignee: Tomáš Procházka
>Priority: Minor
>
> When the namespace does not correspondent to the directory structure, the 
> namespace is underlined. Fine!
> But with PSR4 structure, the start of the namespace is often different to the 
> directory structure. But the end should match.
> I suppose to only underline the part of the namespace, which does not match 
> the directory structure. Then the user can determine himself if this part is 
> because of PSR-4 or because of a typo.



--
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] [Issue Comment Deleted] (NETBEANS-5181) NbBundle only accepts ISO-8859-1 while UTF-8 is default since JDK9

2021-01-01 Thread Jerome Lelasseux (Jira)


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

Jerome Lelasseux updated NETBEANS-5181:
---
Comment: was deleted

(was: To be consistent the change should also impact the IDE: with current NB12 
version, when user opens a .properties file the IDE assumes ISO-8859-1 by 
default (unless the "Use project encoding" property is set for this file).)

> NbBundle only accepts ISO-8859-1 while UTF-8 is default since JDK9
> --
>
> Key: NETBEANS-5181
> URL: https://issues.apache.org/jira/browse/NETBEANS-5181
> Project: NetBeans
>  Issue Type: Improvement
>  Components: nblocalization - Code, platform - Filesystems, platform 
> - Other
>Affects Versions: 9.0, 10.0, 11.0, 12.2
> Environment: All
>Reporter: Jerome Lelasseux
>Priority: Major
>
> Since JDK9 default encoding for .properties files (resource bundles) is 
> UTF-8. JDK's ResourceBundle.getBundle().getString() automatically handles 
> UTF-8 or ISO-8859-1 files via PropertyResourceBundle.
> But NbBundle methods always read resource bundles as ISO-8859-1. Many 
> translation platforms around  produce UTF-8 files. Adapting the build process 
> to add a transcoding step is not so easy and introduces new problems.
> The NB platform code should be updated to have by default the same behavior 
> as the current JDKs.
> I'll try to come up with a patch...
>  
>  
>  



--
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