[jira] [Resolved] (NETBEANS-1349) http://services.netbeans.org is down

2019-12-15 Thread Jira


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

Matthias Bläsing resolved NETBEANS-1349.

  Assignee: Matthias Bläsing
Resolution: Won't Fix

Please see the download page for links to older releases:
http://netbeans.apache.org/download/archive/index.html

> http://services.netbeans.org is down
> 
>
> Key: NETBEANS-1349
> URL: https://issues.apache.org/jira/browse/NETBEANS-1349
> Project: NetBeans
>  Issue Type: Bug
>  Components: website
> Environment: Google Chrome
>Reporter: Joshua McLean
>Assignee: Matthias Bläsing
>Priority: Major
>  Labels: Web
>
> Cannot send email to web master either because 
> [http://services.netbeans.org|http://services.netbeans.org/] is down. So the 
> only way I can report the issue is here.
> I'm trying to access [http://services.netbeans.org/downloads/dev.php] to 
> download an older version of Netbeans
> I get the following
>  
> h1. ERROR
> h2. The requested URL could not be retrieved
> 
> The following error was encountered while trying to retrieve the URL: 
> [http://services.netbeans.org/downloads/dev.php]
> {quote}*Read Error*
> {quote}
> The system returned: _(104) Connection reset by peer_
> An error condition occurred while reading data from the network. Please retry 
> your request.
>  
> https://downforeveryoneorjustme.com/services.netbeans.org



--
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: Upgrade Apache Commons-IO from 1.4 to 2.6

2019-12-15 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 08123d6   Upgrade Apache Commons-IO from 1.4 to 2.6
 new 9a073a2  Merge pull request #1745 from pepness/commons-io-2.6
08123d6 is described below

commit 08123d6cb4b46d07661124f8ebe895378f680317
Author: Jose Contreras 
AuthorDate: Wed Dec 4 17:04:43 2019 -0600

 Upgrade Apache Commons-IO from 1.4 to 2.6
---
 platform/o.apache.commons.io/external/binaries-list   | 2 +-
 .../{commons-io-1.4-license.txt => commons-io-2.6-license.txt}| 4 ++--
 .../external/{commons-io-1.4-notice.txt => commons-io-2.6-notice.txt} | 2 +-
 platform/o.apache.commons.io/manifest.mf  | 1 +
 platform/o.apache.commons.io/nbproject/project.properties | 4 +++-
 platform/o.apache.commons.io/nbproject/project.xml| 2 +-
 6 files changed, 9 insertions(+), 6 deletions(-)

diff --git a/platform/o.apache.commons.io/external/binaries-list 
b/platform/o.apache.commons.io/external/binaries-list
index a00542d..272a680 100644
--- a/platform/o.apache.commons.io/external/binaries-list
+++ b/platform/o.apache.commons.io/external/binaries-list
@@ -14,4 +14,4 @@
 # KIND, either express or implied.  See the License for the
 # specific language governing permissions and limitations
 # under the License.
-A8762D07E76CFDE2395257A5DA47BA7C1DBD3DCE commons-io:commons-io:1.4
+815893DF5F31DA2ECE4040FE0A12FD44B577AFAF commons-io:commons-io:2.6
diff --git a/platform/o.apache.commons.io/external/commons-io-1.4-license.txt 
b/platform/o.apache.commons.io/external/commons-io-2.6-license.txt
similarity index 99%
rename from platform/o.apache.commons.io/external/commons-io-1.4-license.txt
rename to platform/o.apache.commons.io/external/commons-io-2.6-license.txt
index 9544faf..61fba15 100644
--- a/platform/o.apache.commons.io/external/commons-io-1.4-license.txt
+++ b/platform/o.apache.commons.io/external/commons-io-2.6-license.txt
@@ -1,9 +1,9 @@
 Name: Apache Commons IO
 Description: Assist with developing IO functionality
 Origin: Apache Software Foundation
-Version: 1.4
+Version: 2.6
 License: Apache-2.0
-URL: http://commons.apache.org/io/
+URL: https://commons.apache.org/proper/commons-io/
 
 
 
diff --git a/platform/o.apache.commons.io/external/commons-io-1.4-notice.txt 
b/platform/o.apache.commons.io/external/commons-io-2.6-notice.txt
similarity index 70%
rename from platform/o.apache.commons.io/external/commons-io-1.4-notice.txt
rename to platform/o.apache.commons.io/external/commons-io-2.6-notice.txt
index f9e09a5..a6441be 100644
--- a/platform/o.apache.commons.io/external/commons-io-1.4-notice.txt
+++ b/platform/o.apache.commons.io/external/commons-io-2.6-notice.txt
@@ -1,5 +1,5 @@
 Apache Commons IO
-Copyright 2001-2008 The Apache Software Foundation
+Copyright 2001-2019 The Apache Software Foundation
 
 This product includes software developed by
 The Apache Software Foundation (http://www.apache.org/).
diff --git a/platform/o.apache.commons.io/manifest.mf 
b/platform/o.apache.commons.io/manifest.mf
index 920250e..2e60b50 100644
--- a/platform/o.apache.commons.io/manifest.mf
+++ b/platform/o.apache.commons.io/manifest.mf
@@ -1 +1,2 @@
 OpenIDE-Module: org.apache.commons.io
+OpenIDE-Module-Specification-Version: 2.6
\ No newline at end of file
diff --git a/platform/o.apache.commons.io/nbproject/project.properties 
b/platform/o.apache.commons.io/nbproject/project.properties
index 634b86a..544f78b 100644
--- a/platform/o.apache.commons.io/nbproject/project.properties
+++ b/platform/o.apache.commons.io/nbproject/project.properties
@@ -14,6 +14,8 @@
 # KIND, either express or implied.  See the License for the
 # specific language governing permissions and limitations
 # under the License.
-release.external/commons-io-1.4.jar=modules/org-apache-commons-io.jar
+javac.compilerargs=-Xlint -Xlint:-serial
+javac.source=1.8
+release.external/commons-io-2.6.jar=modules/org-apache-commons-io.jar
 is.autoload=true
 nbm.module.author=Tomas Stupka
diff --git a/platform/o.apache.commons.io/nbproject/project.xml 
b/platform/o.apache.commons.io/nbproject/project.xml
index 9687b1a..b5aa45d 100644
--- a/platform/o.apache.commons.io/nbproject/project.xml
+++ b/platform/o.apache.commons.io/nbproject/project.xml
@@ -44,7 +44,7 @@
 
 
 
org-apache-commons-io.jar
-external/commons-io-1.4.jar
+external/commons-io-2.6.jar
 
 
 


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

[jira] [Updated] (NETBEANS-3592) Fix various Windows LAF bugs on HiDPI screens

2019-12-15 Thread Eirik Bakke (Jira)


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

Eirik Bakke updated NETBEANS-3592:
--
Description: 
Provide workarounds to various bugs that caused the Windows LAF to be unusable 
on many HiDPI configurations, typically when an external monitor (or projector) 
is involved, or is disconnected or connected.

1) In certain configurations, the GUI font size would be either way too large 
or way too small. (I can't remember exactly which configurations caused this, 
but going through the manual test case list below _will_ trigger it several 
times.)
2) In multi-monitor configurations that involve one HiDPI screen and one 
regular screen, the size of controls drawn by the OS, such as checkboxes and 
outline expansion handles, will be incorrect unless the HiDPI screen was the 
main display at login. I earlier reported this as a JDK bug at 
https://bugs.openjdk.java.net/browse/JDK-8211715 . (Note that there are a few 
icons which cannot be fixed using the UIDefaults approach taken here, e.g. 
checkmarks in JCheckBoxMenuItem.) In some cases, the LAF would previously end 
up scaling the control images received from the OS using a poor image scaling 
interpolation; the supplied patch improves the scaling quality in these cases.
3) On non-integral scaling levels, e.g. 150%, borders around text components 
will be of uneven thickness due to rounding error. This patch fixes that. This 
also happens to JComboBox, but in that case cannot be fixed with a simple 
patch, since that one does not take its border from UIDefaults.

I will provide a PR with workarounds.

Below is a manual test plan that I used to test these patches, on Windows 10. A 
laptop and one external monitor was used for these tests. After each line in 
the test plan, the patch is confirmed to work. In _most_ of these cases there 
is some kind of improvement in behavior from the patch--either a corrected 
control/font size or at least an improvement in control icon scaling 
interpolation quality.

* main display laptop at sign-in (laptop 200%/external 100%)
* change main display to external monitor while running app
* restart app
* change 100% to 150% while running app
* restart app
* log out and in again
* change 150% to 100% while running app
* restart app
* main display external monitor at sign-in (laptop 200%/external 100%)
* change main display to laptop while running app
* restart app
* change 100% to 150% while running app
* restart app
* log out and in again
* change 150% to 100% while running app
* restart app
* change 200% to 150% while running app
* restart app
* main display laptop at sign-in (laptop 200%/external 100%), then disconnect 
external before running app
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* disconnect external while running app
* main display external monitor at sign-in (laptop 200%/external 100%), then 
disconnect external while running app
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display laptop at sign-in (laptop 200%/external 150%), then disconnect 
external before running
* reconnect external while running app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display external monitor at sign-in (laptop 200%/external 150%), then 
disconnect external before running
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display external at sign-in (laptop 150%, external 100%)
* change 100% to 150% while running app
* restart app
* change main display to laptop (200%), set external display to 100%, log out, 
disconnect external, log in, run app
* reconnect external while running app (will be 100%)
* close laptop lid (will switch to external display)


  was:
Provide workarounds to various bugs that caused the Windows LAF to be unusable 
on many HiDPI configurations, typically when an external monitor (or projector) 
is involved, or is disconnected or connected.

1) In certain configurations, the GUI font size would be either way too large 
or way too small. (I can't remember exactly which configurations caused this, 
but going through the manual test case list below _will_ trigger it several 
times.)
2) In multi-monitor configurations that involve one HiDPI screen and one 
regular screen, the size of controls drawn by the OS, such as checkboxes and 
outline expansion handles, will be incorrect unless the HiDPI screen was the 
main display at login. I earlier reported this as a JDK bug at 
https://bugs.openjdk.java.net/browse/JDK-8211715 . (Note that there are a few 
icons which cannot be fixed using the UIDefaults approach taken here, e.g. 
checkmarks in J

[jira] [Updated] (NETBEANS-3592) Fix various Windows LAF bugs on HiDPI screens

2019-12-15 Thread Eirik Bakke (Jira)


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

Eirik Bakke updated NETBEANS-3592:
--
Description: 
Provide workarounds to various bugs that caused the Windows LAF to be unusable 
on many HiDPI configurations, typically when an external monitor (or projector) 
is involved, or is disconnected or connected.

1) In certain configurations, the GUI font size would be either way too large 
or way too small. (I can't remember exactly which configurations caused this, 
but going through the manual test case list below _will_ trigger it several 
times.)
2) In multi-monitor configurations that involve one HiDPI screen and one 
regular screen, the size of controls drawn by the OS, such as checkboxes and 
outline expansion handles, will be incorrect unless the HiDPI screen was the 
main display at login. I earlier reported this as a JDK bug at 
https://bugs.openjdk.java.net/browse/JDK-8211715 . (Note that there are a few 
icons which cannot be fixed using the UIDefaults approach taken here, e.g. 
checkmarks in JCheckBoxMenuItem.) In some cases, the LAF would previously end 
up scaling the control images received from the OS using a poor image scaling 
interpolation; the supplied patch improves the scaling quality in these cases.
3) On non-integral scaling levels, e.g. 150%, borders around text components 
will be of uneven thickness due to rounding error. This patch fixes that. This 
also happens to JComboBox, but in that case cannot be fixed with a simple 
patch, since that one does not take its border from UIDefaults.

I will provide a PR with workarounds.

Below is a manual test plan that I used to test these patches, on Windows 10. 
After each line in the test plan, the patch is confirmed to work. In _most_ of 
these cases there is some kind of improvement in behavior from the 
patch--either a corrected control/font size or at least an improvement in 
control icon scaling interpolation quality.

* main display laptop at sign-in (laptop 200%/external 100%)
* change main display to external monitor while running app
* restart app
* change 100% to 150% while running app
* restart app
* log out and in again
* change 150% to 100% while running app
* restart app
* main display external monitor at sign-in (laptop 200%/external 100%)
* change main display to laptop while running app
* restart app
* change 100% to 150% while running app
* restart app
* log out and in again
* change 150% to 100% while running app
* restart app
* change 200% to 150% while running app
* restart app
* main display laptop at sign-in (laptop 200%/external 100%), then disconnect 
external before running app
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* disconnect external while running app
* main display external monitor at sign-in (laptop 200%/external 100%), then 
disconnect external while running app
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display laptop at sign-in (laptop 200%/external 150%), then disconnect 
external before running
* reconnect external while running app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display external monitor at sign-in (laptop 200%/external 150%), then 
disconnect external before running
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display external at sign-in (laptop 150%, external 100%)
* change 100% to 150% while running app
* restart app
* change main display to laptop (200%), set external display to 100%, log out, 
disconnect external, log in, run app
* reconnect external while running app (will be 100%)
* close laptop lid (will switch to external display)


  was:
Provide workarounds to various bugs that caused the Windows LAF to be unusable 
on many HiDPI configurations, typically when an external monitor (or projector) 
is involved, or is disconnected or connected.

1) In certain configurations, the GUI font size would be either way too large 
or way too small. (I can't remember exactly which configurations caused this, 
but going through the manual test case list below _will_ trigger it several 
times.)
2) In multi-monitor configurations that involve one HiDPI screen and one 
regular screen, the size of controls drawn by the OS, such as checkboxes and 
outline expansion handles, will be incorrect unless the HiDPI screen was the 
main display at login. I earlier reported this as a JDK bug at 
https://bugs.openjdk.java.net/browse/JDK-8211715 . (Note that there are a few 
icons which cannot be fixed using the UIDefaults approach taken here, e.g. 
checkmarks in JCheckBoxMenuItem.) In some cases, the LAF would previously en

[jira] [Updated] (NETBEANS-3592) Fix various Windows LAF bugs on HiDPI screens

2019-12-15 Thread Eirik Bakke (Jira)


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

Eirik Bakke updated NETBEANS-3592:
--
Description: 
Provide workarounds to various bugs that caused the Windows LAF to be unusable 
on many HiDPI configurations, typically when an external monitor (or projector) 
is involved, or is disconnected or connected.

1) In certain configurations, the GUI font size would be either way too large 
or way too small. (I can't remember exactly which configurations caused this, 
but going through the manual test case list below _will_ trigger it several 
times.)
2) In multi-monitor configurations that involve one HiDPI screen and one 
regular screen, the size of controls drawn by the OS, such as checkboxes and 
outline expansion handles, will be incorrect unless the HiDPI screen was the 
main display at login. I earlier reported this as a JDK bug at 
https://bugs.openjdk.java.net/browse/JDK-8211715 . (Note that there are a few 
icons which cannot be fixed using the UIDefaults approach taken here, e.g. 
checkmarks in JCheckBoxMenuItem.) In some cases, the LAF would previously end 
up scaling the control images received from the OS using a poor image scaling 
interpolation; the supplied patch improves the scaling quality in these cases.
3) On non-integral scaling levels, e.g. 150%, borders around text components 
will be of uneven thickness due to rounding error. This patch fixes that. This 
also happens to JComboBox, but in that case cannot be fixed with a simple 
patch, since that one does not take its border from UIDefaults.

I will provide a PR with workarounds.

Below is a manual test plan that I used to test these patches, on Windows 10. A 
laptop and one external monitor was used for these tests. After each line in 
the test plan, the patch is confirmed to work. In _most_ of these cases there 
is some kind of improvement in behavior from the patch--either a corrected 
control/font size or at least an improvement in control icon scaling 
interpolation quality.

* main display laptop at sign-in (laptop 200%/external 100%)
* change main display to external monitor while running app
* restart app
* change 100% to 150% while running app
* restart app
* log out and in again (of Windows--this makes a difference!)
* change 150% to 100% while running app
* restart app
* main display external monitor at sign-in (laptop 200%/external 100%)
* change main display to laptop while running app
* restart app
* change 100% to 150% while running app
* restart app
* log out and in again
* change 150% to 100% while running app
* restart app
* change 200% to 150% while running app
* restart app
* main display laptop at sign-in (laptop 200%/external 100%), then disconnect 
external before running app
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* disconnect external while running app
* main display external monitor at sign-in (laptop 200%/external 100%), then 
disconnect external while running app
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display laptop at sign-in (laptop 200%/external 150%), then disconnect 
external before running
* reconnect external while running app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display external monitor at sign-in (laptop 200%/external 150%), then 
disconnect external before running
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display external at sign-in (laptop 150%, external 100%)
* change 100% to 150% while running app
* restart app
* change main display to laptop (200%), set external display to 100%, log out, 
disconnect external, log in, run app
* reconnect external while running app (will be 100%)
* close laptop lid (will switch to external display)


  was:
Provide workarounds to various bugs that caused the Windows LAF to be unusable 
on many HiDPI configurations, typically when an external monitor (or projector) 
is involved, or is disconnected or connected.

1) In certain configurations, the GUI font size would be either way too large 
or way too small. (I can't remember exactly which configurations caused this, 
but going through the manual test case list below _will_ trigger it several 
times.)
2) In multi-monitor configurations that involve one HiDPI screen and one 
regular screen, the size of controls drawn by the OS, such as checkboxes and 
outline expansion handles, will be incorrect unless the HiDPI screen was the 
main display at login. I earlier reported this as a JDK bug at 
https://bugs.openjdk.java.net/browse/JDK-8211715 . (Note that there are a few 
icons which cannot be fixed using the UIDefaults app

[jira] [Updated] (NETBEANS-3592) Fix various Windows LAF bugs on HiDPI screens

2019-12-15 Thread Eirik Bakke (Jira)


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

Eirik Bakke updated NETBEANS-3592:
--
Description: 
Provide workarounds to various bugs that caused the Windows LAF to be unusable 
on many HiDPI configurations, typically when an external monitor (or projector) 
is involved, or is disconnected or connected.

1) In certain configurations, the GUI font size would be either way too large 
or way too small. (I can't remember exactly which configurations caused this, 
but going through the manual test case list below _will_ trigger it several 
times.)
2) In multi-monitor configurations that involve one HiDPI screen and one 
regular screen, the size of controls drawn by the OS, such as checkboxes and 
outline expansion handles, will be incorrect unless the HiDPI screen was the 
main display at login. I earlier reported this as a JDK bug at 
https://bugs.openjdk.java.net/browse/JDK-8211715 . (Note that there are a few 
icons which cannot be fixed using the UIDefaults approach taken here, e.g. 
checkmarks in JCheckBoxMenuItem.) In some cases, the LAF would previously end 
up scaling the control images received from the OS using a poor image scaling 
interpolation; the supplied patch improves the scaling quality in these cases.
3) On non-integral scaling levels, e.g. 150%, borders around text components 
will be of uneven thickness due to rounding error. This patch fixes that. This 
also happens to JComboBox, but in that case cannot be fixed with a simple 
patch, since that one does not take its border from UIDefaults.

I will provide a PR with workarounds.

Below is a manual test plan that I used to test these patches, on Windows 10. A 
laptop and one external monitor was used for these tests. After each line in 
the test plan, the patch is confirmed to work. In _most_ of these cases there 
is some kind of improvement in behavior from the patch--either a corrected 
control/font size or at least an improvement in control icon scaling 
interpolation quality.

* main display laptop at Windows login (laptop 200%/external 100%)
* change main display to external monitor while running app
* restart app
* change 100% to 150% while running app
* restart app
* log out and in again (of Windows--this makes a difference!)
* change 150% to 100% while running app
* restart app
* main display external monitor at login (laptop 200%/external 100%)
* change main display to laptop while running app
* restart app
* change 100% to 150% while running app
* restart app
* log out and in again
* change 150% to 100% while running app
* restart app
* change 200% to 150% while running app
* restart app
* main display laptop at login (laptop 200%/external 100%), then disconnect 
external before running app
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* disconnect external while running app
* main display external monitor at login (laptop 200%/external 100%), then 
disconnect external while running app
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display laptop at login (laptop 200%/external 150%), then disconnect 
external before running
* reconnect external while running app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display external monitor at login (laptop 200%/external 150%), then 
disconnect external before running
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display external at login (laptop 150%, external 100%)
* change 100% to 150% while running app
* restart app
* change main display to laptop (200%), set external display to 100%, log out, 
disconnect external, log in, run app
* reconnect external while running app (will be 100%)
* close laptop lid (will switch to external display)


  was:
Provide workarounds to various bugs that caused the Windows LAF to be unusable 
on many HiDPI configurations, typically when an external monitor (or projector) 
is involved, or is disconnected or connected.

1) In certain configurations, the GUI font size would be either way too large 
or way too small. (I can't remember exactly which configurations caused this, 
but going through the manual test case list below _will_ trigger it several 
times.)
2) In multi-monitor configurations that involve one HiDPI screen and one 
regular screen, the size of controls drawn by the OS, such as checkboxes and 
outline expansion handles, will be incorrect unless the HiDPI screen was the 
main display at login. I earlier reported this as a JDK bug at 
https://bugs.openjdk.java.net/browse/JDK-8211715 . (Note that there are a few 
icons which cannot be fixed using the UIDefaults approach 

[jira] [Updated] (NETBEANS-3592) Workarounds for various JDK Windows LAF bugs on HiDPI screens

2019-12-15 Thread Eirik Bakke (Jira)


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

Eirik Bakke updated NETBEANS-3592:
--
Summary: Workarounds for various JDK Windows LAF bugs on HiDPI screens  
(was: Fix various Windows LAF bugs on HiDPI screens)

> Workarounds for various JDK Windows LAF bugs on HiDPI screens
> -
>
> Key: NETBEANS-3592
> URL: https://issues.apache.org/jira/browse/NETBEANS-3592
> Project: NetBeans
>  Issue Type: Improvement
>  Components: platform - Other
>Affects Versions: 11.1
> Environment: Windows with HiDPI screens
>Reporter: Eirik Bakke
>Priority: Major
>  Labels: HiDPI, pull-request-available
> Attachments: Problem 1, incorrect font size.png, Problem 2, OS 
> controls wrong size (after patch).png, Problem 2, OS controls wrong size 
> (before patch).png, Problem 3, uneven text component borders.png, 
> WindowsSwingMultiMonitorTest.png
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Provide workarounds to various bugs that caused the Windows LAF to be 
> unusable on many HiDPI configurations, typically when an external monitor (or 
> projector) is involved, or is disconnected or connected.
> 1) In certain configurations, the GUI font size would be either way too large 
> or way too small. (I can't remember exactly which configurations caused this, 
> but going through the manual test case list below _will_ trigger it several 
> times.)
> 2) In multi-monitor configurations that involve one HiDPI screen and one 
> regular screen, the size of controls drawn by the OS, such as checkboxes and 
> outline expansion handles, will be incorrect unless the HiDPI screen was the 
> main display at login. I earlier reported this as a JDK bug at 
> https://bugs.openjdk.java.net/browse/JDK-8211715 . (Note that there are a few 
> icons which cannot be fixed using the UIDefaults approach taken here, e.g. 
> checkmarks in JCheckBoxMenuItem.) In some cases, the LAF would previously end 
> up scaling the control images received from the OS using a poor image scaling 
> interpolation; the supplied patch improves the scaling quality in these cases.
> 3) On non-integral scaling levels, e.g. 150%, borders around text components 
> will be of uneven thickness due to rounding error. This patch fixes that. 
> This also happens to JComboBox, but in that case cannot be fixed with a 
> simple patch, since that one does not take its border from UIDefaults.
> I will provide a PR with workarounds.
> Below is a manual test plan that I used to test these patches, on Windows 10. 
> A laptop and one external monitor was used for these tests. After each line 
> in the test plan, the patch is confirmed to work. In _most_ of these cases 
> there is some kind of improvement in behavior from the patch--either a 
> corrected control/font size or at least an improvement in control icon 
> scaling interpolation quality.
> * main display laptop at Windows login (laptop 200%/external 100%)
> * change main display to external monitor while running app
> * restart app
> * change 100% to 150% while running app
> * restart app
> * log out and in again (of Windows--this makes a difference!)
> * change 150% to 100% while running app
> * restart app
> * main display external monitor at login (laptop 200%/external 100%)
> * change main display to laptop while running app
> * restart app
> * change 100% to 150% while running app
> * restart app
> * log out and in again
> * change 150% to 100% while running app
> * restart app
> * change 200% to 150% while running app
> * restart app
> * main display laptop at login (laptop 200%/external 100%), then disconnect 
> external before running app
> * reconnect external while running app
> * restart app
> * log out, disconnect external, log in
> * reconnect external while running app
> * restart app
> * disconnect external while running app
> * main display external monitor at login (laptop 200%/external 100%), then 
> disconnect external while running app
> * reconnect external while running app
> * restart app
> * log out, disconnect external, log in
> * reconnect external while running app
> * restart app
> * main display laptop at login (laptop 200%/external 150%), then disconnect 
> external before running
> * reconnect external while running app
> * log out, disconnect external, log in
> * reconnect external while running app
> * restart app
> * main display external monitor at login (laptop 200%/external 150%), then 
> disconnect external before running
> * reconnect external while running app
> * restart app
> * log out, disconnect external, log in
> * reconnect external while running app
> * restart app
> * main display external at login (laptop 150%, external 100%)
> * change 100% to 150% while running app
> * restart app

[jira] [Updated] (NETBEANS-3592) Workarounds for various JDK Windows LAF bugs on HiDPI screens

2019-12-15 Thread Eirik Bakke (Jira)


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

Eirik Bakke updated NETBEANS-3592:
--
Description: 
Provide workarounds to three JDK bugs that caused the Windows LAF to be 
unusable on many HiDPI configurations, typically when an external monitor (or 
projector) is involved, or is disconnected or connected.

# In certain configurations, the GUI font size would be either way too large or 
way too small. (I can't remember exactly which configurations caused this, but 
going through the manual test case list below _will_ trigger it several times.)
# In multi-monitor configurations that involve one HiDPI screen and one regular 
screen, the size of controls drawn by the OS, such as checkboxes and outline 
expansion handles, will be incorrect unless the HiDPI screen was the main 
display at login. I earlier reported this as a JDK bug at 
https://bugs.openjdk.java.net/browse/JDK-8211715 . (Note that there are a few 
icons which cannot be fixed using the UIDefaults approach taken here, e.g. 
checkmarks in JCheckBoxMenuItem.) In some cases, the LAF would previously end 
up scaling the control images received from the OS using a poor image scaling 
interpolation; the supplied patch improves the scaling quality in these cases.
# On non-integral scaling levels, e.g. 150%, borders around text components 
will be of uneven thickness due to rounding error. This patch fixes that. This 
also happens to JComboBox, but in that case cannot be fixed with a simple 
patch, since that one does not take its border from UIDefaults.

I will provide a PR with workarounds.

Below is a manual test plan that I used to test these patches, on Windows 10. A 
laptop and one external monitor was used for these tests. After each line in 
the test plan, the patch is confirmed to work. In _most_ of these cases there 
is some kind of improvement in behavior from the patch--either a corrected 
control/font size or at least an improvement in control icon scaling 
interpolation quality.

* main display laptop at Windows login (laptop 200%/external 100%)
* change main display to external monitor while running app
* restart app
* change 100% to 150% while running app
* restart app
* log out and in again (of Windows--this makes a difference!)
* change 150% to 100% while running app
* restart app
* main display external monitor at login (laptop 200%/external 100%)
* change main display to laptop while running app
* restart app
* change 100% to 150% while running app
* restart app
* log out and in again
* change 150% to 100% while running app
* restart app
* change 200% to 150% while running app
* restart app
* main display laptop at login (laptop 200%/external 100%), then disconnect 
external before running app
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* disconnect external while running app
* main display external monitor at login (laptop 200%/external 100%), then 
disconnect external while running app
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display laptop at login (laptop 200%/external 150%), then disconnect 
external before running
* reconnect external while running app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display external monitor at login (laptop 200%/external 150%), then 
disconnect external before running
* reconnect external while running app
* restart app
* log out, disconnect external, log in
* reconnect external while running app
* restart app
* main display external at login (laptop 150%, external 100%)
* change 100% to 150% while running app
* restart app
* change main display to laptop (200%), set external display to 100%, log out, 
disconnect external, log in, run app
* reconnect external while running app (will be 100%)
* close laptop lid (will switch to external display)


  was:
Provide workarounds to various bugs that caused the Windows LAF to be unusable 
on many HiDPI configurations, typically when an external monitor (or projector) 
is involved, or is disconnected or connected.

1) In certain configurations, the GUI font size would be either way too large 
or way too small. (I can't remember exactly which configurations caused this, 
but going through the manual test case list below _will_ trigger it several 
times.)
2) In multi-monitor configurations that involve one HiDPI screen and one 
regular screen, the size of controls drawn by the OS, such as checkboxes and 
outline expansion handles, will be incorrect unless the HiDPI screen was the 
main display at login. I earlier reported this as a JDK bug at 
https://bugs.openjdk.java.net/browse/JDK-8211715 . (Note that there are a few 
icons which cannot be fixed using the UIDefaults approach ta

[jira] [Updated] (NETBEANS-3593) Make web browser icon in the toolbar take advantage of improved HiDPI scaling

2019-12-15 Thread ASF GitHub Bot (Jira)


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

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

> Make web browser icon in the toolbar take advantage of improved HiDPI scaling
> -
>
> Key: NETBEANS-3593
> URL: https://issues.apache.org/jira/browse/NETBEANS-3593
> Project: NetBeans
>  Issue Type: Improvement
>Affects Versions: 11.1
>Reporter: Eirik Bakke
>Priority: Minor
>  Labels: HiDPI, pull-request-available
> Attachments: browsericon.png
>
>
> This PR ensures that the HiDPI icon scaling improvements made in 
> NETBEANS-2614 applies to the browser icon in the toolbar. (Created a separate 
> PR for this one because it requires one API change to expose the 
> DropDownButton icon.)



--
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: [NETBEANS-3218] Add inline hint support for literals used in constructors

2019-12-15 Thread jlahoda
This is an automated email from the ASF dual-hosted git repository.

jlahoda 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 1e62ffa  [NETBEANS-3218] Add inline hint support for literals used in 
constructors
1e62ffa is described below

commit 1e62ffaf3a9b8247af9406b742d9e687c59b66c1
Author: Benjamin Graf 
AuthorDate: Tue Oct 8 20:13:42 2019 +0200

[NETBEANS-3218] Add inline hint support for literals used in constructors
---
 .../base/semantic/SemanticHighlighterBase.java | 13 +++--
 .../java/editor/base/semantic/DetectorTest.java| 64 --
 2 files changed, 45 insertions(+), 32 deletions(-)

diff --git 
a/java/java.editor.base/src/org/netbeans/modules/java/editor/base/semantic/SemanticHighlighterBase.java
 
b/java/java.editor.base/src/org/netbeans/modules/java/editor/base/semantic/SemanticHighlighterBase.java
index 224e632..46edf7d 100644
--- 
a/java/java.editor.base/src/org/netbeans/modules/java/editor/base/semantic/SemanticHighlighterBase.java
+++ 
b/java/java.editor.base/src/org/netbeans/modules/java/editor/base/semantic/SemanticHighlighterBase.java
@@ -1100,10 +1100,15 @@ public abstract class SemanticHighlighterBase extends 
JavaParserResultTask {
 }
 
 TreePath pp = getCurrentPath().getParentPath();
-if (pp.getLeaf() != null &&
-pp.getLeaf().getKind() == Kind.METHOD_INVOCATION) {
-MethodInvocationTree inv = (MethodInvocationTree) pp.getLeaf();
-int pos = inv.getArguments().indexOf(node);
+Tree leaf = pp.getLeaf();
+if (leaf != null &&
+(leaf.getKind() == Kind.METHOD_INVOCATION || leaf.getKind() == 
Kind.NEW_CLASS)) {
+int pos = -1;
+if (leaf.getKind() == Kind.METHOD_INVOCATION) {
+pos = 
MethodInvocationTree.class.cast(leaf).getArguments().indexOf(node);
+} else if (leaf.getKind() == Kind.NEW_CLASS) {
+pos = 
NewClassTree.class.cast(leaf).getArguments().indexOf(node);
+}
 if (pos != (-1)) {
 Element invoked = info.getTrees().getElement(pp);
 if (invoked != null && (invoked.getKind() == 
ElementKind.METHOD || invoked.getKind() == ElementKind.CONSTRUCTOR)) {
diff --git 
a/java/java.editor.base/test/unit/src/org/netbeans/modules/java/editor/base/semantic/DetectorTest.java
 
b/java/java.editor.base/test/unit/src/org/netbeans/modules/java/editor/base/semantic/DetectorTest.java
index 31d3937..aa09468 100644
--- 
a/java/java.editor.base/test/unit/src/org/netbeans/modules/java/editor/base/semantic/DetectorTest.java
+++ 
b/java/java.editor.base/test/unit/src/org/netbeans/modules/java/editor/base/semantic/DetectorTest.java
@@ -258,46 +258,54 @@ public class DetectorTest extends TestBase {
 performTest("Test.java",
 "package test;" +
 "public class Test {" +
+"public Test(String param) {" +
+"}" +
 "public void api(String param1, int param2, int 
param3, float param4, Object... param5) {" +
 "}" +
 "private int getValue() {" +
 "return -1;" +
 "}" +
 "private void test() {" +
+"new Test(\"\")" +
 "api(\"\", 2, getValue(), 1.0f);" +
 "api(\"\", 2, getValue(), 1.0f, null);" +
 "api(\"\", 2, getValue(), 1.0f, null, null);" +
 "}" +
 "}",
 "[PUBLIC, CLASS, DECLARATION], 0:26-0:30\n" +
-"[PUBLIC, METHOD, DECLARATION], 0:48-0:51\n" +
-"[PUBLIC, CLASS], 0:52-0:58\n" +
-"[PARAMETER, DECLARATION], 0:59-0:65\n" +
-"[PARAMETER, DECLARATION], 0:71-0:77\n" +
-"[PARAMETER, DECLARATION], 0:83-0:89\n" +
-"[PARAMETER, DECLARATION], 0:97-0:103\n" +
-"[PUBLIC, CLASS], 0:105-0:111\n" +
-"[PARAMETER, DECLARATION], 0:115-0:121\n" +
-"[PRIVATE, METHOD, DECLARATION], 0:145-0:153\n" +
-"[PRIVATE, METHOD, UNUSED, DECLARATION], 0:197-0:201\n" +
-"[PUBLIC, METHOD], 0:213-0:216\n" +
-"[param1:], 0:217-0:218\n" +
-"[param2:], 0:221-0:222\n" +
-"[PRIVATE, METHOD], 0:224-0:232\n" +
-"[param4:], 0:236-0:237\n" +
-"[PUBLIC, METHOD], 0:250-0:253\n" +
-"[param1:], 0:254-0:255\n" +
-"[param2:], 0:258-0:259\n" +
-"[PRIVATE, METHO

[jira] [Resolved] (NETBEANS-3218) Add inline hint support for literals used in constructors

2019-12-15 Thread Benjamin Graf (Jira)


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

Benjamin Graf resolved NETBEANS-3218.
-
Resolution: Fixed

> Add inline hint support for literals used in constructors
> -
>
> Key: NETBEANS-3218
> URL: https://issues.apache.org/jira/browse/NETBEANS-3218
> Project: NetBeans
>  Issue Type: Bug
>  Components: editor - Hints & Annotations
>Affects Versions: 11.1
>Reporter: Benjamin Graf
>Assignee: Benjamin Graf
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 11.3
>
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> Implementation of inline hints for literals used in constructors seams 
> actually only partly completed.



--
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-3551) Upgrade Apache Commons-IO from 1.4 to 2.6

2019-12-15 Thread Jose (Jira)


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

Jose resolved NETBEANS-3551.

Fix Version/s: 11.3
   Resolution: Implemented

Merged via PR [1745|https://github.com/apache/netbeans/pull/1745]

> Upgrade Apache Commons-IO from 1.4 to 2.6
> -
>
> Key: NETBEANS-3551
> URL: https://issues.apache.org/jira/browse/NETBEANS-3551
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Libraries
>Affects Versions: Next, 11.2
>Reporter: Jose
>Assignee: Jose
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 11.3
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Notes:
> - Requires JDK 1.7 or later
> - Compatibility with Java 9 module system
> - Many fixed bugs
> - Improved performance
> - Deprecate Charsets Charset constants in favor of Java 7's 
> java.nio.charset.StandardCharsets
> - All closeQuietly overloads in org.apache.commons.io.IOUtils have been 
> deprecated. Use the try-with-resources statement or handle suppressed 
> exceptions manually.
> - The class org.apache.commons.io.FileSystemUtils has been deprecated. Use 
> equivalent methods in java.nio.file.FileStore instead.
> [Apache Commons-IO Web Page|https://commons.apache.org/proper/commons-io/]
> [Apache Commons-IO Release 
> Notes|https://commons.apache.org/proper/commons-io/upgradeto2_6.html]



--
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-3586) Same module name when created, breaks things. Showing null pointer exception on screen.

2019-12-15 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot updated NETBEANS-3586:
-
Labels: java modularization pull-request-available  (was: java 
modularization)

> Same module name when created, breaks things. Showing null pointer exception 
> on screen.
> ---
>
> Key: NETBEANS-3586
> URL: https://issues.apache.org/jira/browse/NETBEANS-3586
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Project
>Affects Versions: 11.2
> Environment: OpenJDK Runtime Environment 13.0.1+9
>Reporter: Akhilesh Singh
>Assignee: Akhilesh Singh
>Priority: Major
>  Labels: java, modularization, pull-request-available
>
> Steps to reproduce:
>  # Create modular project - Go to File->New Project->Java with ant->Java 
> Modular Project
>  # Add a new module "newmodule" & click finish
>  # Add another module of same name "newmodule" & click finish
> Actual result : A java.lang.NullPointerException exception has occurred.
> However, the system should continue working without further problems.
> Click Show Details for the stack trace
>  
> Expected result : Application should not allow to create/add another module 
> of same name if already exist.



--
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 (1e62ffa -> 6b6ce2d)

2019-12-15 Thread jlahoda
This is an automated email from the ASF dual-hosted git repository.

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


from 1e62ffa  [NETBEANS-3218] Add inline hint support for literals used in 
constructors
 add 6b6ce2d  [TRAVIS] Run LSP client tests

No new revisions were added by this update.

Summary of changes:
 .travis.yml | 1 +
 1 file changed, 1 insertion(+)


-
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