[jira] [Closed] (NETBEANS-1958) Wrong netbeans-vm yaml configuration file

2019-04-23 Thread Antonio Vieiro (JIRA)


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

Antonio Vieiro closed NETBEANS-1958.

Resolution: Fixed

This issue was closed long ago after chatting with ASF Infra.

> Wrong netbeans-vm yaml configuration file
> -
>
> Key: NETBEANS-1958
> URL: https://issues.apache.org/jira/browse/NETBEANS-1958
> Project: NetBeans
>  Issue Type: Bug
>Reporter: Antonio Vieiro
>Assignee: Antonio Vieiro
>Priority: Major
>
> The file at 
> [https://github.com/vieiro/infrastructure-puppet/blob/deployment/data/nodes/netbeans-vm.apache.org.yaml]
>  does not properly quote "%", so redirections are lost.
> We should look for other similar yaml files in the directory and properly 
> quote "%" there.



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



[incubator-netbeans-html4j] branch master updated: Logging to indentify root cause of the random failures

2019-04-23 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/incubator-netbeans-html4j.git


The following commit(s) were added to refs/heads/master by this push:
 new 39d23f1  Logging to indentify root cause of the random failures
39d23f1 is described below

commit 39d23f1e9590826d8a240c525dce339a35928b79
Author: Jaroslav Tulach 
AuthorDate: Wed Apr 24 05:17:52 2019 +0200

Logging to indentify root cause of the random failures
---
 .../org/netbeans/html/ko4j/DoubleViewTest.java | 102 +++--
 1 file changed, 54 insertions(+), 48 deletions(-)

diff --git a/ko4j/src/test/java/org/netbeans/html/ko4j/DoubleViewTest.java 
b/ko4j/src/test/java/org/netbeans/html/ko4j/DoubleViewTest.java
index 83a48ed..d2ed578 100644
--- a/ko4j/src/test/java/org/netbeans/html/ko4j/DoubleViewTest.java
+++ b/ko4j/src/test/java/org/netbeans/html/ko4j/DoubleViewTest.java
@@ -45,8 +45,10 @@ public class DoubleViewTest {
 
 @Function
 static void change(DoubleView model) {
+log("changing ").append(model).append(" to ").append(set);
 assertNotNull(set);
 model.setMessage(set);
+log("changing done");
 set = null;
 }
 
@@ -54,18 +56,19 @@ public class DoubleViewTest {
 private WebView view1;
 private WebView view2;
 
+private static final StringBuffer LOG = new StringBuffer();
+
 @BeforeMethod
 public void initializeViews() throws Exception {
+LOG.setLength(0);
+
 final JFXPanel panel = new JFXPanel();
 final JFXPanel p2 = new JFXPanel();
 
 final CountDownLatch initViews = new CountDownLatch(1);
-Platform.runLater(new Runnable() {
-@Override
-public void run() {
-displayFrame(panel, p2);
-initViews.countDown();
-}
+Platform.runLater(() -> {
+displayFrame(panel, p2);
+initViews.countDown();
 });
 initViews.await();
 
@@ -79,28 +82,22 @@ public class DoubleViewTest {
 
 final CountDownLatch view1Init = new CountDownLatch(1);
 final CountDownLatch view2Init = new CountDownLatch(1);
-Platform.runLater(new Runnable() {
-@Override
-public void run() {
-FXBrowsers.load(view1, page, new Runnable() {
-@Override
-public void run() {
-doubleView.applyBindings();
-view1Init.countDown();
-}
-});
-
-FXBrowsers.load(view2, page, new Runnable() {
-@Override
-public void run() {
-doubleView.applyBindings();
-view2Init.countDown();
-}
-});
-}
+Platform.runLater(() -> {
+FXBrowsers.load(view1, page, () -> {
+doubleView.applyBindings();
+log("applyBindings view One");
+view1Init.countDown();
+});
+
+FXBrowsers.load(view2, page, () -> {
+doubleView.applyBindings();
+log("applyBindings view Two");
+view2Init.countDown();
+});
 });
 view1Init.await();
 view2Init.await();
+log("initializeViews - done");
 }
 
 private void displayFrame(JFXPanel panel, JFXPanel p2) {
@@ -128,30 +125,28 @@ public class DoubleViewTest {
 public void synchronizationOfViews() throws Throwable {
 final CountDownLatch cdl = new CountDownLatch(1);
 final Throwable[] arr = new Throwable[1];
-Platform.runLater(new Runnable() {
-@Override
-public void run() {
-try {
-assertMessages("In view one", view1, "Initialized");
-assertMessages("In view two", view2, "Initialized");
-set = "Change1";
-clickButton(view1);
-assertMessages("In view one", view1, "Change1");
-assertMessages("In view two", view2, "Change1");
-set = "Change2";
-clickButton(view2);
-assertMessages("In view one", view1, "Change2");
-assertMessages("In view two", view2, "Change2");
-} catch (Throwable t) {
-arr[0] = t;
-} finally {
-cdl.countDown();
-}
+Platform.runLater(() -> {
+try {
+assertMessages("In view one", view1, "Initialized");
+assertMessages("In view two", view2, "Initialized");
+set = "Change1";
+clickButton("View one", view1);
+assertMessages("In view one", view1, "Change1");
+

[jira] [Created] (NETBEANS-2456) Maven web project opening error - Grovy plugin don't auto activate.

2019-04-23 Thread Helder (JIRA)
Helder created NETBEANS-2456:


 Summary: Maven web project opening error - Grovy plugin don't auto 
activate.
 Key: NETBEANS-2456
 URL: https://issues.apache.org/jira/browse/NETBEANS-2456
 Project: NetBeans
  Issue Type: Bug
Reporter: Helder
 Attachments: ide-log.txt

When opening a maven web project, that uses jpa, an error occurs.
Apparently, activating the plugin manually solves the problem.



--
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-2409) Very Slow Operations on Windows

2019-04-23 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi commented on NETBEANS-2409:
---

Thanks Scott!

[~rtaneja] could we produce a properly signed installer for windows to test?

> Very Slow  Operations on Windows
> 
>
> Key: NETBEANS-2409
> URL: https://issues.apache.org/jira/browse/NETBEANS-2409
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 10.0, 11.0
> Environment: Windows
>Reporter: Laszlo Kishalmi
>Priority: Critical
>  Labels: Performance, Windows, pull-request-available
> Attachments: NB11_autocomplete.nps, NB11_getHint.nps, 
> WinFilesystemSlow.png
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> What is the best course of action for reporting slowness?  I can’t share my 
> project.
> I’m not certain how to give step-by-step instructions when the problem is 
> basically one step in most cases.  E.g. invoke auto-complete - nothing 
> happens for several seconds.  Invoke rename - dialog doesn’t appear for 
> several seconds.  Find usages - extremely slow > 5 second delay on a private 
> member of a class less than 100 lines.
> In general it seems NB 11 is noticeably slower than NB 8.2. Not good 
> considering slowness was already my #1 complaint about NB 8.2.  I have so far 
> found the benefits of NB outweigh the fact that it is much slower than other 
> IDEs for the same operations, but the slowness of NB 11 is tipping the scale. 
>  I don’t want to switch IDEs, pease don’t interpret this as some sort of 
> threat to do so. I would like to help find the issues in NB.  But I don’t 
> have the bandwidth to debug NB and not being about to share my project makes 
> it difficult to provide helpful reports :-(
> Are others seeing the slowness?
> Find usages, renames, call-hierarchy, auto-complete… things I use all the 
> time, I often have to wait 5 to 10 seconds for a response from the IDE, 
> sometimes more.
> I’ve already deleted user dir and cache and restarted. 
> I’m using Gradle-based Java projects, running NB 11.0 with JDK 8u202.



--
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-2455) Splash screens for development version

2019-04-23 Thread Junichi Yamamoto (JIRA)
Junichi Yamamoto created NETBEANS-2455:
--

 Summary: Splash screens for development version
 Key: NETBEANS-2455
 URL: https://issues.apache.org/jira/browse/NETBEANS-2455
 Project: NetBeans
  Issue Type: Bug
  Components: ide - UI
Reporter: Junichi Yamamoto


Currently, the version of the splash screen is 10 in the master branch. So we 
should fix it (e.g. Dev., Development Version, ...).



--
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-2454) Host module StandardModule:org.netbeans.libs.javacimpl jarFile: C:\Programs\netbeans\java\modules\org-netbeans-libs-javacimpl.jar was enabled before, will not accept f

2019-04-23 Thread Opher Shachar (JIRA)


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

Opher Shachar updated NETBEANS-2454:

Attachment: log.zip

> Host module StandardModule:org.netbeans.libs.javacimpl jarFile: 
> C:\Programs\netbeans\java\modules\org-netbeans-libs-javacimpl.jar was enabled 
> before, will not accept fragment
> --
>
> Key: NETBEANS-2454
> URL: https://issues.apache.org/jira/browse/NETBEANS-2454
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.0
> Environment: Windows 10 64 bit
> JDK 11
> Netbeans 11.0
>Reporter: Opher Shachar
>Priority: Major
> Attachments: log.zip
>
>
> # Just installed version 11.0 on Windows 10 by extracting the zip file.
>  # Launched for the first time.
>  # In Plugins marked the 8.2 repository.
>  # Initiated an Update, then restarted.
>  # Installed nb-javac when prompted.
>  # Noticed the message about this exception.
>  



--
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-2454) Host module StandardModule:org.netbeans.libs.javacimpl jarFile: C:\Programs\netbeans\java\modules\org-netbeans-libs-javacimpl.jar was enabled before, will not accept f

2019-04-23 Thread Opher Shachar (JIRA)
Opher Shachar created NETBEANS-2454:
---

 Summary: Host module StandardModule:org.netbeans.libs.javacimpl 
jarFile: C:\Programs\netbeans\java\modules\org-netbeans-libs-javacimpl.jar was 
enabled before, will not accept fragment
 Key: NETBEANS-2454
 URL: https://issues.apache.org/jira/browse/NETBEANS-2454
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 11.0
 Environment: Windows 10 64 bit
JDK 11
Netbeans 11.0
Reporter: Opher Shachar
 Attachments: log.zip

# Just installed version 11.0 on Windows 10 by extracting the zip file.
 # Launched for the first time.
 # In Plugins marked the 8.2 repository.
 # Initiated an Update, then restarted.
 # Installed nb-javac when prompted.
 # Noticed the message about this exception.

 



--
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-2407) Gradle project: Configurations doesn't distinguish dependencies with classifier

2019-04-23 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi commented on NETBEANS-2407:
---

Hmm. This seems to be a nasty one. Gradle does not provide Classifier in module 
dependencies.

> Gradle project: Configurations doesn't distinguish dependencies with 
> classifier
> ---
>
> Key: NETBEANS-2407
> URL: https://issues.apache.org/jira/browse/NETBEANS-2407
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.0
>Reporter: Jose Pereda
>Assignee: Laszlo Kishalmi
>Priority: Minor
>
> For instance, adding a JavaFX project like this one: 
> [https://github.com/openjfx/samples/blob/master/IDE/NetBeans/Non-Modular/Gradle/hellofx]
> There are dependencies:
>  - org.openjfx:javafx-base:12
>  - org.openjfx:javafx-base:12:mac
>  - org.openjfx:javafx-graphics:12
>  - org.openjfx:javafx-graphics:12:mac...
>  
> Under the Project -> Configurations -> CompileClasspath you only see the 
> artifacts:
>  - javafx-base:12
>  - javafx-graphics:12...
>  and if you expand them or if you hover them and see the tooltip), randomly 
> some of them are the ones with classifier, the others not.
>  
> Note that the project works fine, build/run tasks work as expected, so all 
> dependencies are resolved fine.
> Expected: I'd expect to see all artifacts, including those with classifier.
>  
> Also the tooltip shows you the file location in your local repository, but 
> then there is no way to right click and open the file's properties to copy 
> that location.
>  
> Expected: I'd expect to be able to find the file in the local repository.
>  
> Version: NetBeans 11.0
> Mac OS X 10.14.4
>  



--
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-1858) Apply Code Changes not working

2019-04-23 Thread Klaus Rheinwald (JIRA)


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

Klaus Rheinwald commented on NETBEANS-1858:
---

The problem could be Ant:

My original (ant-based) project was used until recently in NB 8.2. After 
upgrading to NB 10 (and now 11) running on openJDK 11 and the project using JDK 
8, ‘Apply Code Changes’ stopped being enabled after editing and saving a source 
file when the debugee was stopped.

To recreate, I created a Java Ant Application (as the original project), added 
System.out.println("Hello World"); to main(), put a breakpoint on that line, 
started debug, changed that line and saved, ‘Apply Code Changes’ is still 
disabled. ‘Compile on Save’ is enabled in the Project Preferences, ‘Apply Code 
Changes on Compile on Save’ in the general settings does not have an impact, 
neither does switching to JDK 8 for NB.

 

> Apply Code Changes not working
> --
>
> Key: NETBEANS-1858
> URL: https://issues.apache.org/jira/browse/NETBEANS-1858
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 10.0
>Reporter: Tomasz Kubik
>Priority: Major
> Fix For: Next
>
>
> Button "Apply Code Changes" is always disabled.



--
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-2453) A java.lang.NullPointerException exception has occurred.

2019-04-23 Thread Guilherme Maitan Teixeira (JIRA)
Guilherme Maitan Teixeira created NETBEANS-2453:
---

 Summary: A java.lang.NullPointerException exception has occurred.
 Key: NETBEANS-2453
 URL: https://issues.apache.org/jira/browse/NETBEANS-2453
 Project: NetBeans
  Issue Type: Bug
  Components: debugger - Java
Affects Versions: 11.0
Reporter: Guilherme Maitan Teixeira


A java.lang.NullPointerException exception has occurred.
Please report this at https://issues.apache.org/jira/projects/NETBEANS/issues,
including a copy of your messages.log file as an attachment.
The messages.log file is located in your 
C:\Users\guimg\AppData\Roaming\NetBeans\11.0\var\log folder

 

--
h3. You have found a bug in the application!

Please help Apache NetBeans by reporting this problem to our bug tracking 
system. Click _View Data_ button, copy the exception and submit it together 
with detailed information about what you were trying to achieve before the 
problem occurred in 
[JIRA|https://issues.apache.org/jira/projects/NETBEANS/issues].

Thank you for helping us make Apache NetBeans better

 



 

---
>Log Session: Tuesday, April 23, 2019 at 10:29:07 AM Brasilia Standard Time
>System Info: 
 Product Version = Apache NetBeans IDE 11.0 (Build 
incubator-netbeans-release-404-on-20190319)
 Operating System = Windows 10 version 10.0 running on amd64
 Java; VM; Vendor = 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11; Oracle 
Corporation
 Runtime = Java(TM) SE Runtime Environment 9.0.1+11
 Java Home = C:\Desenv\Java\jdk-9.0.1
 System Locale; Encoding = en_US (nb); Cp1252
 Home Directory = C:\Users\guimg
 Current Directory = Z:\desenv\Program files\Netbeans\Netbeans 11.0\bin
 User Directory = C:\Users\guimg\AppData\Roaming\NetBeans\11.0
 Cache Directory = C:\Users\guimg\AppData\Local\NetBeans\Cache\11.0
 Installation = Z:\desenv\Program files\Netbeans\Netbeans 11.0\nb
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\ergonomics
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\ide
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\extide
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\java
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\apisupport
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\webcommon
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\websvccommon
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\enterprise
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\profiler
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\php
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\harness
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\groovy
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\javafx
 Z:\desenv\Program files\Netbeans\Netbeans 11.0\platform
 Boot & Ext. Classpath = 
 Application Classpath = Z:\desenv\Program files\Netbeans\Netbeans 
11.0\platform\lib\boot.jar;Z:\desenv\Program files\Netbeans\Netbeans 
11.0\platform\lib\org-openide-modules.jar;Z:\desenv\Program 
files\Netbeans\Netbeans 
11.0\platform\lib\org-openide-util-lookup.jar;Z:\desenv\Program 
files\Netbeans\Netbeans 
11.0\platform\lib\org-openide-util-ui.jar;Z:\desenv\Program 
files\Netbeans\Netbeans 11.0\platform\lib\org-openide-util.jar
 Startup Classpath = Z:\desenv\Program files\Netbeans\Netbeans 
11.0\platform\core\asm-all-5.0.1.jar;Z:\desenv\Program files\Netbeans\Netbeans 
11.0\platform\core\core-base.jar;Z:\desenv\Program files\Netbeans\Netbeans 
11.0\platform\core\core.jar;Z:\desenv\Program files\Netbeans\Netbeans 
11.0\platform\core\org-netbeans-libs-asm.jar;Z:\desenv\Program 
files\Netbeans\Netbeans 
11.0\platform\core\org-openide-filesystems-compat8.jar;Z:\desenv\Program 
files\Netbeans\Netbeans 
11.0\platform\core\org-openide-filesystems.jar;Z:\desenv\Program 
files\Netbeans\Netbeans 
11.0\nb\core\org-netbeans-upgrader.jar;Z:\desenv\Program 
files\Netbeans\Netbeans 11.0\nb\core\locale\core_nb.jar
---
INFO [org.netbeans.modules.netbinox]: Install area set to 
file:/Z:/desenv/Program files/Netbeans/Netbeans 11.0/
WARNING [org.netbeans.core.modules]: the modules 
[org.netbeans.modules.xml.text] use 
org.netbeans.modules.editor.deprecated.pre65formatting which is deprecated.
WARNING [org.netbeans.core.modules]: the modules [org.netbeans.modules.ide.kit, 
org.netbeans.modules.xml.text] use org.netbeans.modules.editor.structure which 
is deprecated.
WARNING [org.openide.filesystems.Ordering]: Not all children in 
Services/MIMEResolver/ marked with the position attribute: 
[org-netbeans-modules-gradle-GradleDataObject-Extension.xml], but some are: 
[org-openide-loaders-DataLoaderPool$InstanceLoaderSystem-Extension.xml, 
org-netbeans-core-startup-layers-SystemFileSystem-Extension.xml, 
org-netbeans-modules-java-JavaDataObject-Extension.xml, 

[jira] [Commented] (NETBEANS-1858) Apply Code Changes not working

2019-04-23 Thread Eirik Bakke (JIRA)


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

Eirik Bakke commented on NETBEANS-1858:
---

Works for me on NetBeans 11 with the IDE running on Java 11.0.1 and a 
Maven-based Java project running Java 9.0.7.1, on Windows 10.

> Apply Code Changes not working
> --
>
> Key: NETBEANS-1858
> URL: https://issues.apache.org/jira/browse/NETBEANS-1858
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 10.0
>Reporter: Tomasz Kubik
>Priority: Major
> Fix For: Next
>
>
> Button "Apply Code Changes" is always disabled.



--
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-2409) Very Slow Operations on Windows

2019-04-23 Thread Scott Palmer (JIRA)


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

Scott Palmer edited comment on NETBEANS-2409 at 4/23/19 1:41 PM:
-

[~lkishalmi] that installer does not appear to be signed by a trusted source.  
When I attempted to open it Windows Defender warned me:

 
 Windows protected your PC
 Windows Defender SmartScreen prevented an unrecognized app from starting. 
Running this app might put your PC at risk.
|App:|Apache-NetBeans-11.0-bin-windows-x64.exe|
|Publisher: |Unknown publisher|


was (Author: swpalmer):
[~lkishalmi] that installer does not appear to be signed by a trusted source.  
When I attempted to open it Windows Defender warned me:

 
Windows protected your PC
Windows Defender SmartScreen prevented an unrecognized app from starting. 
Running this app might put your PC at risk.
[More info|about:blank#]

> Very Slow  Operations on Windows
> 
>
> Key: NETBEANS-2409
> URL: https://issues.apache.org/jira/browse/NETBEANS-2409
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 10.0, 11.0
> Environment: Windows
>Reporter: Laszlo Kishalmi
>Priority: Critical
>  Labels: Performance, Windows, pull-request-available
> Attachments: NB11_autocomplete.nps, NB11_getHint.nps, 
> WinFilesystemSlow.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> What is the best course of action for reporting slowness?  I can’t share my 
> project.
> I’m not certain how to give step-by-step instructions when the problem is 
> basically one step in most cases.  E.g. invoke auto-complete - nothing 
> happens for several seconds.  Invoke rename - dialog doesn’t appear for 
> several seconds.  Find usages - extremely slow > 5 second delay on a private 
> member of a class less than 100 lines.
> In general it seems NB 11 is noticeably slower than NB 8.2. Not good 
> considering slowness was already my #1 complaint about NB 8.2.  I have so far 
> found the benefits of NB outweigh the fact that it is much slower than other 
> IDEs for the same operations, but the slowness of NB 11 is tipping the scale. 
>  I don’t want to switch IDEs, pease don’t interpret this as some sort of 
> threat to do so. I would like to help find the issues in NB.  But I don’t 
> have the bandwidth to debug NB and not being about to share my project makes 
> it difficult to provide helpful reports :-(
> Are others seeing the slowness?
> Find usages, renames, call-hierarchy, auto-complete… things I use all the 
> time, I often have to wait 5 to 10 seconds for a response from the IDE, 
> sometimes more.
> I’ve already deleted user dir and cache and restarted. 
> I’m using Gradle-based Java projects, running NB 11.0 with JDK 8u202.



--
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-2409) Very Slow Operations on Windows

2019-04-23 Thread Scott Palmer (JIRA)


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

Scott Palmer commented on NETBEANS-2409:


[~lkishalmi] that installer does not appear to be signed by a trusted source.  
When I attempted to open it Windows Defender warned me:

 
Windows protected your PC
Windows Defender SmartScreen prevented an unrecognized app from starting. 
Running this app might put your PC at risk.
[More info|about:blank#]

> Very Slow  Operations on Windows
> 
>
> Key: NETBEANS-2409
> URL: https://issues.apache.org/jira/browse/NETBEANS-2409
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 10.0, 11.0
> Environment: Windows
>Reporter: Laszlo Kishalmi
>Priority: Critical
>  Labels: Performance, Windows, pull-request-available
> Attachments: NB11_autocomplete.nps, NB11_getHint.nps, 
> WinFilesystemSlow.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> What is the best course of action for reporting slowness?  I can’t share my 
> project.
> I’m not certain how to give step-by-step instructions when the problem is 
> basically one step in most cases.  E.g. invoke auto-complete - nothing 
> happens for several seconds.  Invoke rename - dialog doesn’t appear for 
> several seconds.  Find usages - extremely slow > 5 second delay on a private 
> member of a class less than 100 lines.
> In general it seems NB 11 is noticeably slower than NB 8.2. Not good 
> considering slowness was already my #1 complaint about NB 8.2.  I have so far 
> found the benefits of NB outweigh the fact that it is much slower than other 
> IDEs for the same operations, but the slowness of NB 11 is tipping the scale. 
>  I don’t want to switch IDEs, pease don’t interpret this as some sort of 
> threat to do so. I would like to help find the issues in NB.  But I don’t 
> have the bandwidth to debug NB and not being about to share my project makes 
> it difficult to provide helpful reports :-(
> Are others seeing the slowness?
> Find usages, renames, call-hierarchy, auto-complete… things I use all the 
> time, I often have to wait 5 to 10 seconds for a response from the IDE, 
> sometimes more.
> I’ve already deleted user dir and cache and restarted. 
> I’m using Gradle-based Java projects, running NB 11.0 with JDK 8u202.



--
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-2452) -Xbootclasspath/p is no longer a supported option

2019-04-23 Thread Emile Brinkman (JIRA)


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

Emile Brinkman updated NETBEANS-2452:
-
Component/s: java - Platform

> -Xbootclasspath/p is no longer a supported option
> -
>
> Key: NETBEANS-2452
> URL: https://issues.apache.org/jira/browse/NETBEANS-2452
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Compiler, java - Platform, projects - Ant
>Affects Versions: 9.0, 10.0, 11.0
> Environment: OpenJDK 11
>Reporter: Emile Brinkman
>Assignee: Emile Brinkman
>Priority: Major
>  Labels: patch
> Fix For: 11.0
>
>
> I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
> OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
> apparently has to be changed to --patch-module. It is however still used in 
> the ANT build-impl.xml file under endorsed.classpath.path. The problem is 
> that if you change "-Xbootclasspath/p:" to "-patch module java.base=" that 
> NetBeans automatically overwrites it back to "-Xbootclasspath/p" when you 
> change properties of a project. -Xbootclasspath/a and -Xbootclasspath also 
> don't work.
> I also get the following error when running a class even when I changed 
> everything to --patch module:
> {{-Xbootclasspath/p is no longer a supported option.}}
>  {{Error: Could not create the Java Virtual Machine.}}
>  {{Error: A fatal exception has occurred. Program will exit.}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
>  The following error occurred while executing this line:}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
>  Java returned: 1}}
>  {{BUILD FAILED (total time: 0 seconds)}}
> Removing the cache folder doesn't help. I am not able anymore to run this 
> class even when I change the Source/Binary format of the project back to 
> JDK1.8. It seems that Apache NetBeans has hardcoded -Xbootclasspath 
> internally?
>  



--
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-2451) Run main project disabled for Spring Boot applications

2019-04-23 Thread hg (JIRA)


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

hg edited comment on NETBEANS-2451 at 4/23/19 11:33 AM:


I've found a better fix... create a gradle.properties file in the root of the 
project containing the following:
{noformat}
action.debug.args=bootRun --debug-jvm
action.run.args=bootRun
{noformat}
These can also be added via the GUI. Project Properties > Build Actions

 

It'd be nice if Netbeans handled this transparently/automatically.


was (Author: hhgg):
I've found a better fix... create a gradle.properties file in the root of the 
project containing the following:
{noformat}
action.debug.args=bootRun --debug-jvm
action.run.args=bootRun
{noformat}
These can also be added via the GUI. Project Properties > Build Actions

> Run main project disabled for Spring Boot applications
> --
>
> Key: NETBEANS-2451
> URL: https://issues.apache.org/jira/browse/NETBEANS-2451
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0
>Reporter: hg
>Assignee: hg
>Priority: Major
>  Labels: Gradle
> Attachments: netbeans-run-issue.mp4
>
>
> The menu options for "Run Main Project" and "Debug Main Project" are disabled 
> for Spring Boot applications. See attached screen recording (note also that 
> the menu does not update automatically).
>  
> *Steps to reproduce:*
> 1) Generate a demo Spring Boot Gradle project here:
> [https://start.spring.io/]
> 2) Open Project in Netbeans. Menu items are disabled.
>  
> *Workarounds:*
> 1) Use the "bootRun" task as found in the Navigator panel.
> or 2) Modify build.gradle to add in the application plugin and mainClassName 
> variable. This causes NetBeans to add a "run" task and enables the menu.
>  
>  
> *Product Version:* Apache NetBeans IDE 11.0 (Build 
> incubator-netbeans-release-404-on-20190319)
> *Java:* 1.8.0_192; Java HotSpot(TM) 64-Bit Server VM 25.192-b12
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_192-b12
> *System:* Mac OS X version 10.14.4 running on x86_64; UTF-8; en_GB (nb)



--
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-2452) -Xbootclasspath/p is no longer a supported option

2019-04-23 Thread Emile Brinkman (JIRA)


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

Emile Brinkman updated NETBEANS-2452:
-
Description: 
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is however still used in the 
ANT build-impl.xml file under endorsed.classpath.path. The problem is that if 
you change "-Xbootclasspath/p:" to "-patch module java.base=" that NetBeans 
automatically overwrites it back to "-Xbootclasspath/p" when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. I am not able anymore to run this class 
even when I change the Source/Binary format of the project back to JDK1.8. It 
seems that Apache NetBeans has hardcoded -Xbootclasspath internally?

 

  was:
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is however still used in the 
ANT build-impl.xml file under endorsed.classpath.path. The problem is that if 
you change "-Xbootclasspath/p:" to "--patch module java.base=" that NetBeans 
automatically overwrites it back to "-Xbootclasspath/p" when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. I am not able anymore to run this class 
even when I change the Source/Binary format of the project back to JDK1.8. It 
seems that Apache NetBeans has hardcoded -Xbootclasspath internally?

 


> -Xbootclasspath/p is no longer a supported option
> -
>
> Key: NETBEANS-2452
> URL: https://issues.apache.org/jira/browse/NETBEANS-2452
> Project: NetBeans
>  Issue Type: Bug
>  Components: cnd - Execution
>Affects Versions: 9.0, 10.0, 11.0
> Environment: OpenJDK 11
>Reporter: Emile Brinkman
>Assignee: Emile Brinkman
>Priority: Major
>  Labels: patch
> Fix For: 11.0
>
>
> I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
> OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
> apparently has to be changed to --patch-module. It is however still used in 
> the ANT build-impl.xml file under endorsed.classpath.path. The problem is 
> that if you change "-Xbootclasspath/p:" to "-patch module java.base=" that 
> NetBeans automatically overwrites it back to "-Xbootclasspath/p" when you 
> change properties of a project. -Xbootclasspath/a and -Xbootclasspath also 
> don't work.
> I also get the following error when running a class even when I changed 
> everything to --patch module:
> {{-Xbootclasspath/p is no longer a supported option.}}
>  {{Error: Could not create the Java Virtual Machine.}}
>  {{Error: A fatal exception has occurred. Program will exit.}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
>  The following error occurred while executing this line:}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
>  Java returned: 1}}
>  {{BUILD FAILED (total time: 0 seconds)}}
> Removing the cache folder doesn't help. I am not able anymore to run this 
> class even when I change the Source/Binary format of the project back to 
> JDK1.8. It seems that Apache NetBeans has hardcoded -Xbootclasspath 
> internally?
>  



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

-
To 

[jira] [Updated] (NETBEANS-2452) -Xbootclasspath/p is no longer a supported option

2019-04-23 Thread Emile Brinkman (JIRA)


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

Emile Brinkman updated NETBEANS-2452:
-
Description: 
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is however still used in the 
ANT build-impl.xml file under endorsed.classpath.path. The problem is that if 
you change "-Xbootclasspath/p:" to "--patch module java.base=" that NetBeans 
automatically overwrites it back to "-Xbootclasspath/p" when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. I am not able anymore to run this class 
even when I change the Source/Binary format of the project back to JDK1.8. It 
seems that Apache NetBeans has hardcoded -Xbootclasspath internally?

 

  was:
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is however still used in the 
ANT build-impl.xml file under endorsed.classpath.path. The problem is that if 
you change "-Xbootclasspath/p:" to "-patch module java.base=" that NetBeans 
automatically overwrites it back to "-Xbootclasspath/p" when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. I am not able anymore to run this class 
even when I change the Source/Binary format of the project back to JDK1.8. It 
seems that Apache NetBeans has hardcoded -Xbootclasspath internally?

 


> -Xbootclasspath/p is no longer a supported option
> -
>
> Key: NETBEANS-2452
> URL: https://issues.apache.org/jira/browse/NETBEANS-2452
> Project: NetBeans
>  Issue Type: Bug
>  Components: cnd - Execution
>Affects Versions: 9.0, 10.0, 11.0
> Environment: OpenJDK 11
>Reporter: Emile Brinkman
>Assignee: Emile Brinkman
>Priority: Major
>  Labels: patch
> Fix For: 11.0
>
>
> I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
> OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
> apparently has to be changed to --patch-module. It is however still used in 
> the ANT build-impl.xml file under endorsed.classpath.path. The problem is 
> that if you change "-Xbootclasspath/p:" to "--patch module java.base=" that 
> NetBeans automatically overwrites it back to "-Xbootclasspath/p" when you 
> change properties of a project. -Xbootclasspath/a and -Xbootclasspath also 
> don't work.
> I also get the following error when running a class even when I changed 
> everything to --patch module:
> {{-Xbootclasspath/p is no longer a supported option.}}
>  {{Error: Could not create the Java Virtual Machine.}}
>  {{Error: A fatal exception has occurred. Program will exit.}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
>  The following error occurred while executing this line:}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
>  Java returned: 1}}
>  {{BUILD FAILED (total time: 0 seconds)}}
> Removing the cache folder doesn't help. I am not able anymore to run this 
> class even when I change the Source/Binary format of the project back to 
> JDK1.8. It seems that Apache NetBeans has hardcoded -Xbootclasspath 
> internally?
>  



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

-
To 

[jira] [Updated] (NETBEANS-2452) -Xbootclasspath/p is no longer a supported option

2019-04-23 Thread Emile Brinkman (JIRA)


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

Emile Brinkman updated NETBEANS-2452:
-
Description: 
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is however still used in the 
ANT build-impl.xml file under endorsed.classpath.path. The problem is that if 
you change "-Xbootclasspath/p:" to "-patch module java.base=" that NetBeans 
automatically overwrites it back to "-Xbootclasspath/p" when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. I am not able anymore to run this class 
even when I change the Source/Binary format of the project back to JDK1.8. It 
seems that Apache NetBeans has hardcoded -Xbootclasspath internally?

 

  was:
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is however still used in the 
ANT build-impl.xml file under endorsed.classpath.path. The problem is that if 
you change "-Xbootclasspath/p:" to "-patch module java.base=" that NetBeans 
automatically overwrites it back to "-Xbootclasspath/p" when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. I am not able anymore to run this class 
even when I change the Source/Binary format of the project to JDK1.8. It seems 
that Apache NetBeans has hardcoded -Xbootclasspath internally?

 


> -Xbootclasspath/p is no longer a supported option
> -
>
> Key: NETBEANS-2452
> URL: https://issues.apache.org/jira/browse/NETBEANS-2452
> Project: NetBeans
>  Issue Type: Bug
>  Components: cnd - Execution
>Affects Versions: 9.0, 10.0, 11.0
> Environment: OpenJDK 11
>Reporter: Emile Brinkman
>Assignee: Emile Brinkman
>Priority: Major
>  Labels: patch
> Fix For: 11.0
>
>
> I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
> OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
> apparently has to be changed to --patch-module. It is however still used in 
> the ANT build-impl.xml file under endorsed.classpath.path. The problem is 
> that if you change "-Xbootclasspath/p:" to "-patch module java.base=" that 
> NetBeans automatically overwrites it back to "-Xbootclasspath/p" when you 
> change properties of a project. -Xbootclasspath/a and -Xbootclasspath also 
> don't work.
> I also get the following error when running a class even when I changed 
> everything to --patch module:
> {{-Xbootclasspath/p is no longer a supported option.}}
>  {{Error: Could not create the Java Virtual Machine.}}
>  {{Error: A fatal exception has occurred. Program will exit.}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
>  The following error occurred while executing this line:}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
>  Java returned: 1}}
>  {{BUILD FAILED (total time: 0 seconds)}}
> Removing the cache folder doesn't help. I am not able anymore to run this 
> class even when I change the Source/Binary format of the project back to 
> JDK1.8. It seems that Apache NetBeans has hardcoded -Xbootclasspath 
> internally?
>  



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

-
To unsubscribe, 

[jira] [Updated] (NETBEANS-2452) -Xbootclasspath/p is no longer a supported option

2019-04-23 Thread Emile Brinkman (JIRA)


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

Emile Brinkman updated NETBEANS-2452:
-
Description: 
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is however still used in the 
ANT build-impl.xml file under endorsed.classpath.path. The problem is that if 
you change "-Xbootclasspath/p:" to "-patch module java.base=" that NetBeans 
automatically overwrites it back to "-Xbootclasspath/p" when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. I am not able anymore to run this class 
even when I change the Source/Binary format of the project to JDK1.8. It seems 
that Apache NetBeans has hardcoded -Xbootclasspath internally?

 

  was:
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is however still used in the 
ANT build-impl.xml file under endorsed.classpath.path. The problem is that if 
you change "-Xbootclasspath/p:" to "-patch module java.base=" that NetBeans 
automatically overwrites it back to "-Xbootclasspath/p" when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. It seems that Apache NetBeans has 
hardcoded -Xbootclasspath internally?

 


> -Xbootclasspath/p is no longer a supported option
> -
>
> Key: NETBEANS-2452
> URL: https://issues.apache.org/jira/browse/NETBEANS-2452
> Project: NetBeans
>  Issue Type: Bug
>  Components: cnd - Execution
>Affects Versions: 9.0, 10.0, 11.0
> Environment: OpenJDK 11
>Reporter: Emile Brinkman
>Assignee: Emile Brinkman
>Priority: Major
>  Labels: patch
> Fix For: 11.0
>
>
> I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
> OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
> apparently has to be changed to --patch-module. It is however still used in 
> the ANT build-impl.xml file under endorsed.classpath.path. The problem is 
> that if you change "-Xbootclasspath/p:" to "-patch module java.base=" that 
> NetBeans automatically overwrites it back to "-Xbootclasspath/p" when you 
> change properties of a project. -Xbootclasspath/a and -Xbootclasspath also 
> don't work.
> I also get the following error when running a class even when I changed 
> everything to --patch module:
> {{-Xbootclasspath/p is no longer a supported option.}}
>  {{Error: Could not create the Java Virtual Machine.}}
>  {{Error: A fatal exception has occurred. Program will exit.}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
>  The following error occurred while executing this line:}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
>  Java returned: 1}}
>  {{BUILD FAILED (total time: 0 seconds)}}
> Removing the cache folder doesn't help. I am not able anymore to run this 
> class even when I change the Source/Binary format of the project to JDK1.8. 
> It seems that Apache NetBeans has hardcoded -Xbootclasspath internally?
>  



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

[jira] [Updated] (NETBEANS-2452) -Xbootclasspath/p is no longer a supported option

2019-04-23 Thread Emile Brinkman (JIRA)


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

Emile Brinkman updated NETBEANS-2452:
-
Description: 
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is however still used in the 
ANT build-impl.xml file under endorsed.classpath.path. The problem is that if 
you change "-Xbootclasspath/p:" to "-patch module java.base=" that NetBeans 
automatically overwrites it back to "-Xbootclasspath/p" when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. It seems that Apache NetBeans has 
hardcoded -Xbootclasspath internally?

 

  was:
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is however still used in the 
ANT build-impl.xml file under endorsed.classpath.path. The problem is that if 
you change "-Xbootclasspath/p:" to "-patch module java.base=" that NetBeans 
automatically overwrites it back to -Xbootclasspath/p when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. It seems that Apache NetBeans has 
hardcoded -Xbootclasspath internally?

 


> -Xbootclasspath/p is no longer a supported option
> -
>
> Key: NETBEANS-2452
> URL: https://issues.apache.org/jira/browse/NETBEANS-2452
> Project: NetBeans
>  Issue Type: Bug
>  Components: cnd - Execution
>Affects Versions: 9.0, 10.0, 11.0
> Environment: OpenJDK 11
>Reporter: Emile Brinkman
>Assignee: Emile Brinkman
>Priority: Major
>  Labels: patch
> Fix For: 11.0
>
>
> I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
> OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
> apparently has to be changed to --patch-module. It is however still used in 
> the ANT build-impl.xml file under endorsed.classpath.path. The problem is 
> that if you change "-Xbootclasspath/p:" to "-patch module java.base=" that 
> NetBeans automatically overwrites it back to "-Xbootclasspath/p" when you 
> change properties of a project. -Xbootclasspath/a and -Xbootclasspath also 
> don't work.
> I also get the following error when running a class even when I changed 
> everything to --patch module:
> {{-Xbootclasspath/p is no longer a supported option.}}
>  {{Error: Could not create the Java Virtual Machine.}}
>  {{Error: A fatal exception has occurred. Program will exit.}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
>  The following error occurred while executing this line:}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
>  Java returned: 1}}
>  {{BUILD FAILED (total time: 0 seconds)}}
> Removing the cache folder doesn't help. It seems that Apache NetBeans has 
> hardcoded -Xbootclasspath internally?
>  



--
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-2452) -Xbootclasspath/p is no longer a supported option

2019-04-23 Thread Emile Brinkman (JIRA)


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

Emile Brinkman updated NETBEANS-2452:
-
Description: 
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is however still used in the 
ANT build-impl.xml file under endorsed.classpath.path. The problem is that if 
you change "-Xbootclasspath/p:" to "-patch module java.base=" that NetBeans 
automatically overwrites it back to -Xbootclasspath/p when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. It seems that Apache NetBeans has 
hardcoded -Xbootclasspath internally?

 

  was:
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is however still used in the 
ANT build-impl.xml file under endorsed.classpath.path. The problem is that if 
you change "-Xbootclasspath/p:" tot "-patch module java.base=" that NetBeans 
automatically overwrites it back to -Xbootclasspath/p when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. It seems that Apache NetBeans has 
hardcoded -Xbootclasspath internally?

 


> -Xbootclasspath/p is no longer a supported option
> -
>
> Key: NETBEANS-2452
> URL: https://issues.apache.org/jira/browse/NETBEANS-2452
> Project: NetBeans
>  Issue Type: Bug
>  Components: cnd - Execution
>Affects Versions: 9.0, 10.0, 11.0
> Environment: OpenJDK 11
>Reporter: Emile Brinkman
>Assignee: Emile Brinkman
>Priority: Major
>  Labels: patch
> Fix For: 11.0
>
>
> I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
> OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
> apparently has to be changed to --patch-module. It is however still used in 
> the ANT build-impl.xml file under endorsed.classpath.path. The problem is 
> that if you change "-Xbootclasspath/p:" to "-patch module java.base=" that 
> NetBeans automatically overwrites it back to -Xbootclasspath/p when you 
> change properties of a project. -Xbootclasspath/a and -Xbootclasspath also 
> don't work.
> I also get the following error when running a class even when I changed 
> everything to --patch module:
> {{-Xbootclasspath/p is no longer a supported option.}}
>  {{Error: Could not create the Java Virtual Machine.}}
>  {{Error: A fatal exception has occurred. Program will exit.}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
>  The following error occurred while executing this line:}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
>  Java returned: 1}}
>  {{BUILD FAILED (total time: 0 seconds)}}
> Removing the cache folder doesn't help. It seems that Apache NetBeans has 
> hardcoded -Xbootclasspath internally?
>  



--
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-2452) -Xbootclasspath/p is no longer a supported option

2019-04-23 Thread Emile Brinkman (JIRA)


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

Emile Brinkman updated NETBEANS-2452:
-
Affects Version/s: 9.0
   10.0

> -Xbootclasspath/p is no longer a supported option
> -
>
> Key: NETBEANS-2452
> URL: https://issues.apache.org/jira/browse/NETBEANS-2452
> Project: NetBeans
>  Issue Type: Bug
>  Components: cnd - Execution
>Affects Versions: 9.0, 10.0, 11.0
> Environment: OpenJDK 11
>Reporter: Emile Brinkman
>Assignee: Emile Brinkman
>Priority: Major
>  Labels: patch
> Fix For: 11.0
>
>
> I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
> OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
> apparently has to be changed to --patch-module. It is however still used in 
> the ANT build-impl.xml file under endorsed.classpath.path. The problem is 
> that if you change "-Xbootclasspath/p:" tot "-patch module java.base=" that 
> NetBeans automatically overwrites it back to -Xbootclasspath/p when you 
> change properties of a project. -Xbootclasspath/a and -Xbootclasspath also 
> don't work.
> I also get the following error when running a class even when I changed 
> everything to --patch module:
> {{-Xbootclasspath/p is no longer a supported option.}}
>  {{Error: Could not create the Java Virtual Machine.}}
>  {{Error: A fatal exception has occurred. Program will exit.}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
>  The following error occurred while executing this line:}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
>  Java returned: 1}}
>  {{BUILD FAILED (total time: 0 seconds)}}
> Removing the cache folder doesn't help. It seems that Apache NetBeans has 
> hardcoded -Xbootclasspath internally?
>  



--
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-2452) -Xbootclasspath/p is no longer a supported option

2019-04-23 Thread Emile Brinkman (JIRA)


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

Emile Brinkman updated NETBEANS-2452:
-
Description: 
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is however still used in the 
ANT build-impl.xml file under endorsed.classpath.path. The problem is that if 
you change "-Xbootclasspath/p:" tot "-patch module java.base=" that NetBeans 
automatically overwrites it back to -Xbootclasspath/p when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. It seems that Apache NetBeans has 
hardcoded -Xbootclasspath internally?

 

  was:
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is used in the ANT 
build-impl.xml file under endorsed.classpath.path. The problem is that if you 
change "-Xbootclasspath/p:" tot "-patch module java.base=" that NetBeans 
automatically overwrites it back to -Xbootclasspath/p when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. It seems that Apache NetBeans has 
hardcoded -Xbootclasspath internally?

 


> -Xbootclasspath/p is no longer a supported option
> -
>
> Key: NETBEANS-2452
> URL: https://issues.apache.org/jira/browse/NETBEANS-2452
> Project: NetBeans
>  Issue Type: Bug
>  Components: cnd - Execution
>Affects Versions: 11.0
> Environment: OpenJDK 11
>Reporter: Emile Brinkman
>Assignee: Emile Brinkman
>Priority: Major
>  Labels: patch
> Fix For: 11.0
>
>
> I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
> OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
> apparently has to be changed to --patch-module. It is however still used in 
> the ANT build-impl.xml file under endorsed.classpath.path. The problem is 
> that if you change "-Xbootclasspath/p:" tot "-patch module java.base=" that 
> NetBeans automatically overwrites it back to -Xbootclasspath/p when you 
> change properties of a project. -Xbootclasspath/a and -Xbootclasspath also 
> don't work.
> I also get the following error when running a class even when I changed 
> everything to --patch module:
> {{-Xbootclasspath/p is no longer a supported option.}}
>  {{Error: Could not create the Java Virtual Machine.}}
>  {{Error: A fatal exception has occurred. Program will exit.}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
>  The following error occurred while executing this line:}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
>  Java returned: 1}}
>  {{BUILD FAILED (total time: 0 seconds)}}
> Removing the cache folder doesn't help. It seems that Apache NetBeans has 
> hardcoded -Xbootclasspath internally?
>  



--
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-2452) -Xbootclasspath/p is no longer a supported option

2019-04-23 Thread Emile Brinkman (JIRA)
Emile Brinkman created NETBEANS-2452:


 Summary: -Xbootclasspath/p is no longer a supported option
 Key: NETBEANS-2452
 URL: https://issues.apache.org/jira/browse/NETBEANS-2452
 Project: NetBeans
  Issue Type: Bug
  Components: cnd - Execution
Affects Versions: 11.0
 Environment: OpenJDK 11
Reporter: Emile Brinkman
Assignee: Emile Brinkman
 Fix For: 11.0


I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The -Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is used in the ANT 
build-impl.xml file under endorsed.classpath.path. The problem is that if you 
change "-Xbootclasspath/p:" tot "--patch module java.base=" that NetBeans 
automatically overwrites it back to -Xbootclasspath/p when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
{{Error: Could not create the Java Virtual Machine.}}
{{Error: A fatal exception has occurred. Program will exit.}}
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
{{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. It seems that Apache NetBeans has 
hardcoded -Xbootclasspath internally?

 



--
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-2452) -Xbootclasspath/p is no longer a supported option

2019-04-23 Thread Emile Brinkman (JIRA)


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

Emile Brinkman updated NETBEANS-2452:
-
Description: 
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is used in the ANT 
build-impl.xml file under endorsed.classpath.path. The problem is that if you 
change "-Xbootclasspath/p:" tot "-patch module java.base=" that NetBeans 
automatically overwrites it back to -Xbootclasspath/p when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
 {{Error: Could not create the Java Virtual Machine.}}
 {{Error: A fatal exception has occurred. Program will exit.}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
 
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
 {{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. It seems that Apache NetBeans has 
hardcoded -Xbootclasspath internally?

 

  was:
I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
OpenJDK 11. The -Xbootclasspath option is no longer supported bij JDK11 and 
apparently has to be changed to --patch-module. It is used in the ANT 
build-impl.xml file under endorsed.classpath.path. The problem is that if you 
change "-Xbootclasspath/p:" tot "--patch module java.base=" that NetBeans 
automatically overwrites it back to -Xbootclasspath/p when you change 
properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't work.

I also get the following error when running a class even when I changed 
everything to --patch module:

{{-Xbootclasspath/p is no longer a supported option.}}
{{Error: Could not create the Java Virtual Machine.}}
{{Error: A fatal exception has occurred. Program will exit.}}
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
 The following error occurred while executing this line:}}
{{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
 Java returned: 1}}
{{BUILD FAILED (total time: 0 seconds)}}

Removing the cache folder doesn't help. It seems that Apache NetBeans has 
hardcoded -Xbootclasspath internally?

 


> -Xbootclasspath/p is no longer a supported option
> -
>
> Key: NETBEANS-2452
> URL: https://issues.apache.org/jira/browse/NETBEANS-2452
> Project: NetBeans
>  Issue Type: Bug
>  Components: cnd - Execution
>Affects Versions: 11.0
> Environment: OpenJDK 11
>Reporter: Emile Brinkman
>Assignee: Emile Brinkman
>Priority: Major
>  Labels: patch
> Fix For: 11.0
>
>
> I have upgraded from NetBeans 8.2 and JDK1.8 to Apache NetBeans 11.0 and 
> OpenJDK 11. The Xbootclasspath option is no longer supported bij JDK11 and 
> apparently has to be changed to --patch-module. It is used in the ANT 
> build-impl.xml file under endorsed.classpath.path. The problem is that if you 
> change "-Xbootclasspath/p:" tot "-patch module java.base=" that NetBeans 
> automatically overwrites it back to -Xbootclasspath/p when you change 
> properties of a project. -Xbootclasspath/a and -Xbootclasspath also don't 
> work.
> I also get the following error when running a class even when I changed 
> everything to --patch module:
> {{-Xbootclasspath/p is no longer a supported option.}}
>  {{Error: Could not create the Java Virtual Machine.}}
>  {{Error: A fatal exception has occurred. Program will exit.}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:111:
>  The following error occurred while executing this line:}}
>  
> {{C:\Users\user1\AppData\Local\NetBeans\Cache\11.0\executor-snippets\run.xml:94:
>  Java returned: 1}}
>  {{BUILD FAILED (total time: 0 seconds)}}
> Removing the cache folder doesn't help. It seems that Apache NetBeans has 
> hardcoded -Xbootclasspath internally?
>  



--
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-703) Rename packages windows takes a long time to respond

2019-04-23 Thread Reema Taneja (JIRA)


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

Reema Taneja resolved NETBEANS-703.
---
Resolution: Cannot Reproduce

> Rename packages windows takes a long time to respond
> 
>
> Key: NETBEANS-703
> URL: https://issues.apache.org/jira/browse/NETBEANS-703
> Project: NetBeans
>  Issue Type: Bug
> Environment: Windows 7
>Reporter: Alex de Kruijff
>Assignee: Reema Taneja
>Priority: Major
>
> *Actual*
>  Given NetBeans 8.2
>  When renaming a package (ctrl-R) using the projects view
>  Then a windows is opened
>  And the field "New name" is unresponive for 10 seconds or so.
> *Expected*
>  Given NetBeans 8.2
>  When renaming a package (ctrl-R)
>  Then a windows is opened
>  And the field "New name" is responive within 2 seconds.
>  



--
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-2451) Run main project disabled for Spring Boot applications

2019-04-23 Thread hg (JIRA)


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

hg commented on NETBEANS-2451:
--

I've found a better fix... create a gradle.properties file in the root of the 
project containing the following:
{noformat}
action.debug.args=bootRun --debug-jvm
action.run.args=bootRun
{noformat}
These can also be added via the GUI. Project Properties > Build Actions

> Run main project disabled for Spring Boot applications
> --
>
> Key: NETBEANS-2451
> URL: https://issues.apache.org/jira/browse/NETBEANS-2451
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0
>Reporter: hg
>Assignee: hg
>Priority: Major
>  Labels: Gradle
> Attachments: netbeans-run-issue.mp4
>
>
> The menu options for "Run Main Project" and "Debug Main Project" are disabled 
> for Spring Boot applications. See attached screen recording (note also that 
> the menu does not update automatically).
>  
> *Steps to reproduce:*
> 1) Generate a demo Spring Boot Gradle project here:
> [https://start.spring.io/]
> 2) Open Project in Netbeans. Menu items are disabled.
>  
> *Workarounds:*
> 1) Use the "bootRun" task as found in the Navigator panel.
> or 2) Modify build.gradle to add in the application plugin and mainClassName 
> variable. This causes NetBeans to add a "run" task and enables the menu.
>  
>  
> *Product Version:* Apache NetBeans IDE 11.0 (Build 
> incubator-netbeans-release-404-on-20190319)
> *Java:* 1.8.0_192; Java HotSpot(TM) 64-Bit Server VM 25.192-b12
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_192-b12
> *System:* Mac OS X version 10.14.4 running on x86_64; UTF-8; en_GB (nb)



--
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] [Assigned] (NETBEANS-2451) Run main project disabled for Spring Boot applications

2019-04-23 Thread hg (JIRA)


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

hg reassigned NETBEANS-2451:


Assignee: hg

> Run main project disabled for Spring Boot applications
> --
>
> Key: NETBEANS-2451
> URL: https://issues.apache.org/jira/browse/NETBEANS-2451
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0
>Reporter: hg
>Assignee: hg
>Priority: Major
>  Labels: Gradle
> Attachments: netbeans-run-issue.mp4
>
>
> The menu options for "Run Main Project" and "Debug Main Project" are disabled 
> for Spring Boot applications. See attached screen recording (note also that 
> the menu does not update automatically).
>  
> *Steps to reproduce:*
> 1) Generate a demo Spring Boot Gradle project here:
> [https://start.spring.io/]
> 2) Open Project in Netbeans. Menu items are disabled.
>  
> *Workarounds:*
> 1) Use the "bootRun" task as found in the Navigator panel.
> or 2) Modify build.gradle to add in the application plugin and mainClassName 
> variable. This causes NetBeans to add a "run" task and enables the menu.
>  
>  
> *Product Version:* Apache NetBeans IDE 11.0 (Build 
> incubator-netbeans-release-404-on-20190319)
> *Java:* 1.8.0_192; Java HotSpot(TM) 64-Bit Server VM 25.192-b12
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_192-b12
> *System:* Mac OS X version 10.14.4 running on x86_64; UTF-8; en_GB (nb)



--
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-2449) Indent Guide lines overdraw font

2019-04-23 Thread Thomas Oster (JIRA)


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

Thomas Oster commented on NETBEANS-2449:


After changing the font from `Monospaced` to `Noto Sans Mono` it looks better. 
So it may be a problem related to specific fonts.

> Indent Guide lines overdraw font
> 
>
> Key: NETBEANS-2449
> URL: https://issues.apache.org/jira/browse/NETBEANS-2449
> Project: NetBeans
>  Issue Type: Bug
>  Components: editor - Painting  Printing
>Affects Versions: 11.0
> Environment: Arch Linux, openjdk 11.0.3, cinnamon
>Reporter: Thomas Oster
>Priority: Minor
> Attachments: bn.png
>
>
> Since the upgrade to NB 11.0 (from 10) the indent guide lines in the editor 
> overdraw the normal font, which looks broken. I first suspected the usual 
> font-rendering and anti-aliasing stuff, but that seems to work. Maybe the 
> drawing order changed?



--
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-2451) Run main project disabled for Spring Boot applications

2019-04-23 Thread HG (JIRA)
HG created NETBEANS-2451:


 Summary: Run main project disabled for Spring Boot applications
 Key: NETBEANS-2451
 URL: https://issues.apache.org/jira/browse/NETBEANS-2451
 Project: NetBeans
  Issue Type: Bug
  Components: projects - Gradle
Affects Versions: 11.0
Reporter: HG
 Attachments: netbeans-run-issue.mp4

The menu options for "Run Main Project" and "Debug Main Project" are disabled 
for Spring Boot applications. See attached screen recording (note also that the 
menu does not update automatically).

 

*Steps to reproduce:*
1) Generate a demo Spring Boot Gradle project here:
[https://start.spring.io/]

2) Open Project in Netbeans. Menu items are disabled.

 

*Workarounds:*

1) Use the "bootRun" task as found in the Navigator panel.

or 2) Modify build.gradle to add in the application plugin and mainClassName 
variable. This causes NetBeans to add a "run" task and enables the menu.

 

 

*Product Version:* Apache NetBeans IDE 11.0 (Build 
incubator-netbeans-release-404-on-20190319)
*Java:* 1.8.0_192; Java HotSpot(TM) 64-Bit Server VM 25.192-b12
*Runtime:* Java(TM) SE Runtime Environment 1.8.0_192-b12
*System:* Mac OS X version 10.14.4 running on x86_64; UTF-8; en_GB (nb)



--
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-2131) CCE: JDK11, Goto type 'WebView'

2019-04-23 Thread Reema Taneja (JIRA)


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

Reema Taneja resolved NETBEANS-2131.

Resolution: Duplicate

> CCE: JDK11, Goto type 'WebView'
> ---
>
> Key: NETBEANS-2131
> URL: https://issues.apache.org/jira/browse/NETBEANS-2131
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Navigation
>Reporter: Jaroslav Tulach
>Assignee: Reema Taneja
>Priority: Major
>
> Running the NetBeans 11 VC1 on JDK11 with an empty dir. Created "Java with 
> Maven/Java Frontend App". Then I tried Ctrl-O and jump to `WebView`. Nothing 
> happens and this is the text on the console:
>  
> {code:java}
> Even though the source level of  is set to: 11, java.util.zip.CRC32C cannot 
> be found on the system module path:
> Changing source level to 1.8
> SEVERE [global]
> java.lang.ClassCastException: class com.sun.tools.javac.jvm.ClassReader$1 
> cannot be cast to class com.sun.tools.javac.code.Type$ErrorType 
> (com.sun.tools.javac.jvm.ClassReader$1 and 
> com.sun.tools.javac.code.Type$ErrorType are in unnamed module of loader 
> org.netbeans.StandardModule$OneModuleClassLoader @49d43819)
>     at 
> org.netbeans.modules.java.source.builder.TreeFactory.Type(TreeFactory.java:858)
>     at org.netbeans.api.java.source.TreeMaker.Type(TreeMaker.java:1107)
>     at 
> org.netbeans.modules.java.classfile.CodeGenerator$TreeBuilder.visitVariable(CodeGenerator.java:520)
>     at 
> org.netbeans.modules.java.classfile.CodeGenerator$TreeBuilder.visitVariable(CodeGenerator.java:285)
>     at com.sun.tools.javac.code.Symbol$VarSymbol.accept(Symbol.java:1606)
>     at 
> javax.lang.model.util.AbstractElementVisitor6.visit(AbstractElementVisitor6.java:106)
>     at 
> org.netbeans.modules.java.classfile.CodeGenerator$TreeBuilder.visitType(CodeGenerator.java:367)
>     at 
> org.netbeans.modules.java.classfile.CodeGenerator$TreeBuilder.visitType(CodeGenerator.java:285)
>     at 
> com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1473)
>     at 
> javax.lang.model.util.AbstractElementVisitor6.visit(AbstractElementVisitor6.java:106)
>     at 
> org.netbeans.modules.java.classfile.CodeGenerator$TreeBuilder.visitType(CodeGenerator.java:367)
>     at 
> org.netbeans.modules.java.classfile.CodeGenerator$TreeBuilder.visitType(CodeGenerator.java:285)
>     at 
> com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1473)
>     at 
> javax.lang.model.util.AbstractElementVisitor6.visit(AbstractElementVisitor6.java:106)
>     at 
> org.netbeans.modules.java.classfile.CodeGenerator.generateCode(CodeGenerator.java:275)
>     at 
> org.netbeans.modules.java.classfile.CodeGenerator$1.run(CodeGenerator.java:232)
>     at 
> org.netbeans.modules.java.classfile.CodeGenerator$1.run(CodeGenerator.java:152)
>     at org.netbeans.api.java.source.JavaSource$1.run(JavaSource.java:672)
>     at org.netbeans.api.java.source.JavaSource$1.run(JavaSource.java:662)
>     at 
> org.netbeans.api.java.source.JavaSource$MultiTask.run(JavaSource.java:501)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
>     at 
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130)
>     at 
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
>     at 
> org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
>     at 
> org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
>     at 
> org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
>     at 
> org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
>     at 
> org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
>     at 
> org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:451)
>     at 
> org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:422)
>     at 
> org.netbeans.api.java.source.JavaSource.runModificationTask(JavaSource.java:683)
>     at 
> org.netbeans.modules.java.classfile.CodeGenerator.generateCode(CodeGenerator.java:152)
>     at 
> org.netbeans.modules.java.classfile.BinaryElementOpenImpl.open(BinaryElementOpenImpl.java:44)
>     at 
> 

[jira] [Resolved] (NETBEANS-2450) javac compiler option --enable-preview doesn't take effect for maven projects

2019-04-23 Thread Reema Taneja (JIRA)


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

Reema Taneja resolved NETBEANS-2450.

   Resolution: Fixed
Fix Version/s: 12.0

Merged
https://github.com/apache/incubator-netbeans/pull/1173


> javac compiler option --enable-preview doesn't take effect for maven projects
> -
>
> Key: NETBEANS-2450
> URL: https://issues.apache.org/jira/browse/NETBEANS-2450
> Project: NetBeans
>  Issue Type: Bug
>Reporter: Reema Taneja
>Assignee: Reema Taneja
>Priority: Major
> Fix For: 12.0
>
>
> pom.xml entry: 
> 
> 
> 
> maven-compiler-plugin
> 3.8.0
> 
> 
> --enable-preview
> 
> 
> 
> 
> 



--
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-2450) javac compiler option --enable-preview doesn't take effect for maven projects

2019-04-23 Thread Reema Taneja (JIRA)
Reema Taneja created NETBEANS-2450:
--

 Summary: javac compiler option --enable-preview doesn't take 
effect for maven projects
 Key: NETBEANS-2450
 URL: https://issues.apache.org/jira/browse/NETBEANS-2450
 Project: NetBeans
  Issue Type: Bug
Reporter: Reema Taneja
Assignee: Reema Taneja


pom.xml entry: 




maven-compiler-plugin
3.8.0


--enable-preview








--
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-2449) Indent Guide lines overdraw font

2019-04-23 Thread Thomas Oster (JIRA)
Thomas Oster created NETBEANS-2449:
--

 Summary: Indent Guide lines overdraw font
 Key: NETBEANS-2449
 URL: https://issues.apache.org/jira/browse/NETBEANS-2449
 Project: NetBeans
  Issue Type: Bug
  Components: editor - Painting  Printing
Affects Versions: 11.0
 Environment: Arch Linux, openjdk 11.0.3, cinnamon
Reporter: Thomas Oster
 Attachments: bn.png

Since the upgrade to NB 11.0 (from 10) the indent guide lines in the editor 
overdraw the normal font, which looks broken. I first suspected the usual 
font-rendering and anti-aliasing stuff, but that seems to work. Maybe the 
drawing order changed?



--
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-2448) Add migrator support for JDK 10, 12 syntax

2019-04-23 Thread Reema Taneja (JIRA)


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

Reema Taneja updated NETBEANS-2448:
---
Description: 
We should add migrators for newer JDK releases 10, 12, in "Inspect and 
Transform" dialog. 
For JDK 9, 11, no JDK migration support hints were added.

  was:We should add migrators for newer JDK releases 10, 12. For JDK 9, 11, no 
JDK migration support hints were added.


> Add migrator support for JDK 10, 12 syntax
> --
>
> Key: NETBEANS-2448
> URL: https://issues.apache.org/jira/browse/NETBEANS-2448
> Project: NetBeans
>  Issue Type: Bug
>Reporter: Reema Taneja
>Assignee: Reema Taneja
>Priority: Major
>
> We should add migrators for newer JDK releases 10, 12, in "Inspect and 
> Transform" dialog. 
> For JDK 9, 11, no JDK migration support hints were added.



--
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-2448) Add migrator support for JDK 10, 12 syntax

2019-04-23 Thread Reema Taneja (JIRA)
Reema Taneja created NETBEANS-2448:
--

 Summary: Add migrator support for JDK 10, 12 syntax
 Key: NETBEANS-2448
 URL: https://issues.apache.org/jira/browse/NETBEANS-2448
 Project: NetBeans
  Issue Type: Bug
Reporter: Reema Taneja
Assignee: Reema Taneja


We should add migrators for newer JDK releases 10, 12. For JDK 9, 11, no JDK 
migration support hints were added.



--
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-2447) Gradle - building.

2019-04-23 Thread David Irving (JIRA)
David Irving created NETBEANS-2447:
--

 Summary: Gradle - building.
 Key: NETBEANS-2447
 URL: https://issues.apache.org/jira/browse/NETBEANS-2447
 Project: NetBeans
  Issue Type: Bug
  Components: projects - Gradle
Affects Versions: 11.0
 Environment: Windows 10 - up to date.
Reporter: David Irving


Out of bounds exception during gradle build. Logs from IDE included.


  2019-04-18T15:43:14
  198594192
  64
  300
  15
  SCREEN SIZE
  1366
  768
  3


  2019-04-18T15:43:14
  198594193
  65
  700
  15
  IDE_STARTUP


  2019-04-18T15:43:19
  198599170
  100
  800
  15
  USG_LOOK_AND_FEEL
  DARK Metal
  Dark Metal


  2019-04-18T15:43:26
  198606899
  135
  800
  14
  MEMORY
  8452857856


  2019-04-18T15:43:31
  198611690
  137
  400
  21
  UI_ACTION_BUTTON_PRESS
  UI_ACTION_BUTTON_PRESS
  org.openide.awt.Bundle
  org.openide.awt.Toolbar$DefaultIconButton[]
  org.openide.awt.Toolbar$DefaultIconButton
  org.netbeans.modules.project.ui.actions.OpenProject[Open 
Project...]
  org.netbeans.modules.project.ui.actions.OpenProject
  Open Project...


  2019-04-18T15:46:51
  198811452
  138
  500
  21
  LOG_WINDOW_DEACTIVATED
  LOG_WINDOW_DEACTIVATED
  org.netbeans.core.ui.warmup.Bundle


  2019-04-18T15:46:52
  198812621
  139
  500
  21
  LOG_WINDOW_DEACTIVATED
  LOG_WINDOW_DEACTIVATED
  org.netbeans.core.ui.warmup.Bundle


  2019-04-18T15:46:57
  198817768
  140
  500
  69
  LOG_WINDOW_ACTIVATED
  LOG_WINDOW_ACTIVATED
  org.netbeans.core.ui.warmup.Bundle
  4248


  2019-04-18T15:46:59
  198819116
  141
  500
  69
  LOG_WINDOW_ACTIVATED
  LOG_WINDOW_ACTIVATED
  org.netbeans.core.ui.warmup.Bundle
  460


  2019-04-18T15:47:00
  198820782
  142
  900
  22
  2
  
    java.lang.ArrayIndexOutOfBoundsException: 2
    
  
org.netbeans.modules.gradle.api.GradleDependency$ModuleDependency
  init
  85
  ${netBeansDir}modules/org-netbeans-modules-gradle.jar
    
    
  org.netbeans.modules.gradle.api.GradleBaseProjectBuilder
  processDependencies
  149
  ${netBeansDir}modules/org-netbeans-modules-gradle.jar
    
    
  org.netbeans.modules.gradle.api.GradleBaseProjectBuilder
  build
  75
  ${netBeansDir}modules/org-netbeans-modules-gradle.jar
    
    
  
org.netbeans.modules.gradle.api.GradleBaseProjectBuilder$Extractor
  extract
  288
  ${netBeansDir}modules/org-netbeans-modules-gradle.jar
    
    
  org.netbeans.modules.gradle.GradleProjectCache
  createGradleProject
  432
  ${netBeansDir}modules/org-netbeans-modules-gradle.jar
    
    
  org.netbeans.modules.gradle.GradleProjectCache
  loadGradleProject
  257
  ${netBeansDir}modules/org-netbeans-modules-gradle.jar
    
    
  org.netbeans.modules.gradle.GradleProjectCache
  access$100
  85
  ${netBeansDir}modules/org-netbeans-modules-gradle.jar
    
    
  
org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask
  call
  348
  ${netBeansDir}modules/org-netbeans-modules-gradle.jar
    
    
  
org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask
  call
  326
  ${netBeansDir}modules/org-netbeans-modules-gradle.jar
    
    
  java.util.concurrent.FutureTask
  run
  266
  ${java.home}lib/rt.jar
    
    
  org.openide.util.RequestProcessor$Task
  run
  1418
  ${netbeans.home}lib/org-openide-util.jar
    
    
  org.netbeans.modules.openide.util.GlobalLookup
  execute
  45
  ${netbeans.home}lib/org-openide-util-lookup.jar
    
    
  org.openide.util.lookup.Lookups
  executeWith
  278
  ${netbeans.home}lib/org-openide-util-lookup.jar
    
    
  org.openide.util.RequestProcessor$Processor
  run
  2033
  ${netbeans.home}lib/org-openide-util.jar
    
  


  2019-04-18T15:47:01
  198821245
  144
  700
  70
  UI_OPEN_PROJECTS
  UI_OPEN_PROJECTS
  org.netbeans.modules.project.ui.Bundle
  org.netbeans.modules.gradle.NbGradleProjectImpl
  NbGradleProjectImpl
  1


  2019-04-18T15:47:01
  198821245
  145
  800
  70
  USG_PROJECT_OPEN
  org.netbeans.modules.gradle.NbGradleProjectImpl


  2019-04-18T15:47:01
  198821631
  146
  800
  69
  INDEXING_STARTED
  INDEXING_STARTED
  org.netbeans.modules.parsing.impl.indexing.Bundle
  0


  2019-04-18T15:47:03
  198823819
  148
  800
  83
  USG_VCS_CLIENT
  GIT
  JAVALIB


  2019-04-18T15:47:10
  198830938
  151
  500
  21
  LOG_WINDOW_DEACTIVATED
  LOG_WINDOW_DEACTIVATED
  org.netbeans.core.ui.warmup.Bundle


  2019-04-18T15:48:55
  198935603
  160
  800
  69
  INDEXING_FINISHED
  INDEXING_FINISHED
  org.netbeans.modules.parsing.impl.indexing.Bundle
  113969
  java
  61
  85312
  SpringBinary
  57
  6
  TaskListIndexer
  4
  7
  
org.netbeans.modules.java.source.indexing.COSSynchronizingIndexer
  4
  31
  

[jira] [Created] (NETBEANS-2446) New project wizard with wrong project location

2019-04-23 Thread James Z (JIRA)
James Z created NETBEANS-2446:
-

 Summary: New project wizard with wrong project location
 Key: NETBEANS-2446
 URL: https://issues.apache.org/jira/browse/NETBEANS-2446
 Project: NetBeans
  Issue Type: Bug
  Components: ide - Code
Affects Versions: 11.0
Reporter: James Z


New Project wizard has bug, it used wrong Project Location, and when navigate 
with 'Next >', '< Back', the project location will become longer and longer. It 
also create lots of directories.

Such as: ~/NetBeansProjects/mavenproject1/mavenproject1/mavenproject1/.../...



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

2019-04-23 Thread JIRA


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

Dominik Derwiński commented on NETBEANS-2415:
-

But besides license, there is still the problem that it doesn't compile.

> 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] [Commented] (NETBEANS-888) Open Recent file not working

2019-04-23 Thread Christian Lenz (JIRA)


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

Christian Lenz commented on NETBEANS-888:
-

Only mac related? For me, on windows 10 with NB 10 and JDK 11.0.2 the menu 
entry is working.

> Open Recent file not working
> 
>
> Key: NETBEANS-888
> URL: https://issues.apache.org/jira/browse/NETBEANS-888
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - UI
>Affects Versions: 9.0, 10.0, 11.0
> Environment: MacOS High Sierra version 10.13.4
> MacOS Mojave 10.14.4
>Reporter: Javier A. Ortiz
>Priority: Major
>
> Clicking on File>Open Recent File>File doesn't open the file but using the 
> shortcut for the most recent one works.
> No error or suspecting messages in the log either.



--
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-2445) Need for Netbeans Version schema release for Chocolatey Package

2019-04-23 Thread ComFreek (JIRA)


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

ComFreek edited comment on NETBEANS-2445 at 4/23/19 6:05 AM:
-

I am a package maintainer as well and involved in the linked discussion. I 
think a short TL;DR would be helpful to you:
h2. Summary, TL;DR

Chocolatey is a package manager for Windows.

*Current state:* we have a package "netbeans" for NetBeans 8.2, see 
[https://chocolatey.org/packages/netbeans.]

*New state:* Apache NetBeans has officially been approven, thus we now have 
three alternative options:
 * Provide packages "netbeans", "apache-netbeans": "netbeans" is for the old 
version 8, "apache-netbeans" serves versions 9, 10 and 11 in parallel.
 Users of "apache-netbeans" may pin their desired major version and thus for 
example still receive updates on the 9.x line.

 * Provide packages "netbeans", "apache-netbeans9", "apache-netbeans10", 
"apache-netbeans11"
 Same as above, but now the versions are split onto three packages on their own.
 * Provide package "netbeans" with versions 8, 9, 10 and 11 in parallel
 Again, users may pin their version and still receive updates.

*Question from us to you*: Which option would you favor?

 


was (Author: comfreek):
I am a package maintainer as well and involved in the linked discussion. I 
think a quick TL;DR would be helpful to you:
h2. Summary, TL;DR

Chocolatey is a package manager for Windows.

*Current state:* we have a package "netbeans" for NetBeans 8.2, see 
[https://chocolatey.org/packages/netbeans.]

*New state:* Apache NetBeans has officially been approven, thus we now have 
three alternative options:
 * Provide packages "netbeans", "apache-netbeans": "netbeans" is for the old 
version 8, "apache-netbeans" serves versions 9, 10 and 11 in parallel.
 Users of "apache-netbeans" may pin their desired major version and thus for 
example still receive updates on the 9.x line.

 * Provide packages "netbeans", "apache-netbeans9", "apache-netbeans10", 
"apache-netbeans11"
 Same as above, but now the versions are split onto three packages on their own.
 * Provide package "netbeans" with versions 8, 9, 10 and 11 in parallel
 Again, users may pin their version and still receive updates.

*Question from us to you*: Which option would you favor?

 

> Need for Netbeans Version schema release for Chocolatey Package
> ---
>
> Key: NETBEANS-2445
> URL: https://issues.apache.org/jira/browse/NETBEANS-2445
> Project: NetBeans
>  Issue Type: Task
>Affects Versions: 10.0, 11.0
>Reporter: SALES
>Priority: Major
>  Labels: documentation, windows
>
> h1. Context
> I'm a chocolatey package maintainer... and also a big fan of Netbeans. I 
> recently implemented a dedicated {{Netbeans 11}} package.
> Now, the Chocolatey Moderators are faciing a dilemna about the package 
> version scheme.
> I'm about sure your feedback could help a lot.
> h1. Question
> From what I could see I looks more convenient to manage separated packages to 
> make softwares updates more confortable.
> I mean : if I initially installed Netbeans 10, I want to stick on 10, and 
> when I apply updates, stick on Netbeans 10, *and not upgrade to 11*. From my 
> point of view it makes the final user update process easier and safer. For 
> example to better manage plugin compatibilities.
> h1. Action
> Could yo please tell us your opinion about that on the dedicated ticket :
> [https://github.com/chocolatey/chocolatey-package-requests/issues/572]
>  
> So we can make the {{Netbeans 11}} available on chocolatey central repo ?
>  
> h1. Resources
>  * Package sources : [https://github.com/adriens/chocolatey-netbeans-11]
>  * Package moderation issue : 
> [https://github.com/chocolatey/chocolatey-package-requests/issues/572]
>  
> Thank you in advance for your help.
>  



--
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-2445) Need for Netbeans Version schema release for Chocolatey Package

2019-04-23 Thread ComFreek (JIRA)


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

ComFreek edited comment on NETBEANS-2445 at 4/23/19 6:04 AM:
-

I am a package maintainer as well and involved in the linked discussion. I 
think a quick TL;DR would be helpful to you:
h2. Summary, TL;DR

Chocolatey is a package manager for Windows.

*Current state:* we have a package "netbeans" for NetBeans 8.2, see 
[https://chocolatey.org/packages/netbeans.]

*New state:* Apache NetBeans has officially been approven, thus we now have 
three alternative options:
 * Provide packages "netbeans", "apache-netbeans": "netbeans" is for the old 
version 8, "apache-netbeans" serves versions 9, 10 and 11 in parallel.
 Users of "apache-netbeans" may pin their desired major version and thus for 
example still receive updates on the 9.x line.

 * Provide packages "netbeans", "apache-netbeans9", "apache-netbeans10", 
"apache-netbeans11"
 Same as above, but now the versions are split onto three packages on their own.
 * Provide package "netbeans" with versions 8, 9, 10 and 11 in parallel
 Again, users may pin their version and still receive updates.

*Question from us to you*: Which option would you favor?

 


was (Author: comfreek):
I am a package maintainer as well and involved in the linked discussion. I 
think a quick *TL;DR* would be helpful to you:

Chocolatey is a package manager for Windows.

Current state: we have a package "netbeans" for NetBeans 8.2, see 
[https://chocolatey.org/packages/netbeans.]

New state: Apache NetBeans has officially been approven, thus we now have three 
alternative options:
 * Provide packages "netbeans", "apache-netbeans": "netbeans" is for the old 
version 8, "apache-netbeans" serves versions 9, 10 and 11 in parallel.
Users of "apache-netbeans" may pin their desired major version and thus for 
example still receive updates on the 9.x line.


 * Provide packages "netbeans", "apache-netbeans9", "apache-netbeans10", 
"apache-netbeans11"
Same as above, but now the versions are split onto three packages on their own.
 * Provide package "netbeans" with versions 8, 9, 10 and 11 in parallel
Again, users may pin their version and still receive updates.

*Question from us to you*: Which option would you favor?

 

> Need for Netbeans Version schema release for Chocolatey Package
> ---
>
> Key: NETBEANS-2445
> URL: https://issues.apache.org/jira/browse/NETBEANS-2445
> Project: NetBeans
>  Issue Type: Task
>Affects Versions: 10.0, 11.0
>Reporter: SALES
>Priority: Major
>  Labels: documentation, windows
>
> h1. Context
> I'm a chocolatey package maintainer... and also a big fan of Netbeans. I 
> recently implemented a dedicated {{Netbeans 11}} package.
> Now, the Chocolatey Moderators are faciing a dilemna about the package 
> version scheme.
> I'm about sure your feedback could help a lot.
> h1. Question
> From what I could see I looks more convenient to manage separated packages to 
> make softwares updates more confortable.
> I mean : if I initially installed Netbeans 10, I want to stick on 10, and 
> when I apply updates, stick on Netbeans 10, *and not upgrade to 11*. From my 
> point of view it makes the final user update process easier and safer. For 
> example to better manage plugin compatibilities.
> h1. Action
> Could yo please tell us your opinion about that on the dedicated ticket :
> [https://github.com/chocolatey/chocolatey-package-requests/issues/572]
>  
> So we can make the {{Netbeans 11}} available on chocolatey central repo ?
>  
> h1. Resources
>  * Package sources : [https://github.com/adriens/chocolatey-netbeans-11]
>  * Package moderation issue : 
> [https://github.com/chocolatey/chocolatey-package-requests/issues/572]
>  
> Thank you in advance for your help.
>  



--
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-2445) Need for Netbeans Version schema release for Chocolatey Package

2019-04-23 Thread ComFreek (JIRA)


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

ComFreek commented on NETBEANS-2445:


I am a package maintainer as well and involved in the linked discussion. I 
think a quick *TL;DR* would be helpful to you:

Chocolatey is a package manager for Windows.

Current state: we have a package "netbeans" for NetBeans 8.2, see 
[https://chocolatey.org/packages/netbeans.]

New state: Apache NetBeans has officially been approven, thus we now have three 
alternative options:
 * Provide packages "netbeans", "apache-netbeans": "netbeans" is for the old 
version 8, "apache-netbeans" serves versions 9, 10 and 11 in parallel.
Users of "apache-netbeans" may pin their desired major version and thus for 
example still receive updates on the 9.x line.


 * Provide packages "netbeans", "apache-netbeans9", "apache-netbeans10", 
"apache-netbeans11"
Same as above, but now the versions are split onto three packages on their own.
 * Provide package "netbeans" with versions 8, 9, 10 and 11 in parallel
Again, users may pin their version and still receive updates.

*Question from us to you*: Which option would you favor?

 

> Need for Netbeans Version schema release for Chocolatey Package
> ---
>
> Key: NETBEANS-2445
> URL: https://issues.apache.org/jira/browse/NETBEANS-2445
> Project: NetBeans
>  Issue Type: Task
>Affects Versions: 10.0, 11.0
>Reporter: SALES
>Priority: Major
>  Labels: documentation, windows
>
> h1. Context
> I'm a chocolatey package maintainer... and also a big fan of Netbeans. I 
> recently implemented a dedicated {{Netbeans 11}} package.
> Now, the Chocolatey Moderators are faciing a dilemna about the package 
> version scheme.
> I'm about sure your feedback could help a lot.
> h1. Question
> From what I could see I looks more convenient to manage separated packages to 
> make softwares updates more confortable.
> I mean : if I initially installed Netbeans 10, I want to stick on 10, and 
> when I apply updates, stick on Netbeans 10, *and not upgrade to 11*. From my 
> point of view it makes the final user update process easier and safer. For 
> example to better manage plugin compatibilities.
> h1. Action
> Could yo please tell us your opinion about that on the dedicated ticket :
> [https://github.com/chocolatey/chocolatey-package-requests/issues/572]
>  
> So we can make the {{Netbeans 11}} available on chocolatey central repo ?
>  
> h1. Resources
>  * Package sources : [https://github.com/adriens/chocolatey-netbeans-11]
>  * Package moderation issue : 
> [https://github.com/chocolatey/chocolatey-package-requests/issues/572]
>  
> Thank you in advance for your help.
>  



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