[jira] [Updated] (NETBEANS-2653) Generate toString() with StringBuilder

2019-06-08 Thread ASF GitHub Bot (JIRA)


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

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

> Generate toString() with StringBuilder
> --
>
> Key: NETBEANS-2653
> URL: https://issues.apache.org/jira/browse/NETBEANS-2653
> Project: NetBeans
>  Issue Type: Improvement
>  Components: java - Editor
>Affects Versions: 11.0
>Reporter: Junichi Yamamoto
>Assignee: Junichi Yamamoto
>Priority: Major
>  Labels: pull-request-available
>
> Currently, the following toString() is inserted using "insert code" feature:
> {code:java}
> public class NewClass {
> private final String test = "test";
> private final String test2 = "test";
> private final String test3 = "test";
> @Override
> public String toString() {
> // generate toString() with "+" operator
> return "NewClass{" + "test=" + test + ", test2=" + test2 + ", test3=" 
> + test3 + '}';
> }
> }
> {code}
> Add a check box to the panel for using StringBuilder, then insert the 
> following toString(): 
> {code:java}
> public class NewClass {
> private final String test = "test";
> private final String test2 = "test";
> private final String test3 = "test";
> @Override
> public String toString() {
> StringBuilder sb = new StringBuilder();
> sb.append("NewClass{");
> sb.append("test=").append(test);
> sb.append(", ");
> sb.append("test2=").append(test2);
> sb.append(", ");
> sb.append("test3=").append(test3);
> sb.append('}');
> return sb.toString();
> }
> }
> {code}



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

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

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



[jira] [Created] (NETBEANS-2653) Generate toString() with StringBuilder

2019-06-08 Thread Junichi Yamamoto (JIRA)
Junichi Yamamoto created NETBEANS-2653:
--

 Summary: Generate toString() with StringBuilder
 Key: NETBEANS-2653
 URL: https://issues.apache.org/jira/browse/NETBEANS-2653
 Project: NetBeans
  Issue Type: Improvement
  Components: java - Editor
Affects Versions: 11.0
Reporter: Junichi Yamamoto
Assignee: Junichi Yamamoto


Currently, the following toString() is inserted using "insert code" feature:
{code:java}
public class NewClass {
private final String test = "test";
private final String test2 = "test";
private final String test3 = "test";

@Override
public String toString() {
// generate toString() with "+" operator
return "NewClass{" + "test=" + test + ", test2=" + test2 + ", test3=" + 
test3 + '}';
}

}
{code}

Add a check box to the panel for using StringBuilder, then insert the following 
toString(): 
{code:java}
public class NewClass {
private final String test = "test";
private final String test2 = "test";
private final String test3 = "test";

@Override
public String toString() {
StringBuilder sb = new StringBuilder();
sb.append("NewClass{");
sb.append("test=").append(test);
sb.append(", ");
sb.append("test2=").append(test2);
sb.append(", ");
sb.append("test3=").append(test3);
sb.append('}');
return sb.toString();
}

}
{code}




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

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

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



[netbeans] branch master updated: Ensure the NBMs can be signed even if the sources are checked out in a directory with spaces in its name.

2019-06-08 Thread jtulach
This is an automated email from the ASF dual-hosted git repository.

jtulach 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 bdc4af3  Ensure the NBMs can be signed even if the sources are checked 
out in a directory with spaces in its name.
 new 3b41f3d  Merge pull request #1287 from jlahoda/build-in-dir-with-space
bdc4af3 is described below

commit bdc4af3b427575379b91dd316afa8df1ac0f673f
Author: Jan Lahoda 
AuthorDate: Sat Jun 8 08:18:49 2019 +0200

Ensure the NBMs can be signed even if the sources are checked out in a 
directory with spaces in its name.
---
 nb/updatecenters/build.xml | 15 ++-
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/nb/updatecenters/build.xml b/nb/updatecenters/build.xml
index 75a5185..5145b3d 100644
--- a/nb/updatecenters/build.xml
+++ b/nb/updatecenters/build.xml
@@ -43,18 +43,23 @@
   
   
   
-  
+  
+  
   
-  
-  
+  
+  
+  
+  
   
   
   
   
   
-  
+  
+  
   
-  
+  
+  
   
   
   


-
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-2415) Bring back support for WildFly server

2019-06-08 Thread JIRA


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

Dominik Derwiński commented on NETBEANS-2415:
-

Isn't that one for 8.0, even older than the version included in 8.2?

> Bring back support for WildFly server
> -
>
> Key: NETBEANS-2415
> URL: https://issues.apache.org/jira/browse/NETBEANS-2415
> Project: NetBeans
>  Issue Type: Wish
>  Components: serverplugins - WildFly
>Affects Versions: 11.0
> Environment: n.a.
>Reporter: Dominik Derwiński
>Priority: Minor
>
> NetBeans 8.2 had WildFly server module, which helped greatly in debugging 
> Java EE applications directly from IDE. NetBeans 11.0 does not contain this 
> module, despite boasting to be the first version of Apache NetBeans to offer 
> full support for developing Java EE applications.
> I don't think it would be very hard to bring back WildFly server module 
> (currently it does not complile), because copying files of the module from 
> NetBeans 8.2 into NetBeans 11.0 installation, and recreating userdir is 
> enough to bring back that functionality (so the old module still works, but 
> for how long?).
> The files I have copied (after removing references to localization files) are:
>  * enterprise/config/Modules/org-netbeans-modules-javaee-wildfly.xml
>  * enterprise/modules/org-netbeans-modules-javaee-wildfly.jar
>  * enterprise/update_tracking/org-netbeans-modules-javaee-wildfly.xml
>  



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

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

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



[jira] [Comment Edited] (NETBEANS-2638) NullPointerException within GradleBaseProjectBuilder

2019-06-08 Thread Lou Hamersly (JIRA)


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

Lou Hamersly edited comment on NETBEANS-2638 at 6/8/19 5:23 PM:


I don't _think_ this is really Android related, it just happens to be an 
Android project. Under the main project (/jmonkeyengine), I believe you can do 
the following to reproduce: 

1) Set buildAndroidExamples = true in the root project's gradle.properties file:
 # specify if SDK and Native libraries get built
 buildNativeProjects = false
 *buildAndroidExamples = true*

2) Set a valid Android SDK path in the *local.properties* file located in the 
root project folder. (I don't do Android so this was a sidetrack to get, but if 
you already have it...) 

3) As shown in the issue above, I increased the SDK version to 27 from 23 so 
the android-examples subproject starts like this: 

apply plugin: 'com.android.application'

android {
 *compileSdkVersion 27*
 *buildToolsVersion "27.0.3"*

The 3rd step may not even be necessary, I just reverted it back and I'm still 
getting the NPE. 

When starting a manual build of jme3-android examples from NB with those 
changes, I was able to reproduce this again just now. Also I'm not sure if it 
happened the first time immediately (unless I just missed it), so it might take 
a few attempts to get it to show up. But I'm definitely getting it consistently 
now on manual builds. I know I ran with stacktraces enabled a few times using 
Run Gradle->Tasks->"build" with Stack Trace set to FULL in the dropdown, so 
that may have been a trigger. 

Note: I had moved on to other things since reporting this, so I had to recreate 
the conditions just now, hopefully I'm not forgetting something. 

!nb1.png!


was (Author: louhy):
Under the main project (/jmonkeyengine), I believe you can do the following to 
reproduce: 

1) Set buildAndroidExamples = true in the root project's gradle.properties file:
# specify if SDK and Native libraries get built
buildNativeProjects = false
*buildAndroidExamples = true*

2) Set a valid Android SDK path in the *local.properties* file located in the 
root project folder. (I don't do Android so this was a sidetrack to get, but if 
you already have it...) 

3) As shown in the issue above, I increased the SDK version to 27 from 23 so 
the android-examples subproject starts like this: 

apply plugin: 'com.android.application'

android {
 *compileSdkVersion 27*
 *buildToolsVersion "27.0.3"*

The 3rd step may not even be necessary, I just reverted it back and I'm still 
getting the NPE. 

When starting a manual build of jme3-android examples from NB with those 
changes, I was able to reproduce this again just now. Also I'm not sure if it 
happened the first time immediately (unless I just missed it), so it might take 
a few attempts to get it to show up. But I'm definitely getting it consistently 
now on manual builds. I know I ran with stacktraces enabled a few times using 
Run Gradle->Tasks->"build" with Stack Trace set to FULL in the dropdown, so 
that may have been a trigger. 

Note: I had moved on to other things since reporting this, so I had to recreate 
the conditions just now, hopefully I'm not forgetting something. 

!nb1.png!

> NullPointerException within GradleBaseProjectBuilder
> 
>
> Key: NETBEANS-2638
> URL: https://issues.apache.org/jira/browse/NETBEANS-2638
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
> Environment: Linux
>Reporter: Lou Hamersly
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: nb1.png
>
>
> Encountered this error reported by NetBeans 11 with Groovy/Gradle plugin 
> 1.0.1: 
> {noformat}
> java.lang.NullPointerException
>  at java.base/java.util.AbstractCollection.addAll(AbstractCollection.java:351)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.processDependencies(GradleBaseProjectBuilder.java:128)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.build(GradleBaseProjectBuilder.java:75)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder$Extractor.extract(GradleBaseProjectBuilder.java:288)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.createGradleProject(GradleProjectCache.java:432)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.loadGradleProject(GradleProjectCache.java:257)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.access$100(GradleProjectCache.java:85)
> [catch] at 
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:348)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:326)
>  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>  at 

[jira] [Commented] (NETBEANS-2638) NullPointerException within GradleBaseProjectBuilder

2019-06-08 Thread Lou Hamersly (JIRA)


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

Lou Hamersly commented on NETBEANS-2638:


Under the main project (/jmonkeyengine), I believe you can do the following to 
reproduce: 

1) Set buildAndroidExamples = true in the root project's gradle.properties file:
# specify if SDK and Native libraries get built
buildNativeProjects = false
*buildAndroidExamples = true*

2) Set a valid Android SDK path in the *local.properties* file located in the 
root project folder. (I don't do Android so this was a sidetrack to get, but if 
you already have it...) 

3) As shown in the issue above, I increased the SDK version to 27 from 23 so 
the android-examples subproject starts like this: 

apply plugin: 'com.android.application'

android {
 *compileSdkVersion 27*
 *buildToolsVersion "27.0.3"*

The 3rd step may not even be necessary, I just reverted it back and I'm still 
getting the NPE. 

When starting a manual build of jme3-android examples from NB with those 
changes, I was able to reproduce this again just now. Also I'm not sure if it 
happened the first time immediately (unless I just missed it), so it might take 
a few attempts to get it to show up. But I'm definitely getting it consistently 
now on manual builds. I know I ran with stacktraces enabled a few times using 
Run Gradle->Tasks->"build" with Stack Trace set to FULL in the dropdown, so 
that may have been a trigger. 

Note: I had moved on to other things since reporting this, so I had to recreate 
the conditions just now, hopefully I'm not forgetting something. 

!nb1.png!

> NullPointerException within GradleBaseProjectBuilder
> 
>
> Key: NETBEANS-2638
> URL: https://issues.apache.org/jira/browse/NETBEANS-2638
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
> Environment: Linux
>Reporter: Lou Hamersly
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: nb1.png
>
>
> Encountered this error reported by NetBeans 11 with Groovy/Gradle plugin 
> 1.0.1: 
> {noformat}
> java.lang.NullPointerException
>  at java.base/java.util.AbstractCollection.addAll(AbstractCollection.java:351)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.processDependencies(GradleBaseProjectBuilder.java:128)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.build(GradleBaseProjectBuilder.java:75)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder$Extractor.extract(GradleBaseProjectBuilder.java:288)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.createGradleProject(GradleProjectCache.java:432)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.loadGradleProject(GradleProjectCache.java:257)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.access$100(GradleProjectCache.java:85)
> [catch] at 
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:348)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:326)
>  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>  at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
>  at 
> org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
>  at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
>  at 
> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033){noformat}
> This was encountered building the jme3-android-examples subproject located in 
> this repository: [https://github.com/jMonkeyEngine/jmonkeyengine] 
> Unfortunately some setup (Android SDK related) would be involved to reproduce 
> (I may be able to help test), however since this appears to be "source set" 
> related, glancing at the code I suspect it may have something to do with 
> relative paths used in the build file. Build file used for the subproject is 
> below. 
> (Note  - the version number on the 4th/5th line was changed from 23 to 27 
> from the repo's version to bypass a compile issue. This NPE was encountered 
> with the below build file.)
>  
> {code:java}
> apply plugin: 'com.android.application'
> android {
>  compileSdkVersion 27
>  buildToolsVersion "27.0.3"
> lintOptions {
>  // Fix nifty gui referencing "java.awt" package.
>  disable 'InvalidPackage'
>  abortOnError false
>  }
> defaultConfig {
>  applicationId "org.jmonkeyengine.jme3androidexamples"
>  minSdkVersion 15 // Android 4.0.3 ICE CREAM SANDWICH
>  targetSdkVersion 22 // Android 5.1 LOLLIPOP
>  versionCode 1
>  versionName "1.0" // TODO: from settings.gradle
>  }
> buildTypes {
>  release {
>  minifyEnabled false
>  proguardFiles getDefaultProguardFile('proguard-android.txt'), 
> 'proguard-rules.pro'
>  }
>  }
> 

[jira] [Updated] (NETBEANS-2638) NullPointerException within GradleBaseProjectBuilder

2019-06-08 Thread Lou Hamersly (JIRA)


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

Lou Hamersly updated NETBEANS-2638:
---
Attachment: nb1.png

> NullPointerException within GradleBaseProjectBuilder
> 
>
> Key: NETBEANS-2638
> URL: https://issues.apache.org/jira/browse/NETBEANS-2638
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
> Environment: Linux
>Reporter: Lou Hamersly
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: nb1.png
>
>
> Encountered this error reported by NetBeans 11 with Groovy/Gradle plugin 
> 1.0.1: 
> {noformat}
> java.lang.NullPointerException
>  at java.base/java.util.AbstractCollection.addAll(AbstractCollection.java:351)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.processDependencies(GradleBaseProjectBuilder.java:128)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.build(GradleBaseProjectBuilder.java:75)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder$Extractor.extract(GradleBaseProjectBuilder.java:288)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.createGradleProject(GradleProjectCache.java:432)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.loadGradleProject(GradleProjectCache.java:257)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.access$100(GradleProjectCache.java:85)
> [catch] at 
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:348)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:326)
>  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>  at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
>  at 
> org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
>  at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
>  at 
> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033){noformat}
> This was encountered building the jme3-android-examples subproject located in 
> this repository: [https://github.com/jMonkeyEngine/jmonkeyengine] 
> Unfortunately some setup (Android SDK related) would be involved to reproduce 
> (I may be able to help test), however since this appears to be "source set" 
> related, glancing at the code I suspect it may have something to do with 
> relative paths used in the build file. Build file used for the subproject is 
> below. 
> (Note  - the version number on the 4th/5th line was changed from 23 to 27 
> from the repo's version to bypass a compile issue. This NPE was encountered 
> with the below build file.)
>  
> {code:java}
> apply plugin: 'com.android.application'
> android {
>  compileSdkVersion 27
>  buildToolsVersion "27.0.3"
> lintOptions {
>  // Fix nifty gui referencing "java.awt" package.
>  disable 'InvalidPackage'
>  abortOnError false
>  }
> defaultConfig {
>  applicationId "org.jmonkeyengine.jme3androidexamples"
>  minSdkVersion 15 // Android 4.0.3 ICE CREAM SANDWICH
>  targetSdkVersion 22 // Android 5.1 LOLLIPOP
>  versionCode 1
>  versionName "1.0" // TODO: from settings.gradle
>  }
> buildTypes {
>  release {
>  minifyEnabled false
>  proguardFiles getDefaultProguardFile('proguard-android.txt'), 
> 'proguard-rules.pro'
>  }
>  }
> sourceSets {
>  main {
>  java {
>  srcDir 'src/main/java'
>  }
>  assets {
>  srcDir 'src/assets'
>  srcDir '../jme3-testdata/src/main/resources'
>  srcDir '../jme3-examples/src/main/resources'
>  }
>  }
>  }
> }
> dependencies {
>  compile fileTree(dir: 'libs', include: ['*.jar'])
>  testCompile 'junit:junit:4.12'
>  compile 'com.android.support:appcompat-v7:23.3.0'
> compile project(':jme3-core')
>  compile project(':jme3-android')
>  compile project(':jme3-android-native')
>  compile project(':jme3-effects')
>  compile project(':jme3-bullet')
>  compile project(':jme3-bullet-native-android')
>  compile project(':jme3-networking')
>  compile project(':jme3-niftygui')
>  compile project(':jme3-plugins')
>  compile project(':jme3-terrain')
>  compile fileTree(dir: '../jme3-examples/build/libs', include: ['*.jar'], 
> exclude: ['*sources*.*'])
> // compile project(':jme3-examples')
> }
> {code}
>  
>  



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

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

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



[jira] [Resolved] (NETBEANS-374) font is too small on high res notebook monitor

2019-06-08 Thread Eirik Bakke (JIRA)


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

Eirik Bakke resolved NETBEANS-374.
--
Resolution: Incomplete

> font is too small on high res notebook monitor
> --
>
> Key: NETBEANS-374
> URL: https://issues.apache.org/jira/browse/NETBEANS-374
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - UI
>Reporter: Peter
>Priority: Major
>  Labels: HiDPI
>
> font is too small on high res notebook monitor (e.g. macbook pro 15, 
> 2880x1800). Even i tuned to enlarge the font, all other things : menu, button 
> are just too small



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

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

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



[jira] [Commented] (NETBEANS-374) font is too small on high res notebook monitor

2019-06-08 Thread Eirik Bakke (JIRA)


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

Eirik Bakke commented on NETBEANS-374:
--

OK, I see the reporter said it was a MacBook Pro. I suspect something was wrong 
with the DPI settings, perhaps an old Java version was used? If the issue 
persists on the most recent NetBeans and Java versions, feel free to open a new 
issue with more information (including OS version, NetBeans version, and Java 
version).

> font is too small on high res notebook monitor
> --
>
> Key: NETBEANS-374
> URL: https://issues.apache.org/jira/browse/NETBEANS-374
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - UI
>Reporter: Peter
>Priority: Major
>  Labels: HiDPI
>
> font is too small on high res notebook monitor (e.g. macbook pro 15, 
> 2880x1800). Even i tuned to enlarge the font, all other things : menu, button 
> are just too small



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

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

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



[jira] [Updated] (NETBEANS-374) font is too small on high res notebook monitor

2019-06-08 Thread Eirik Bakke (JIRA)


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

Eirik Bakke updated NETBEANS-374:
-
Labels: HiDPI  (was: )

> font is too small on high res notebook monitor
> --
>
> Key: NETBEANS-374
> URL: https://issues.apache.org/jira/browse/NETBEANS-374
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - UI
>Reporter: Peter
>Priority: Major
>  Labels: HiDPI
>
> font is too small on high res notebook monitor (e.g. macbook pro 15, 
> 2880x1800). Even i tuned to enlarge the font, all other things : menu, button 
> are just too small



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

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

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



[jira] [Resolved] (NETBEANS-2622) gradle project seams always taken the default JDK

2019-06-08 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi resolved NETBEANS-2622.
---
   Resolution: Fixed
Fix Version/s: Next

It seems to be resolved by NETBEANS-2004.

> gradle project seams always taken the default JDK
> -
>
> Key: NETBEANS-2622
> URL: https://issues.apache.org/jira/browse/NETBEANS-2622
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0
>Reporter: Andreas Eberhöfer
>Assignee: Laszlo Kishalmi
>Priority: Minor
> Fix For: Next
>
> Attachments: JDKTest.tar.gz, netbeans_jdk.png
>
>
> Hi,
> I start netbeans with JDK 10, set in the `etc/netbeans.conf` the jdkhome 
> path. Now I create a new gradle project and set in the `build.gradle` 
> ```
> sourceCompatibility = 11
> targetCompatibility = 11
> ```
> In my code I use a JDK 11 API like
> ```
> Path p = Path.of(".");
> ```
> This won't compile. 
> I added a JDK 11 to netbeans and change under 
> `Properies->Build->Compile->Java Platform` to JDK 11. It still does not 
> compile. 
> After a restart, it still does not compile.
>  I changed the jdkhome in `etc/netbeans.conf` to the JDK 11. After a restart 
> it compiles. 
> Not a big deal, but maybe you should have a look at it. To me it seams like 
> gradle project always takes the default JDK.



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

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

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



[jira] [Commented] (NETBEANS-2622) gradle project seams always taken the default JDK

2019-06-08 Thread JIRA


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

Andreas Eberhöfer commented on NETBEANS-2622:
-

It is working now, thanks

> gradle project seams always taken the default JDK
> -
>
> Key: NETBEANS-2622
> URL: https://issues.apache.org/jira/browse/NETBEANS-2622
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0
>Reporter: Andreas Eberhöfer
>Assignee: Laszlo Kishalmi
>Priority: Minor
> Attachments: JDKTest.tar.gz, netbeans_jdk.png
>
>
> Hi,
> I start netbeans with JDK 10, set in the `etc/netbeans.conf` the jdkhome 
> path. Now I create a new gradle project and set in the `build.gradle` 
> ```
> sourceCompatibility = 11
> targetCompatibility = 11
> ```
> In my code I use a JDK 11 API like
> ```
> Path p = Path.of(".");
> ```
> This won't compile. 
> I added a JDK 11 to netbeans and change under 
> `Properies->Build->Compile->Java Platform` to JDK 11. It still does not 
> compile. 
> After a restart, it still does not compile.
>  I changed the jdkhome in `etc/netbeans.conf` to the JDK 11. After a restart 
> it compiles. 
> Not a big deal, but maybe you should have a look at it. To me it seams like 
> gradle project always takes the default JDK.



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

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

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