[jira] [Assigned] (NETBEANS-3847) CLONE - Release installers

2020-02-13 Thread Reema Taneja (Jira)


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

Reema Taneja reassigned NETBEANS-3847:
--

Assignee: Arunava Sinha  (was: Reema Taneja)

> CLONE - Release installers
> --
>
> Key: NETBEANS-3847
> URL: https://issues.apache.org/jira/browse/NETBEANS-3847
> Project: NetBeans
>  Issue Type: Sub-task
>Reporter: Neil C Smith
>Assignee: Arunava Sinha
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-3847) CLONE - Release installers

2020-02-13 Thread Reema Taneja (Jira)


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

Reema Taneja commented on NETBEANS-3847:


Arunava is working on 11.3 installers.

> CLONE - Release installers
> --
>
> Key: NETBEANS-3847
> URL: https://issues.apache.org/jira/browse/NETBEANS-3847
> Project: NetBeans
>  Issue Type: Sub-task
>Reporter: Neil C Smith
>Assignee: Arunava Sinha
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-3768) Library source handling does not handle module-info

2020-02-13 Thread Ernie Rael (Jira)


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

Ernie Rael updated NETBEANS-3768:
-
Labels: javafx  (was: )

> Library source handling does not handle module-info
> ---
>
> Key: NETBEANS-3768
> URL: https://issues.apache.org/jira/browse/NETBEANS-3768
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Project, java - Source
>Affects Versions: 11.3
> Environment: NB-11.3beta1, jdk-13, Win7
>Reporter: Ernie Rael
>Priority: Major
>  Labels: javafx
> Fix For: 11.3
>
>
> After creating a library from javafx-sdk-13.0.2, including source (had to 
> unzip source and add each of the 7 top level zip directories as a folder), 
> almost all import statements are red underlined with an error. From within a 
> javafx source file, "Go To Source", "Go To Declaration" do not work. For 
> example for Label.java there is
> {code:java}
> import javafx.beans.property.ObjectProperty;
> {code}
> in the editor we get the popup error
> {quote}package javafx.beans.property is not visible
>  (package javafx.beans.property is declared in the unnamed module, but module 
> javafx.beans.property does not read it)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-3763) Go To Type fails with Maven artifact source; similar commands like Go To Declaration also fail

2020-02-13 Thread Ernie Rael (Jira)


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

Ernie Rael updated NETBEANS-3763:
-
Labels: javafx  (was: )

> Go To Type fails with Maven artifact source; similar commands like Go To 
> Declaration also fail
> --
>
> Key: NETBEANS-3763
> URL: https://issues.apache.org/jira/browse/NETBEANS-3763
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source, projects - Maven
>Affects Versions: 11.3
> Environment: NB-11.3beta1 running on jdk1,8, Win7, project running on 
> jdk-13.0.2
>Reporter: Ernie Rael
>Priority: Critical
>  Labels: javafx
> Fix For: 11.3
>
>
> {{Starting with JavaFXMavenArchetype from Gluon and some fixup (see 
> NETBEANS-3730 attachemnts), in the projecs window I expanded 
> SimpleProj>Dependencies, selected all the jars, did "Download Sources" 
> action.}}
> {{I can debug step into javafx sources, but stuff like "Go To Type" fail. I 
> see the message }}{{"_Can not open ... (missing source?)_" }} a lot. I 
> The log has stuff like
>  
> {quote}INFO [org.netbeans.api.java.source.ElementHandle]: Resolved type is 
> null for kind = CONSTRUCTOR
>  INFO [org.netbeans.api.java.source.ElementHandle]: Cannot resolve: 
> ElementHandle[kind=CONSTRUCTOR; sigs=javafx.scene.control.Label  
> (Ljava/lang/String;)V ]
>  INFO [org.netbeans.modules.java.classfile.CodeGenerator]: Cannot resolve 
> element: ElementHandle[kind=CONSTRUCTOR; sigs=javafx.scene.control.Label 
>  (Ljava/lang/String;)V ] on classpath: 
> nbjrt:[file:/F:/j/jdk/jdk-13.0.2/!/modules/java.base/;C:\f\j\maven_repository\org\openjfx\javafx-controls\13\javafx-controls-13-win.jar;C:\f\j\maven_repository\org\openjfx\javafx-graphics\13\javafx-graphics-13-win.jar;C:\f\j\maven_repository\org\openjfx\javafx-base\13\javafx-base-13-win.jar;F:\j\nb-stuff\NetBeansProjects\simple-maven-proto\src\main\java;F:\j\nb-stuff\NetBeansProjects\simple-maven-proto\src\main\resources|file:///F:/j/jdk/jdk-13.0.2/!/modules/java.base/;C:fjmaven_repositoryorgopenjfxjavafx-controls13javafx-controls-13-win.jar;C:fjmaven_repositoryorgopenjfxjavafx-graphics13javafx-graphics-13-win.jar;C:fjmaven_repositoryorgopenjfxjavafx-base13javafx-base-13-win.jar;F:jnb-stuffNetBeansProjectssimple-maven-protosrcmainjava;F:jnb-stuffNetBeansProjectssimple-maven-protosrcmainresources]
>  INFO [org.netbeans.api.java.source.ElementHandle]: Resolved type is null for 
> kind = METHOD
>  INFO [org.netbeans.api.java.source.ElementHandle]: Cannot resolve: 
> ElementHandle[kind=METHOD; sigs=javafx.stage.Stage setScene 
> (Ljavafx/scene/Scene;)V ]
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Created] (NETBEANS-3879) FlatLaf Dark/Light Ctrl+PAGE_UP and Ctrl+PAGE_DOWN not work

2020-02-13 Thread Philippe FICHET (Jira)
Philippe FICHET created NETBEANS-3879:
-

 Summary: FlatLaf Dark/Light Ctrl+PAGE_UP and Ctrl+PAGE_DOWN not 
work
 Key: NETBEANS-3879
 URL: https://issues.apache.org/jira/browse/NETBEANS-3879
 Project: NetBeans
  Issue Type: Bug
  Components: FlatLaf
Affects Versions: 11.3
 Environment: Product Version: Apache NetBeans IDE 11.3-beta2
Java: 13.0.2; OpenJDK 64-Bit Server VM 13.0.2+8
Runtime: OpenJDK Runtime Environment 13.0.2+8
System: Windows 10 version 10.0 running on amd64; Cp1252; fr_FR (nb)
Reporter: Philippe FICHET


Keymap Ctrl+PAGE_UP and Ctrl+PAGE_DOWN not work on FlatLaf Dark and Light but 
work on other Laf (Nimbus, Dark Nimbus, ...).

By default Ctrl+PAGE_UP and Ctrl+PAGE_DOWN are mapped to "Previous Tab" and 
"Next Tab".

When I change keymap "Previous Tab" to Ctrl+NUMPAD1 and "Next Tab" to 
Ctrl+NUMPAD2, keymap work.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-3871) Gradle TestNG test results "go to source" not working

2020-02-13 Thread cda (Jira)


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

cda commented on NETBEANS-3871:
---

Tests are run by right clicking the subproject -> Test

> Gradle TestNG test results "go to source" not working
> -
>
> Key: NETBEANS-3871
> URL: https://issues.apache.org/jira/browse/NETBEANS-3871
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.2
>Reporter: cda
>Assignee: Laszlo Kishalmi
>Priority: Major
>
> In "Output" window, the failed test is displayed:
> {noformat}
> UnitTestSuite > UnitTest > proj.shop.ShopsControllerTest > testGetOk FAILED
> org.springframework.web.util.NestedServletException at 
> ShopsControllerTest.java:29
> Caused by: java.util.NoSuchElementException at 
> ShopsControllerTest.java:29{noformat}
> The "Test Results" window correctly shows failed tests, but right clicking -> 
> "Go to Source" does nothing.
> Tests are run in a gradle subproject.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-3871) Gradle TestNG test results "go to source" not working

2020-02-13 Thread Laszlo Kishalmi (Jira)


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

Laszlo Kishalmi commented on NETBEANS-3871:
---

What happens if you run those test within the subproject itself?

> Gradle TestNG test results "go to source" not working
> -
>
> Key: NETBEANS-3871
> URL: https://issues.apache.org/jira/browse/NETBEANS-3871
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.2
>Reporter: cda
>Priority: Major
>
> In "Output" window, the failed test is displayed:
> {noformat}
> UnitTestSuite > UnitTest > proj.shop.ShopsControllerTest > testGetOk FAILED
> org.springframework.web.util.NestedServletException at 
> ShopsControllerTest.java:29
> Caused by: java.util.NoSuchElementException at 
> ShopsControllerTest.java:29{noformat}
> The "Test Results" window correctly shows failed tests, but right clicking -> 
> "Go to Source" does nothing.
> Tests are run in a gradle subproject.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Assigned] (NETBEANS-3871) Gradle TestNG test results "go to source" not working

2020-02-13 Thread Laszlo Kishalmi (Jira)


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

Laszlo Kishalmi reassigned NETBEANS-3871:
-

Assignee: Laszlo Kishalmi

> Gradle TestNG test results "go to source" not working
> -
>
> Key: NETBEANS-3871
> URL: https://issues.apache.org/jira/browse/NETBEANS-3871
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.2
>Reporter: cda
>Assignee: Laszlo Kishalmi
>Priority: Major
>
> In "Output" window, the failed test is displayed:
> {noformat}
> UnitTestSuite > UnitTest > proj.shop.ShopsControllerTest > testGetOk FAILED
> org.springframework.web.util.NestedServletException at 
> ShopsControllerTest.java:29
> Caused by: java.util.NoSuchElementException at 
> ShopsControllerTest.java:29{noformat}
> The "Test Results" window correctly shows failed tests, but right clicking -> 
> "Go to Source" does nothing.
> Tests are run in a gradle subproject.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-3871) Gradle TestNG test results "go to source" not working

2020-02-13 Thread Laszlo Kishalmi (Jira)


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

Laszlo Kishalmi updated NETBEANS-3871:
--
Component/s: projects - Gradle

> Gradle TestNG test results "go to source" not working
> -
>
> Key: NETBEANS-3871
> URL: https://issues.apache.org/jira/browse/NETBEANS-3871
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.2
>Reporter: cda
>Priority: Major
>
> In "Output" window, the failed test is displayed:
> {noformat}
> UnitTestSuite > UnitTest > proj.shop.ShopsControllerTest > testGetOk FAILED
> org.springframework.web.util.NestedServletException at 
> ShopsControllerTest.java:29
> Caused by: java.util.NoSuchElementException at 
> ShopsControllerTest.java:29{noformat}
> The "Test Results" window correctly shows failed tests, but right clicking -> 
> "Go to Source" does nothing.
> Tests are run in a gradle subproject.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-3744) NetBeans should load multi-project gradle projects in one shot

2020-02-13 Thread Shevek (Jira)


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

Shevek updated NETBEANS-3744:
-
Attachment: visualvm-gradle-netbeans-611.png

> NetBeans should load multi-project gradle projects in one shot
> --
>
> Key: NETBEANS-3744
> URL: https://issues.apache.org/jira/browse/NETBEANS-3744
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.1, 11.2
> Environment: Gradle 5.6 definitely exhibits this. Haven't tried 6.x 
> yet.
> I think Gradle 4.10.3 did not have the issue, but we didn't have 100 
> subprojects and/or use a shared build cache back then either.
>Reporter: Shevek
>Priority: Major
> Attachments: nb-gradle-class-stats.png, 
> nb-gradle-recovery-weirdness.png, netbeans-gradle-out-of-memory.png, 
> visualvm-gradle-netbeans-611.png
>
>
> It appears that NB does a gradle "build" (model, whatever) per subproject in 
> a multi module project. Given a project with say 100 subprojects, two things 
> happen:
> 1. It takes FOREVER, because 100 invocations of gradle takes FOREVER.
> 2. It never completes, because after 30 or 40 projects, Gradle runs out of 
> RAM, and the Gradle JVM goes into GC Ergonomics while holding various 
> system-wide Gradle locks, and now the entire system is hung and NO Gradle 
> invocation on that system can proceed.
> Please can NetBeans load this project-set in one bite, with a single 
> invocation, from which it can get all the model data (like it used to with 
> the old Gradle plugin)?
> This is the major reason why NetBeans takes such a long time to load, and 
> frequently, when it detects file changes, I can only get NB to be usable 
> again by restarting it.
> I already gave Gradle 10Gb of RAM; the project is definitely buildable and 
> testable in 2Gb, the rest is caches/leaks/whatever, that's Gradle's proble 
> but it's vastly exacerbated by the NB Gradle model-loading strategy.
> Related: NETBEANS-3041 which at least gives me the 10Gb. Before that, I think 
> NB just used to crash.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-3744) NetBeans should load multi-project gradle projects in one shot

2020-02-13 Thread Shevek (Jira)


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

Shevek commented on NETBEANS-3744:
--

 !visualvm-gradle-netbeans-611.png! 

> NetBeans should load multi-project gradle projects in one shot
> --
>
> Key: NETBEANS-3744
> URL: https://issues.apache.org/jira/browse/NETBEANS-3744
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.1, 11.2
> Environment: Gradle 5.6 definitely exhibits this. Haven't tried 6.x 
> yet.
> I think Gradle 4.10.3 did not have the issue, but we didn't have 100 
> subprojects and/or use a shared build cache back then either.
>Reporter: Shevek
>Priority: Major
> Attachments: nb-gradle-class-stats.png, 
> nb-gradle-recovery-weirdness.png, netbeans-gradle-out-of-memory.png, 
> visualvm-gradle-netbeans-611.png
>
>
> It appears that NB does a gradle "build" (model, whatever) per subproject in 
> a multi module project. Given a project with say 100 subprojects, two things 
> happen:
> 1. It takes FOREVER, because 100 invocations of gradle takes FOREVER.
> 2. It never completes, because after 30 or 40 projects, Gradle runs out of 
> RAM, and the Gradle JVM goes into GC Ergonomics while holding various 
> system-wide Gradle locks, and now the entire system is hung and NO Gradle 
> invocation on that system can proceed.
> Please can NetBeans load this project-set in one bite, with a single 
> invocation, from which it can get all the model data (like it used to with 
> the old Gradle plugin)?
> This is the major reason why NetBeans takes such a long time to load, and 
> frequently, when it detects file changes, I can only get NB to be usable 
> again by restarting it.
> I already gave Gradle 10Gb of RAM; the project is definitely buildable and 
> testable in 2Gb, the rest is caches/leaks/whatever, that's Gradle's proble 
> but it's vastly exacerbated by the NB Gradle model-loading strategy.
> Related: NETBEANS-3041 which at least gives me the 10Gb. Before that, I think 
> NB just used to crash.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-3744) NetBeans should load multi-project gradle projects in one shot

2020-02-13 Thread Shevek (Jira)


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

Shevek commented on NETBEANS-3744:
--

 !visualvm-gradle-netbeans-611.png! 

For the record. Gradle 6.1.1 with NB11.2 has the same issue. Looks like some 
sort of 10 minute timeout on a cache within Gradle, as the memory is clearly 
cleanly released after spending 10 mins in ergonomics.

> NetBeans should load multi-project gradle projects in one shot
> --
>
> Key: NETBEANS-3744
> URL: https://issues.apache.org/jira/browse/NETBEANS-3744
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.1, 11.2
> Environment: Gradle 5.6 definitely exhibits this. Haven't tried 6.x 
> yet.
> I think Gradle 4.10.3 did not have the issue, but we didn't have 100 
> subprojects and/or use a shared build cache back then either.
>Reporter: Shevek
>Priority: Major
> Attachments: nb-gradle-class-stats.png, 
> nb-gradle-recovery-weirdness.png, netbeans-gradle-out-of-memory.png
>
>
> It appears that NB does a gradle "build" (model, whatever) per subproject in 
> a multi module project. Given a project with say 100 subprojects, two things 
> happen:
> 1. It takes FOREVER, because 100 invocations of gradle takes FOREVER.
> 2. It never completes, because after 30 or 40 projects, Gradle runs out of 
> RAM, and the Gradle JVM goes into GC Ergonomics while holding various 
> system-wide Gradle locks, and now the entire system is hung and NO Gradle 
> invocation on that system can proceed.
> Please can NetBeans load this project-set in one bite, with a single 
> invocation, from which it can get all the model data (like it used to with 
> the old Gradle plugin)?
> This is the major reason why NetBeans takes such a long time to load, and 
> frequently, when it detects file changes, I can only get NB to be usable 
> again by restarting it.
> I already gave Gradle 10Gb of RAM; the project is definitely buildable and 
> testable in 2Gb, the rest is caches/leaks/whatever, that's Gradle's proble 
> but it's vastly exacerbated by the NB Gradle model-loading strategy.
> Related: NETBEANS-3041 which at least gives me the 10Gb. Before that, I think 
> NB just used to crash.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-3878) Test results missing tests

2020-02-13 Thread cda (Jira)


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

cda commented on NETBEANS-3878:
---

May be related to issue NETBEANS-3871 where "go to source" is bugged.

> Test results missing tests
> --
>
> Key: NETBEANS-3878
> URL: https://issues.apache.org/jira/browse/NETBEANS-3878
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - TestNG, projects - Gradle
>Affects Versions: 11.2
> Environment: TestNg
> Gradle
>Reporter: cda
>Assignee: Laszlo Kishalmi
>Priority: Major
>
> After running testng gradle tests, the "Test Results" window shows incorrect 
> results.
> In the "Output" window it prints:
>  
> {code:java}
> 4161 tests completed, 33 failed
> > Task :backend:server:test FAILED
> {code}
> but the "Test Results" window shows "2.838 tests passed, 18 tests failed. 
> (6676,167 s).
> Note that the testng report shows also 4161 tests, 33 failures.
>  
>  
> Output:
> > Task :backend:server:test
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access using Lookup on 
> org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor 
> (file:/C:/Users/Alex/.gradle/caches/modules-2/files-2.1/org.aspectj/aspectjweaver/1.9.4/9205229878f3d62fbd3a32a0fb6be2d6ad8589a9/aspectjweaver-1.9.4.jar)
>  to class java.lang.ClassLoader
> WARNING: Please consider reporting this to the maintainers of 
> org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [AppClassLoader@299a06ac] warning javax.* types are not being woven because 
> the weaver option '-Xset:weaveJavaxPackages=true' has not been specified
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at PriceTokenAssemblerTest.java:97
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at PriceTokenAssemblerTest.java:97
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at PriceTokenParserTest.java:82
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at PriceTokenParserTest.java:82
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at PriceTokenParserTest.java:82
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:534
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:562
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:576
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:478
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:478
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:478
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:478
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:478
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:478
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:478
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:478
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:478
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:478
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:478
> UnitTestSuite > UnitTest > ... FAILED
>  org.mockito.exceptions.verification.NeverWantedButInvoked at 
> FiltersTest.java:45
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at KeyValueSplitterPostprocessorTest.java:54
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ColorPropertyTypeTest.java:37
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at ProductPropertyParserTest.java:489
> UnitTestSuite > UnitTest > ... FAILED
>  org.springframework.web.util.NestedServletException at 
> ShopsControllerTest.java:29
>  Caused by: java.util.NoSuchElementException at ShopsControllerTest.java:29
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at FtsUtilsTest.java:35
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at FtsUtilsTest.java:50
> UnitTestSuite > UnitTest > ... FAILED
>  java.lang.AssertionError at CategoryFilterTest.java:162
> UnitTestSuite > UnitTest > ... FAILED
>  

[jira] [Updated] (NETBEANS-3878) Test results missing tests

2020-02-13 Thread cda (Jira)


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

cda updated NETBEANS-3878:
--
Description: 
After running testng gradle tests, the "Test Results" window shows incorrect 
results.

In the "Output" window it prints:

 
{code:java}
4161 tests completed, 33 failed
> Task :backend:server:test FAILED
{code}
but the "Test Results" window shows "2.838 tests passed, 18 tests failed. 
(6676,167 s).

Note that the testng report shows also 4161 tests, 33 failures.

 

 

Output:

> Task :backend:server:test
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access using Lookup on 
org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor 
(file:/C:/Users/Alex/.gradle/caches/modules-2/files-2.1/org.aspectj/aspectjweaver/1.9.4/9205229878f3d62fbd3a32a0fb6be2d6ad8589a9/aspectjweaver-1.9.4.jar)
 to class java.lang.ClassLoader
WARNING: Please consider reporting this to the maintainers of 
org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[AppClassLoader@299a06ac] warning javax.* types are not being woven because the 
weaver option '-Xset:weaveJavaxPackages=true' has not been specified

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at PriceTokenAssemblerTest.java:97

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at PriceTokenAssemblerTest.java:97

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at PriceTokenParserTest.java:82

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at PriceTokenParserTest.java:82

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at PriceTokenParserTest.java:82

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:534

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:562

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:576

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:478

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:478

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:478

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:478

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:478

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:478

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:478

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:478

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:478

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:478

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:478

UnitTestSuite > UnitTest > ... FAILED
 org.mockito.exceptions.verification.NeverWantedButInvoked at 
FiltersTest.java:45

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at KeyValueSplitterPostprocessorTest.java:54

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ColorPropertyTypeTest.java:37

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at ProductPropertyParserTest.java:489

UnitTestSuite > UnitTest > ... FAILED
 org.springframework.web.util.NestedServletException at 
ShopsControllerTest.java:29
 Caused by: java.util.NoSuchElementException at ShopsControllerTest.java:29

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at FtsUtilsTest.java:35

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at FtsUtilsTest.java:50

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at CategoryFilterTest.java:162

UnitTestSuite > UnitTest > ... FAILED
 java.util.NoSuchElementException at CategoryFilterTest.java:146

UnitTestSuite > UnitTest > ... FAILED
 java.util.NoSuchElementException at CategoryFilterTest.java:115

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at BugReportControllerTest.java:77

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at BugReportControllerTest.java:46

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at PriceHtmlParserTest.java:147

UnitTestSuite > UnitTest > ... FAILED
 java.lang.AssertionError at SecurityTest.java:31
2020-02-13 20:30:58,638 INFO 
org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor 
[SpringContextShutdownHook] Shutting down ExecutorService 

[jira] [Created] (NETBEANS-3878) Test results missing tests

2020-02-13 Thread cda (Jira)
cda created NETBEANS-3878:
-

 Summary: Test results missing tests
 Key: NETBEANS-3878
 URL: https://issues.apache.org/jira/browse/NETBEANS-3878
 Project: NetBeans
  Issue Type: Bug
  Components: java - TestNG, projects - Gradle
Affects Versions: 11.2
 Environment: TestNg
Gradle
Reporter: cda
Assignee: Laszlo Kishalmi


After running testng gradle tests, the "Test Results" window shows incorrect 
results.

In the "Output" window it prints:

 
{code:java}
4161 tests completed, 33 failed
> Task :backend:server:test FAILED
{code}
but the "Test Results" window shows "2.838 tests passed, 18 tests failed. 
(6676,167 s).

Note that the testng report shows also 4161 tests, 33 failures.

 

 

Output:

 
{noformat}
> Task :backend:server:test
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access using Lookup on 
org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor 
(file:/C:/Users/Alex/.gradle/caches/modules-2/files-2.1/org.aspectj/aspectjweaver/1.9.4/9205229878f3d62fbd3a32a0fb6be2d6ad8589a9/aspectjweaver-1.9.4.jar)
 to class java.lang.ClassLoader
WARNING: Please consider reporting this to the maintainers of 
org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[AppClassLoader@299a06ac] warning javax.* types are not being woven because the 
weaver option '-Xset:weaveJavaxPackages=true' has not been 
specifiedUnitTestSuite > UnitTest > ... FAILED
java.lang.AssertionError at PriceTokenAssemblerTest.java:97UnitTestSuite > 
UnitTest > ... FAILED
java.lang.AssertionError at PriceTokenAssemblerTest.java:97UnitTestSuite > 
UnitTest > ... FAILED
java.lang.AssertionError at PriceTokenParserTest.java:82UnitTestSuite > 
UnitTest > ... FAILED
java.lang.AssertionError at PriceTokenParserTest.java:82UnitTestSuite > 
UnitTest > ... FAILED
java.lang.AssertionError at PriceTokenParserTest.java:82UnitTestSuite > 
UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:534UnitTestSuite 
> UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:562UnitTestSuite 
> UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:576UnitTestSuite 
> UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:478UnitTestSuite 
> UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:478UnitTestSuite 
> UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:478UnitTestSuite 
> UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:478UnitTestSuite 
> UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:478UnitTestSuite 
> UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:478UnitTestSuite 
> UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:478UnitTestSuite 
> UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:478UnitTestSuite 
> UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:478UnitTestSuite 
> UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:478UnitTestSuite 
> UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:478UnitTestSuite 
> UnitTest > ... FAILED
org.mockito.exceptions.verification.NeverWantedButInvoked at 
FiltersTest.java:45UnitTestSuite > UnitTest > ... FAILED
java.lang.AssertionError at 
KeyValueSplitterPostprocessorTest.java:54UnitTestSuite > UnitTest > ... FAILED
java.lang.AssertionError at ColorPropertyTypeTest.java:37UnitTestSuite > 
UnitTest > ... FAILED
java.lang.AssertionError at ProductPropertyParserTest.java:489UnitTestSuite 
> UnitTest > ... FAILED
org.springframework.web.util.NestedServletException at 
ShopsControllerTest.java:29
Caused by: java.util.NoSuchElementException at 
ShopsControllerTest.java:29UnitTestSuite > UnitTest > ... FAILED
java.lang.AssertionError at FtsUtilsTest.java:35UnitTestSuite > UnitTest > 
... FAILED
java.lang.AssertionError at FtsUtilsTest.java:50UnitTestSuite > UnitTest > 
... FAILED
java.lang.AssertionError at CategoryFilterTest.java:162UnitTestSuite > 
UnitTest > ... FAILED
java.util.NoSuchElementException at 
CategoryFilterTest.java:146UnitTestSuite > UnitTest > ... FAILED
java.util.NoSuchElementException at 
CategoryFilterTest.java:115UnitTestSuite > UnitTest > ... FAILED
java.lang.AssertionError at BugReportControllerTest.java:77UnitTestSuite > 
UnitTest > ... FAILED
java.lang.AssertionError at 

[jira] [Commented] (NETBEANS-3877) Cannot open url in browser

2020-02-13 Thread cda (Jira)


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

cda commented on NETBEANS-3877:
---

It seems that this is reproductible when I run tests from the root gradle 
project with the Gradle Support Plugin:

*Version:* 2.0.2
*Source:* 1544990439_netbeans-gradle-plugin-2.0.2.nb

I have a gradle project with multiple subprojects.

When running tests from gradle subproject and clicking the link in the output 
window correctly opens the browser.

> Cannot open url in browser
> --
>
> Key: NETBEANS-3877
> URL: https://issues.apache.org/jira/browse/NETBEANS-3877
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.2
>Reporter: cda
>Priority: Major
>
> After running testng tests, in the "Output" window a report is generated with 
> a link (file:///C:\...\index.html").
> Clicking this link shows a warning "Could not access the URL through the 
> external browser. Check the browser configuration."
> I have my web browser configured in Tools -> Options -> General -> Web 
> Brwoser : Firefox.
> Pressing Edit shows browser path "C:\Program Files\Mozilla 
> Firefox\firefox.exe" and arguments "\{URL}".
> Pressing "Test connection" in proxy settings results in green check mark.
> If I try to run the command in a terminal "C:\Program Files\Mozilla 
> Firefox\firefox.exe" file:///C:/.../index.html, the page is correctly opened 
> in browser.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-3871) Gradle TestNG test results "go to source" not working

2020-02-13 Thread cda (Jira)


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

cda commented on NETBEANS-3871:
---

Found other non-working "go to source" test results for a method that fails and 
uses mockito, where the erorr message is like:
{code:java}
org.mockito.exceptions.verification.NeverWantedButInvoked: 
categoryMatchFilter.computeLimits(
,
,

);
Never wanted here:
-> at 
proj.filters.FiltersTest.testSkipSingleActiveComputeLimits_aroundBody0(FiltersTest.java:45)
But invoked here:
-> at 
proj.filters.MultiFilterController.lambda$computeLimits$2(MultiFilterController.java:60)
  at 
proj.filters..FiltersTest.testSkipSingleActiveComputeLimits_aroundBody0(FiltersTest.java:45)
at proj.filters..FiltersTest$AjcClosure1.run(FiltersTest.java:1)
at 
org.springframework.transaction.aspectj.AbstractTransactionAspect.ajc$around$org_springframework_transaction_aspectj_AbstractTransactionAspect$1$2a73e96cproceed(AbstractTransactionAspect.aj:66)

{code}
Possibly the error's message formatting prevents recognizing the source so "go 
to soruce" is not working.

> Gradle TestNG test results "go to source" not working
> -
>
> Key: NETBEANS-3871
> URL: https://issues.apache.org/jira/browse/NETBEANS-3871
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.2
>Reporter: cda
>Priority: Major
>
> In "Output" window, the failed test is displayed:
> {noformat}
> UnitTestSuite > UnitTest > proj.shop.ShopsControllerTest > testGetOk FAILED
> org.springframework.web.util.NestedServletException at 
> ShopsControllerTest.java:29
> Caused by: java.util.NoSuchElementException at 
> ShopsControllerTest.java:29{noformat}
> The "Test Results" window correctly shows failed tests, but right clicking -> 
> "Go to Source" does nothing.
> Tests are run in a gradle subproject.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-3876) Using Groovy in projects is causing java.lang.NoClassDefFoundError

2020-02-13 Thread Benjamin Graf (Jira)


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

Benjamin Graf commented on NETBEANS-3876:
-

Might be linked to https://issues.apache.org/jira/browse/GROOVY-9211

> Using Groovy in projects is causing java.lang.NoClassDefFoundError
> --
>
> Key: NETBEANS-3876
> URL: https://issues.apache.org/jira/browse/NETBEANS-3876
> Project: NetBeans
>  Issue Type: Bug
>  Components: groovy - Editor
>Affects Versions: 11.3
> Environment: Windows 10
> openjdk version "14" 2020-03-17
> OpenJDK Runtime Environment AdoptOpenJDK (build 14+34-202002111235)
> OpenJDK 64-Bit Server VM AdoptOpenJDK (build 14+34-202002111235, mixed mode, 
> sharing)
>Reporter: Benjamin Graf
>Priority: Major
>
> Following Exception is throws in several use cases for projects using groovy 
> files. I can recognize it for following use cases:
> * internal code parsing of editor
> * while "Clean and Build" ant project
> {noformat}
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.codehaus.groovy.vmplugin.v7.Java7
>   at 
> org.codehaus.groovy.vmplugin.VMPluginFactory.(VMPluginFactory.java:43)
>   at org.codehaus.groovy.ast.ClassHelper.makeCached(ClassHelper.java:141)
>   at org.codehaus.groovy.ast.ClassHelper.(ClassHelper.java:77)
>   at org.codehaus.groovy.classgen.Verifier.(Verifier.java:133)
>   at 
> org.codehaus.groovy.control.CompilationUnit.(CompilationUnit.java:170)
>   at 
> org.netbeans.modules.groovy.editor.compiler.CompilationUnit.(CompilationUnit.java:64)
>   at 
> org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parseBuffer(GroovyParser.java:441)
>   at 
> org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parse(GroovyParser.java:137)
>   at 
> org.netbeans.modules.parsing.impl.TaskProcessor.callParse(TaskProcessor.java:598)
>   at 
> org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:228)
>   at 
> org.netbeans.modules.parsing.api.ResultIterator.getParserResult(ResultIterator.java:115)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$2.run(RepositoryUpdater.java:3171)
>   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.modules.parsing.impl.indexing.RepositoryUpdater$Work.indexEmbedding(RepositoryUpdater.java:3143)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doIndex(RepositoryUpdater.java:2862)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.access$800(RepositoryUpdater.java:2154)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2636)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2634)
>   at 
> org.netbeans.modules.parsing.impl.indexing.errors.TaskCache.refreshTransaction(TaskCache.java:540)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.index(RepositoryUpdater.java:2634)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5714)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5622)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$4.run(RepositoryUpdater.java:2127)
>   at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2123)
>   at 
> 

[jira] [Updated] (NETBEANS-3876) Using Groovy in projects is causing java.lang.NoClassDefFoundError

2020-02-13 Thread Benjamin Graf (Jira)


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

Benjamin Graf updated NETBEANS-3876:

Environment: 
Windows 10
openjdk version "14" 2020-03-17
OpenJDK Runtime Environment AdoptOpenJDK (build 14+34-202002111235)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 14+34-202002111235, mixed mode, 
sharing)

> Using Groovy in projects is causing java.lang.NoClassDefFoundError
> --
>
> Key: NETBEANS-3876
> URL: https://issues.apache.org/jira/browse/NETBEANS-3876
> Project: NetBeans
>  Issue Type: Bug
>  Components: groovy - Editor
>Affects Versions: 11.3
> Environment: Windows 10
> openjdk version "14" 2020-03-17
> OpenJDK Runtime Environment AdoptOpenJDK (build 14+34-202002111235)
> OpenJDK 64-Bit Server VM AdoptOpenJDK (build 14+34-202002111235, mixed mode, 
> sharing)
>Reporter: Benjamin Graf
>Priority: Major
>
> Following Exception is throws in several use cases for projects using groovy 
> files. I can recognize it for following use cases:
> * internal code parsing of editor
> * while "Clean and Build" ant project
> {noformat}
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.codehaus.groovy.vmplugin.v7.Java7
>   at 
> org.codehaus.groovy.vmplugin.VMPluginFactory.(VMPluginFactory.java:43)
>   at org.codehaus.groovy.ast.ClassHelper.makeCached(ClassHelper.java:141)
>   at org.codehaus.groovy.ast.ClassHelper.(ClassHelper.java:77)
>   at org.codehaus.groovy.classgen.Verifier.(Verifier.java:133)
>   at 
> org.codehaus.groovy.control.CompilationUnit.(CompilationUnit.java:170)
>   at 
> org.netbeans.modules.groovy.editor.compiler.CompilationUnit.(CompilationUnit.java:64)
>   at 
> org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parseBuffer(GroovyParser.java:441)
>   at 
> org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parse(GroovyParser.java:137)
>   at 
> org.netbeans.modules.parsing.impl.TaskProcessor.callParse(TaskProcessor.java:598)
>   at 
> org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:228)
>   at 
> org.netbeans.modules.parsing.api.ResultIterator.getParserResult(ResultIterator.java:115)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$2.run(RepositoryUpdater.java:3171)
>   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.modules.parsing.impl.indexing.RepositoryUpdater$Work.indexEmbedding(RepositoryUpdater.java:3143)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doIndex(RepositoryUpdater.java:2862)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.access$800(RepositoryUpdater.java:2154)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2636)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2634)
>   at 
> org.netbeans.modules.parsing.impl.indexing.errors.TaskCache.refreshTransaction(TaskCache.java:540)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.index(RepositoryUpdater.java:2634)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5714)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5622)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$4.run(RepositoryUpdater.java:2127)
>   at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
>   at 
> 

[jira] [Updated] (NETBEANS-3876) Using Groovy in projects is causing

2020-02-13 Thread Benjamin Graf (Jira)


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

Benjamin Graf updated NETBEANS-3876:

Summary: Using Groovy in projects is causing   (was: Using Groovy in 
projects causing error)

> Using Groovy in projects is causing 
> 
>
> Key: NETBEANS-3876
> URL: https://issues.apache.org/jira/browse/NETBEANS-3876
> Project: NetBeans
>  Issue Type: Bug
>  Components: groovy - Editor
>Affects Versions: 11.3
>Reporter: Benjamin Graf
>Priority: Major
>
> Following Exception is throws in several use cases for projects using groovy 
> files. I can recognize it for following use cases:
> * internal code parsing of editor
> * while "Clean and Build" ant project
> {noformat}
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.codehaus.groovy.vmplugin.v7.Java7
>   at 
> org.codehaus.groovy.vmplugin.VMPluginFactory.(VMPluginFactory.java:43)
>   at org.codehaus.groovy.ast.ClassHelper.makeCached(ClassHelper.java:141)
>   at org.codehaus.groovy.ast.ClassHelper.(ClassHelper.java:77)
>   at org.codehaus.groovy.classgen.Verifier.(Verifier.java:133)
>   at 
> org.codehaus.groovy.control.CompilationUnit.(CompilationUnit.java:170)
>   at 
> org.netbeans.modules.groovy.editor.compiler.CompilationUnit.(CompilationUnit.java:64)
>   at 
> org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parseBuffer(GroovyParser.java:441)
>   at 
> org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parse(GroovyParser.java:137)
>   at 
> org.netbeans.modules.parsing.impl.TaskProcessor.callParse(TaskProcessor.java:598)
>   at 
> org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:228)
>   at 
> org.netbeans.modules.parsing.api.ResultIterator.getParserResult(ResultIterator.java:115)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$2.run(RepositoryUpdater.java:3171)
>   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.modules.parsing.impl.indexing.RepositoryUpdater$Work.indexEmbedding(RepositoryUpdater.java:3143)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doIndex(RepositoryUpdater.java:2862)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.access$800(RepositoryUpdater.java:2154)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2636)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2634)
>   at 
> org.netbeans.modules.parsing.impl.indexing.errors.TaskCache.refreshTransaction(TaskCache.java:540)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.index(RepositoryUpdater.java:2634)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5714)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5622)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$4.run(RepositoryUpdater.java:2127)
>   at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2123)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2104)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.access$1500(RepositoryUpdater.java:136)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork.scanSource(RepositoryUpdater.java:5749)
>   at 
> 

[jira] [Updated] (NETBEANS-3876) Using Groovy in projects is causing java.lang.NoClassDefFoundError

2020-02-13 Thread Benjamin Graf (Jira)


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

Benjamin Graf updated NETBEANS-3876:

Summary: Using Groovy in projects is causing java.lang.NoClassDefFoundError 
 (was: Using Groovy in projects is causing )

> Using Groovy in projects is causing java.lang.NoClassDefFoundError
> --
>
> Key: NETBEANS-3876
> URL: https://issues.apache.org/jira/browse/NETBEANS-3876
> Project: NetBeans
>  Issue Type: Bug
>  Components: groovy - Editor
>Affects Versions: 11.3
>Reporter: Benjamin Graf
>Priority: Major
>
> Following Exception is throws in several use cases for projects using groovy 
> files. I can recognize it for following use cases:
> * internal code parsing of editor
> * while "Clean and Build" ant project
> {noformat}
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.codehaus.groovy.vmplugin.v7.Java7
>   at 
> org.codehaus.groovy.vmplugin.VMPluginFactory.(VMPluginFactory.java:43)
>   at org.codehaus.groovy.ast.ClassHelper.makeCached(ClassHelper.java:141)
>   at org.codehaus.groovy.ast.ClassHelper.(ClassHelper.java:77)
>   at org.codehaus.groovy.classgen.Verifier.(Verifier.java:133)
>   at 
> org.codehaus.groovy.control.CompilationUnit.(CompilationUnit.java:170)
>   at 
> org.netbeans.modules.groovy.editor.compiler.CompilationUnit.(CompilationUnit.java:64)
>   at 
> org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parseBuffer(GroovyParser.java:441)
>   at 
> org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parse(GroovyParser.java:137)
>   at 
> org.netbeans.modules.parsing.impl.TaskProcessor.callParse(TaskProcessor.java:598)
>   at 
> org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:228)
>   at 
> org.netbeans.modules.parsing.api.ResultIterator.getParserResult(ResultIterator.java:115)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$2.run(RepositoryUpdater.java:3171)
>   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.modules.parsing.impl.indexing.RepositoryUpdater$Work.indexEmbedding(RepositoryUpdater.java:3143)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doIndex(RepositoryUpdater.java:2862)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.access$800(RepositoryUpdater.java:2154)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2636)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2634)
>   at 
> org.netbeans.modules.parsing.impl.indexing.errors.TaskCache.refreshTransaction(TaskCache.java:540)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.index(RepositoryUpdater.java:2634)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5714)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5622)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$4.run(RepositoryUpdater.java:2127)
>   at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2123)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2104)
>   at 
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.access$1500(RepositoryUpdater.java:136)
>   at 
> 

[jira] [Updated] (NETBEANS-3876) Using Groovy in projects causing error

2020-02-13 Thread Benjamin Graf (Jira)


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

Benjamin Graf updated NETBEANS-3876:

Description: 
Following Exception is throws in several use cases for projects using groovy 
files. I can recognize it for following use cases:
* internal code parsing of editor
* while "Clean and Build" ant project

{noformat}
java.lang.NoClassDefFoundError: Could not initialize class 
org.codehaus.groovy.vmplugin.v7.Java7
at 
org.codehaus.groovy.vmplugin.VMPluginFactory.(VMPluginFactory.java:43)
at org.codehaus.groovy.ast.ClassHelper.makeCached(ClassHelper.java:141)
at org.codehaus.groovy.ast.ClassHelper.(ClassHelper.java:77)
at org.codehaus.groovy.classgen.Verifier.(Verifier.java:133)
at 
org.codehaus.groovy.control.CompilationUnit.(CompilationUnit.java:170)
at 
org.netbeans.modules.groovy.editor.compiler.CompilationUnit.(CompilationUnit.java:64)
at 
org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parseBuffer(GroovyParser.java:441)
at 
org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parse(GroovyParser.java:137)
at 
org.netbeans.modules.parsing.impl.TaskProcessor.callParse(TaskProcessor.java:598)
at 
org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:228)
at 
org.netbeans.modules.parsing.api.ResultIterator.getParserResult(ResultIterator.java:115)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$2.run(RepositoryUpdater.java:3171)
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.modules.parsing.impl.indexing.RepositoryUpdater$Work.indexEmbedding(RepositoryUpdater.java:3143)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doIndex(RepositoryUpdater.java:2862)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.access$800(RepositoryUpdater.java:2154)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2636)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2634)
at 
org.netbeans.modules.parsing.impl.indexing.errors.TaskCache.refreshTransaction(TaskCache.java:540)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.index(RepositoryUpdater.java:2634)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5714)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5622)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$4.run(RepositoryUpdater.java:2127)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2123)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2104)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.access$1500(RepositoryUpdater.java:136)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork.scanSource(RepositoryUpdater.java:5749)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork.scanSources(RepositoryUpdater.java:5419)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$RootsWork.getDone(RepositoryUpdater.java:5038)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$InitialRootsWork.getDone(RepositoryUpdater.java:5821)
[catch] at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doTheWork(RepositoryUpdater.java:3420)
at 

[jira] [Created] (NETBEANS-3876) Using Groovy in projects causing error

2020-02-13 Thread Benjamin Graf (Jira)
Benjamin Graf created NETBEANS-3876:
---

 Summary: Using Groovy in projects causing error
 Key: NETBEANS-3876
 URL: https://issues.apache.org/jira/browse/NETBEANS-3876
 Project: NetBeans
  Issue Type: Bug
  Components: groovy - Editor
Affects Versions: 11.3
Reporter: Benjamin Graf


Following Exception is throws in several use cases for projects using groovy 
files. I can recognize it for following use cases:
* internal code parsing of editor
* while "Clean and Build" ant project

{noformat}
java.lang.NoClassDefFoundError: Could not initialize class 
org.codehaus.groovy.vmplugin.v7.Java7
at 
org.codehaus.groovy.vmplugin.VMPluginFactory.(VMPluginFactory.java:43)
at org.codehaus.groovy.ast.ClassHelper.makeCached(ClassHelper.java:141)
at org.codehaus.groovy.ast.ClassHelper.(ClassHelper.java:77)
at org.codehaus.groovy.classgen.Verifier.(Verifier.java:133)
at 
org.codehaus.groovy.control.CompilationUnit.(CompilationUnit.java:170)
at 
org.netbeans.modules.groovy.editor.compiler.CompilationUnit.(CompilationUnit.java:64)
at 
org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parseBuffer(GroovyParser.java:441)
at 
org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parse(GroovyParser.java:137)
at 
org.netbeans.modules.parsing.impl.TaskProcessor.callParse(TaskProcessor.java:598)
at 
org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:228)
at 
org.netbeans.modules.parsing.api.ResultIterator.getParserResult(ResultIterator.java:115)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$2.run(RepositoryUpdater.java:3171)
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.modules.parsing.impl.indexing.RepositoryUpdater$Work.indexEmbedding(RepositoryUpdater.java:3143)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doIndex(RepositoryUpdater.java:2862)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.access$800(RepositoryUpdater.java:2154)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2636)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2634)
at 
org.netbeans.modules.parsing.impl.indexing.errors.TaskCache.refreshTransaction(TaskCache.java:540)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.index(RepositoryUpdater.java:2634)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5714)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5622)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$4.run(RepositoryUpdater.java:2127)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2123)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2104)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.access$1500(RepositoryUpdater.java:136)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork.scanSource(RepositoryUpdater.java:5749)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork.scanSources(RepositoryUpdater.java:5419)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$RootsWork.getDone(RepositoryUpdater.java:5038)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$InitialRootsWork.getDone(RepositoryUpdater.java:5821)

[jira] [Created] (NETBEANS-3877) Cannot open url in browser

2020-02-13 Thread cda (Jira)
cda created NETBEANS-3877:
-

 Summary: Cannot open url in browser
 Key: NETBEANS-3877
 URL: https://issues.apache.org/jira/browse/NETBEANS-3877
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 11.2
Reporter: cda


After running testng tests, in the "Output" window a report is generated with a 
link (file:///C:\...\index.html").

Clicking this link shows a warning "Could not access the URL through the 
external browser. Check the browser configuration."

I have my web browser configured in Tools -> Options -> General -> Web Brwoser 
: Firefox.

Pressing Edit shows browser path "C:\Program Files\Mozilla Firefox\firefox.exe" 
and arguments "\{URL}".

Pressing "Test connection" in proxy settings results in green check mark.

If I try to run the command in a terminal "C:\Program Files\Mozilla 
Firefox\firefox.exe" file:///C:/.../index.html, the page is correctly opened in 
browser.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-3810) Netbeans 11.3 does not report clearly certificate problems downloading javafx and nb-javac

2020-02-13 Thread Michele Costabile (Jira)


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

Michele Costabile updated NETBEANS-3810:

Summary: Netbeans 11.3 does not report clearly certificate problems 
downloading javafx and nb-javac  (was: Netbeans 11.3 beta2 startup infinite 
loop downloading javafx and nb-javac)

> Netbeans 11.3 does not report clearly certificate problems downloading javafx 
> and nb-javac
> --
>
> Key: NETBEANS-3810
> URL: https://issues.apache.org/jira/browse/NETBEANS-3810
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Autoupdate
>Affects Versions: 11.3
> Environment: Windows 2016 server, Intel Xeon, 48G RAM.
> Network includes a proxy server with deep packet inspection and certificate 
> rewriting.
>Reporter: Michele Costabile
>Priority: Blocker
>  Labels: newbie
> Fix For: 11.3
>
> Attachments: Netbeans-11.3_bug.PNG, Netbeans-11.3_plugin-problem.PNG, 
> Netbeans-11.3_plugin.PNG
>
>
> NetBeans cannot get past installation of JavaFX and nb-javac on my 
> installation behind a company firewall. This problem was also in 11.2, but it 
> did not stop the IDE from working. It just kept on quietly asking for 
> nb-javac installation.
> 11.3, on the other hand does not seem to get past this problem. It keeps on 
> asking for installation of javafx and nb-javac and "Loading projects" never 
> comes to an end.
> I tested my proxy setting in options and I have a green light with system 
> settings and also with manual settings.
>  In any case I have never been able to install nb-javac and could not find 
> instructions on how to install manually the plugin.
> Note that my proxy has deep packet inspection and can create problems with 
> certificate verification on SSL.
>  
> EDIT: the request for installation is not an infinite loop. It appears to be 
> once for every open project. Hitting cancel more times, the progress bar in 
> the status bar eventually gets to 100%, but all the projects are reported 
> broken.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-3871) Gradle TestNG test results "go to source" not working

2020-02-13 Thread cda (Jira)


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

cda commented on NETBEANS-3871:
---

Oddly, it seems to be working now.

Only ones that don't work now are "go to source" for test methods with testng's 
*dataProvider* (methods called multiple times with different arguments from the 
dataprovider).

> Gradle TestNG test results "go to source" not working
> -
>
> Key: NETBEANS-3871
> URL: https://issues.apache.org/jira/browse/NETBEANS-3871
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.2
>Reporter: cda
>Priority: Major
>
> In "Output" window, the failed test is displayed:
> {noformat}
> UnitTestSuite > UnitTest > proj.shop.ShopsControllerTest > testGetOk FAILED
> org.springframework.web.util.NestedServletException at 
> ShopsControllerTest.java:29
> Caused by: java.util.NoSuchElementException at 
> ShopsControllerTest.java:29{noformat}
> The "Test Results" window correctly shows failed tests, but right clicking -> 
> "Go to Source" does nothing.
> Tests are run in a gradle subproject.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Created] (NETBEANS-3875) Jersey project creation from archetype fails

2020-02-13 Thread Alessandro Falappa (Jira)
Alessandro Falappa created NETBEANS-3875:


 Summary: Jersey project creation from archetype fails
 Key: NETBEANS-3875
 URL: https://issues.apache.org/jira/browse/NETBEANS-3875
 Project: NetBeans
  Issue Type: Bug
  Components: projects - Maven
Affects Versions: 11.3
Reporter: Alessandro Falappa


# New Project > Java with Maven > Project from Archetype
 # Search for *jersey*
 # Select the first {{jersey-quickstart-archetype}} archetype item (group id: 
{{org.glassfish.jersey.archetypes}} version: {{2.30}})
 # Press _Next_
 # Choose foobar as *Project Name*
 # Fill the other field and choose an empty directory as *Project Location*
 # Press _Finish_

The project generation fails complaining a folder with name foobar exists. An 
empty foobar folder is left in the choosen project location.
{code:java}

Building Maven Stub Project (No POM) 1
>>> 
maven-archetype-plugin:2.4:generate (default-cli) > generate-sources @ 
standalone-pom >>><<< maven-archetype-plugin:2.4:generate (default-cli) < 
generate-sources @ standalone-pom <<<--- maven-archetype-plugin:2.4:generate 
(default-cli) @ standalone-pom ---
Generating project in Batch mode
Archetype defined by properties

Using following parameters for creating project from Old (1.x) Archetype: 
jersey-quickstart-webapp:2.30

Parameter: basedir, Value: C:\Users\falappa\Documents\NetBeansProjects
Parameter: package, Value: af.foobar
Parameter: groupId, Value: af
Parameter: artifactId, Value: foobar
Parameter: packageName, Value: af.foobar
Parameter: version, Value: 1.0-SNAPSHOT

BUILD FAILURE

Total time: 1.484 s
Finished at: 2020-02-13T14:16:58+01:00
Final Memory: 11M/40M

Failed to execute goal 
org.apache.maven.plugins:maven-archetype-plugin:2.4:generate (default-cli) on 
project standalone-pom: Directory foobar already exists - please run from a 
clean directory -> [Help 1]To see the full stack trace of the errors, re-run 
Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.For more 
information about the errors and possible solutions, please read the following 
articles:
[Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException{code}
Probably the Maven from archetype wizard creates the folder prior to maven 
archetype execution.

Not sure if this can be considered a bug in the jersey archetype instead.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Created] (NETBEANS-3874) Error while

2020-02-13 Thread Joao Rodrigues (Jira)
Joao Rodrigues created NETBEANS-3874:


 Summary: Error while 
 Key: NETBEANS-3874
 URL: https://issues.apache.org/jira/browse/NETBEANS-3874
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 11.2
 Environment: mint 19.3 linux
Reporter: Joao Rodrigues
 Attachments: messages.log

Error when hiding parser errors in a blade file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-3873) Hardcoded color in New Project from Maven Archetype

2020-02-13 Thread Alessandro Falappa (Jira)


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

Alessandro Falappa updated NETBEANS-3873:
-
Description: 
In step 2 of _New Project from Maven Archetype_ the description text area has 
probably an hardcoded white background, the description text is barely visible 
in dark LAFs like FlatDark:

!image-2020-02-13-13-43-28-516.png!

  was:
In step 2 of _New Project from Maven Archetype_ the description text area has 
probably an hardcoded white background.

The description text is barely visible in dark LAFs like FlatDark:

!image-2020-02-13-13-43-28-516.png!


> Hardcoded color in New Project from Maven Archetype
> ---
>
> Key: NETBEANS-3873
> URL: https://issues.apache.org/jira/browse/NETBEANS-3873
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Maven
>Affects Versions: 11.3
>Reporter: Alessandro Falappa
>Priority: Minor
> Attachments: image-2020-02-13-13-43-28-516.png
>
>
> In step 2 of _New Project from Maven Archetype_ the description text area has 
> probably an hardcoded white background, the description text is barely 
> visible in dark LAFs like FlatDark:
> !image-2020-02-13-13-43-28-516.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-3873) Hardcoded color in New Project from Maven Archetype

2020-02-13 Thread Alessandro Falappa (Jira)


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

Alessandro Falappa updated NETBEANS-3873:
-
Attachment: (was: bug-maven-archetype.png)

> Hardcoded color in New Project from Maven Archetype
> ---
>
> Key: NETBEANS-3873
> URL: https://issues.apache.org/jira/browse/NETBEANS-3873
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Maven
>Affects Versions: 11.3
>Reporter: Alessandro Falappa
>Priority: Minor
> Attachments: image-2020-02-13-13-43-28-516.png
>
>
> In step 2 of _New Project from Maven Archetype_ the description text area has 
> probably an hardcoded white background.
> The description text is barely visible in dark LAFs like FlatDark:
> !image-2020-02-13-13-43-28-516.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-3873) Hardcoded color in New Project from Maven Archetype

2020-02-13 Thread Alessandro Falappa (Jira)


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

Alessandro Falappa updated NETBEANS-3873:
-
Description: 
In step 2 of _New Project from Maven Archetype_ the description text area has 
probably an hardcoded white background.

The description text is barely visible in dark LAFs like FlatDark:

!image-2020-02-13-13-43-28-516.png!

  was:
In step 2 of _New Project from Maven Archetype_ the description text area has 
probably an hardcoded white background.

The description text is barely visible in dark LAFs like FlatDark, see 
attachment.


> Hardcoded color in New Project from Maven Archetype
> ---
>
> Key: NETBEANS-3873
> URL: https://issues.apache.org/jira/browse/NETBEANS-3873
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Maven
>Affects Versions: 11.3
>Reporter: Alessandro Falappa
>Priority: Minor
> Attachments: image-2020-02-13-13-43-28-516.png
>
>
> In step 2 of _New Project from Maven Archetype_ the description text area has 
> probably an hardcoded white background.
> The description text is barely visible in dark LAFs like FlatDark:
> !image-2020-02-13-13-43-28-516.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-3873) Hardcoded color in New Project from Maven Archetype

2020-02-13 Thread Alessandro Falappa (Jira)


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

Alessandro Falappa updated NETBEANS-3873:
-
Attachment: bug-maven-archetype.png

> Hardcoded color in New Project from Maven Archetype
> ---
>
> Key: NETBEANS-3873
> URL: https://issues.apache.org/jira/browse/NETBEANS-3873
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Maven
>Affects Versions: 11.3
>Reporter: Alessandro Falappa
>Priority: Minor
> Attachments: image-2020-02-13-13-43-28-516.png
>
>
> In step 2 of _New Project from Maven Archetype_ the description text area has 
> probably an hardcoded white background.
> The description text is barely visible in dark LAFs like FlatDark, see 
> attachment.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-3873) Hardcoded color in New Project from Maven Archetype

2020-02-13 Thread Alessandro Falappa (Jira)


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

Alessandro Falappa updated NETBEANS-3873:
-
Attachment: image-2020-02-13-13-43-28-516.png

> Hardcoded color in New Project from Maven Archetype
> ---
>
> Key: NETBEANS-3873
> URL: https://issues.apache.org/jira/browse/NETBEANS-3873
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Maven
>Affects Versions: 11.3
>Reporter: Alessandro Falappa
>Priority: Minor
> Attachments: image-2020-02-13-13-43-28-516.png
>
>
> In step 2 of _New Project from Maven Archetype_ the description text area has 
> probably an hardcoded white background.
> The description text is barely visible in dark LAFs like FlatDark, see 
> attachment.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Created] (NETBEANS-3873) Hardcoded color in New Project from Maven Archetype

2020-02-13 Thread Alessandro Falappa (Jira)
Alessandro Falappa created NETBEANS-3873:


 Summary: Hardcoded color in New Project from Maven Archetype
 Key: NETBEANS-3873
 URL: https://issues.apache.org/jira/browse/NETBEANS-3873
 Project: NetBeans
  Issue Type: Bug
  Components: projects - Maven
Affects Versions: 11.3
Reporter: Alessandro Falappa
 Attachments: bug-maven-archetype.png

In step 2 of _New Project from Maven Archetype_ the description text area has 
probably an hardcoded white background.

The description text is barely visible in dark LAFs like FlatDark, see 
attachment.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-3810) Netbeans 11.3 beta2 startup infinite loop downloading javafx and nb-javac

2020-02-13 Thread Michele Costabile (Jira)


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

Michele Costabile updated NETBEANS-3810:

Attachment: Netbeans-11.3_plugin-problem.PNG

> Netbeans 11.3 beta2 startup infinite loop downloading javafx and nb-javac
> -
>
> Key: NETBEANS-3810
> URL: https://issues.apache.org/jira/browse/NETBEANS-3810
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Autoupdate
>Affects Versions: 11.3
> Environment: Windows 2016 server, Intel Xeon, 48G RAM.
> Network includes a proxy server with deep packet inspection and certificate 
> rewriting.
>Reporter: Michele Costabile
>Priority: Blocker
>  Labels: newbie
> Fix For: 11.3
>
> Attachments: Netbeans-11.3_bug.PNG, Netbeans-11.3_plugin-problem.PNG, 
> Netbeans-11.3_plugin.PNG
>
>
> NetBeans cannot get past installation of JavaFX and nb-javac on my 
> installation behind a company firewall. This problem was also in 11.2, but it 
> did not stop the IDE from working. It just kept on quietly asking for 
> nb-javac installation.
> 11.3, on the other hand does not seem to get past this problem. It keeps on 
> asking for installation of javafx and nb-javac and "Loading projects" never 
> comes to an end.
> I tested my proxy setting in options and I have a green light with system 
> settings and also with manual settings.
>  In any case I have never been able to install nb-javac and could not find 
> instructions on how to install manually the plugin.
> Note that my proxy has deep packet inspection and can create problems with 
> certificate verification on SSL.
>  
> EDIT: the request for installation is not an infinite loop. It appears to be 
> once for every open project. Hitting cancel more times, the progress bar in 
> the status bar eventually gets to 100%, but all the projects are reported 
> broken.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-3810) Netbeans 11.3 beta2 startup infinite loop downloading javafx and nb-javac

2020-02-13 Thread Michele Costabile (Jira)


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

Michele Costabile commented on NETBEANS-3810:
-

Update: I tried removing existing projects and creating a new project. I am 
still stuck in the same point, but I have more feedback from NB and it appears 
that it cannot connect to the plugin repository because certificate 
verification fails.

In fact, I was using a machine behind a company proxy with deep inspection and 
certificate rewriting. any connection could not work without importing the 
relevant certificates inside cacerts.

After fixing certificates, I can use NB 11.3 as I was using NB 11.2.

I think that security of the connection to the plugin site has been tightened 
in plugin download in 11.3. Perhaps

1) certificate problems should be reported to the user, so that one can fix the 
trust chain adding the corporate CA to the trusted roots

2) missing JavaFX and nb-javac should not be a blocker for project importing or 
creation

3) if they are, they should be bundled with NB. Developers are not lawyers, or 
it should be stated "some assemply required"and clearer instructions.

> Netbeans 11.3 beta2 startup infinite loop downloading javafx and nb-javac
> -
>
> Key: NETBEANS-3810
> URL: https://issues.apache.org/jira/browse/NETBEANS-3810
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Autoupdate
>Affects Versions: 11.3
> Environment: Windows 2016 server, Intel Xeon, 48G RAM.
> Network includes a proxy server with deep packet inspection and certificate 
> rewriting.
>Reporter: Michele Costabile
>Priority: Blocker
>  Labels: newbie
> Fix For: 11.3
>
> Attachments: Netbeans-11.3_bug.PNG, Netbeans-11.3_plugin-problem.PNG, 
> Netbeans-11.3_plugin.PNG
>
>
> NetBeans cannot get past installation of JavaFX and nb-javac on my 
> installation behind a company firewall. This problem was also in 11.2, but it 
> did not stop the IDE from working. It just kept on quietly asking for 
> nb-javac installation.
> 11.3, on the other hand does not seem to get past this problem. It keeps on 
> asking for installation of javafx and nb-javac and "Loading projects" never 
> comes to an end.
> I tested my proxy setting in options and I have a green light with system 
> settings and also with manual settings.
>  In any case I have never been able to install nb-javac and could not find 
> instructions on how to install manually the plugin.
> Note that my proxy has deep packet inspection and can create problems with 
> certificate verification on SSL.
>  
> EDIT: the request for installation is not an infinite loop. It appears to be 
> once for every open project. Hitting cancel more times, the progress bar in 
> the status bar eventually gets to 100%, but all the projects are reported 
> broken.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-3810) Netbeans 11.3 beta2 startup infinite loop downloading javafx and nb-javac

2020-02-13 Thread Michele Costabile (Jira)


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

Michele Costabile updated NETBEANS-3810:

Attachment: Netbeans-11.3_bug.PNG

> Netbeans 11.3 beta2 startup infinite loop downloading javafx and nb-javac
> -
>
> Key: NETBEANS-3810
> URL: https://issues.apache.org/jira/browse/NETBEANS-3810
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Autoupdate
>Affects Versions: 11.3
> Environment: Windows 2016 server, Intel Xeon, 48G RAM.
> Network includes a proxy server with deep packet inspection and certificate 
> rewriting.
>Reporter: Michele Costabile
>Priority: Blocker
>  Labels: newbie
> Fix For: 11.3
>
> Attachments: Netbeans-11.3_bug.PNG, Netbeans-11.3_plugin.PNG
>
>
> NetBeans cannot get past installation of JavaFX and nb-javac on my 
> installation behind a company firewall. This problem was also in 11.2, but it 
> did not stop the IDE from working. It just kept on quietly asking for 
> nb-javac installation.
> 11.3, on the other hand does not seem to get past this problem. It keeps on 
> asking for installation of javafx and nb-javac and "Loading projects" never 
> comes to an end.
> I tested my proxy setting in options and I have a green light with system 
> settings and also with manual settings.
>  In any case I have never been able to install nb-javac and could not find 
> instructions on how to install manually the plugin.
> Note that my proxy has deep packet inspection and can create problems with 
> certificate verification on SSL.
>  
> EDIT: the request for installation is not an infinite loop. It appears to be 
> once for every open project. Hitting cancel more times, the progress bar in 
> the status bar eventually gets to 100%, but all the projects are reported 
> broken.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-3810) Netbeans 11.3 beta2 startup infinite loop downloading javafx and nb-javac

2020-02-13 Thread Michele Costabile (Jira)


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

Michele Costabile commented on NETBEANS-3810:
-

I have tried resetting Netbeans preferences, but I have not yet been able to 
reopen my projects.
 * All the projects are reported broken
 * For every project I have a dialog box during startup asking for installation 
of java-fx and nb-javac. I do not use JavaFX and my JDK in etc/netbeans.conf is 
OpenJDK 11.2
 * After opening the projects, Netbeans reports every project broken.

In other words, I cannot use beta2.

I might try to close my projects and reopen them. I wonder if I could do it 
without breaking my production setup with NB 11.2.

This bug is a blocker

> Netbeans 11.3 beta2 startup infinite loop downloading javafx and nb-javac
> -
>
> Key: NETBEANS-3810
> URL: https://issues.apache.org/jira/browse/NETBEANS-3810
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Autoupdate
>Affects Versions: 11.3
> Environment: Windows 2016 server, Intel Xeon, 48G RAM.
> Network includes a proxy server with deep packet inspection and certificate 
> rewriting.
>Reporter: Michele Costabile
>Priority: Blocker
>  Labels: newbie
> Fix For: 11.3
>
> Attachments: Netbeans-11.3_bug.PNG, Netbeans-11.3_plugin.PNG
>
>
> NetBeans cannot get past installation of JavaFX and nb-javac on my 
> installation behind a company firewall. This problem was also in 11.2, but it 
> did not stop the IDE from working. It just kept on quietly asking for 
> nb-javac installation.
> 11.3, on the other hand does not seem to get past this problem. It keeps on 
> asking for installation of javafx and nb-javac and "Loading projects" never 
> comes to an end.
> I tested my proxy setting in options and I have a green light with system 
> settings and also with manual settings.
>  In any case I have never been able to install nb-javac and could not find 
> instructions on how to install manually the plugin.
> Note that my proxy has deep packet inspection and can create problems with 
> certificate verification on SSL.
>  
> EDIT: the request for installation is not an infinite loop. It appears to be 
> once for every open project. Hitting cancel more times, the progress bar in 
> the status bar eventually gets to 100%, but all the projects are reported 
> broken.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-3810) Netbeans 11.3 beta2 startup infinite loop downloading javafx and nb-javac

2020-02-13 Thread Michele Costabile (Jira)


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

Michele Costabile updated NETBEANS-3810:

Priority: Blocker  (was: Major)

> Netbeans 11.3 beta2 startup infinite loop downloading javafx and nb-javac
> -
>
> Key: NETBEANS-3810
> URL: https://issues.apache.org/jira/browse/NETBEANS-3810
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Autoupdate
>Affects Versions: 11.3
> Environment: Windows 2016 server, Intel Xeon, 48G RAM.
> Network includes a proxy server with deep packet inspection and certificate 
> rewriting.
>Reporter: Michele Costabile
>Priority: Blocker
>  Labels: newbie
> Fix For: 11.3
>
> Attachments: Netbeans-11.3_plugin.PNG
>
>
> NetBeans cannot get past installation of JavaFX and nb-javac on my 
> installation behind a company firewall. This problem was also in 11.2, but it 
> did not stop the IDE from working. It just kept on quietly asking for 
> nb-javac installation.
> 11.3, on the other hand does not seem to get past this problem. It keeps on 
> asking for installation of javafx and nb-javac and "Loading projects" never 
> comes to an end.
> I tested my proxy setting in options and I have a green light with system 
> settings and also with manual settings.
>  In any case I have never been able to install nb-javac and could not find 
> instructions on how to install manually the plugin.
> Note that my proxy has deep packet inspection and can create problems with 
> certificate verification on SSL.
>  
> EDIT: the request for installation is not an infinite loop. It appears to be 
> once for every open project. Hitting cancel more times, the progress bar in 
> the status bar eventually gets to 100%, but all the projects are reported 
> broken.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-2457) Error hint to fix the '--enable-preview' features in Java Application

2020-02-13 Thread Arunava Sinha (Jira)


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

Arunava Sinha updated NETBEANS-2457:

 Attachment: enable-preview.png
Description: 
!enable-preview.png! Suppose we had used switch-expression in Java application 
(JDK-12)

e.g.,

int a = switch (num)

{      case 1 ->1;     default->2; }

;

It will show the below error:

switch expressions are a preview feature and are disabled by default.
 (use --enable-preview to enable switch expressions)

 

NetBeans doesn't provide the fix.

Currently manually need to add '--enable-preview" in build configuration file .

  was:
Suppose we had used switch-expression in Java application (JDK-12)

e.g.,

int a = switch (num)

{      case 1 ->1;     default->2; }

;

It will show the below error:

switch expressions are a preview feature and are disabled by default.
 (use --enable-preview to enable switch expressions)

 

NetBeans doesn't provide the fix.

Currently manually need to add '--enable-preview" in build configuration file .


> Error hint to fix the '--enable-preview' features in  Java Application
> --
>
> Key: NETBEANS-2457
> URL: https://issues.apache.org/jira/browse/NETBEANS-2457
> Project: NetBeans
>  Issue Type: Improvement
>Reporter: ARUNAVA SINHA
>Assignee: ARUNAVA SINHA
>Priority: Major
>  Labels: pull-request-available
> Fix For: 11.1
>
> Attachments: enable-preview.png, plugin-addition-in-pom.png, 
> run-config-changes.png
>
>  Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> !enable-preview.png! Suppose we had used switch-expression in Java 
> application (JDK-12)
> e.g.,
> int a = switch (num)
> {      case 1 ->1;     default->2; }
> ;
> It will show the below error:
> switch expressions are a preview feature and are disabled by default.
>  (use --enable-preview to enable switch expressions)
>  
> NetBeans doesn't provide the fix.
> Currently manually need to add '--enable-preview" in build configuration file 
> .



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-2457) Error hint to fix the '--enable-preview' features in Java Application

2020-02-13 Thread Arunava Sinha (Jira)


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

Arunava Sinha updated NETBEANS-2457:

Attachment: run-config-changes.png

!run-config-changes.png!

> Error hint to fix the '--enable-preview' features in  Java Application
> --
>
> Key: NETBEANS-2457
> URL: https://issues.apache.org/jira/browse/NETBEANS-2457
> Project: NetBeans
>  Issue Type: Improvement
>Reporter: ARUNAVA SINHA
>Assignee: ARUNAVA SINHA
>Priority: Major
>  Labels: pull-request-available
> Fix For: 11.1
>
> Attachments: enable-preview.png, plugin-addition-in-pom.png, 
> run-config-changes.png
>
>  Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Suppose we had used switch-expression in Java application (JDK-12)
> e.g.,
> int a = switch (num)
> {      case 1 ->1;     default->2; }
> ;
> It will show the below error:
> switch expressions are a preview feature and are disabled by default.
>  (use --enable-preview to enable switch expressions)
>  
> NetBeans doesn't provide the fix.
> Currently manually need to add '--enable-preview" in build configuration file 
> .



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Updated] (NETBEANS-2457) Error hint to fix the '--enable-preview' features in Java Application

2020-02-13 Thread Arunava Sinha (Jira)


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

Arunava Sinha updated NETBEANS-2457:

Attachment: plugin-addition-in-pom.png

!plugin-addition-in-pom.png!

> Error hint to fix the '--enable-preview' features in  Java Application
> --
>
> Key: NETBEANS-2457
> URL: https://issues.apache.org/jira/browse/NETBEANS-2457
> Project: NetBeans
>  Issue Type: Improvement
>Reporter: ARUNAVA SINHA
>Assignee: ARUNAVA SINHA
>Priority: Major
>  Labels: pull-request-available
> Fix For: 11.1
>
> Attachments: plugin-addition-in-pom.png
>
>  Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Suppose we had used switch-expression in Java application (JDK-12)
> e.g.,
> int a = switch (num)
> {      case 1 ->1;     default->2; }
> ;
> It will show the below error:
> switch expressions are a preview feature and are disabled by default.
>  (use --enable-preview to enable switch expressions)
>  
> NetBeans doesn't provide the fix.
> Currently manually need to add '--enable-preview" in build configuration file 
> .



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-2457) Error hint to fix the '--enable-preview' features in Java Application

2020-02-13 Thread Arunava Sinha (Jira)


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

Arunava Sinha commented on NETBEANS-2457:
-

On use of enable-preview hint in maven project, below changes will happen
 # in pom.xml it will add  a plugin "maven-compiler-plugin" with enable preview 
as parameter
 # in run config "--enable-preview" vm parameter will be added

Please see the attached screenshots for details wherein  Text-Block is used as 
an example in JDK-14 NB run-time

> Error hint to fix the '--enable-preview' features in  Java Application
> --
>
> Key: NETBEANS-2457
> URL: https://issues.apache.org/jira/browse/NETBEANS-2457
> Project: NetBeans
>  Issue Type: Improvement
>Reporter: ARUNAVA SINHA
>Assignee: ARUNAVA SINHA
>Priority: Major
>  Labels: pull-request-available
> Fix For: 11.1
>
>  Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Suppose we had used switch-expression in Java application (JDK-12)
> e.g.,
> int a = switch (num)
> {      case 1 ->1;     default->2; }
> ;
> It will show the below error:
> switch expressions are a preview feature and are disabled by default.
>  (use --enable-preview to enable switch expressions)
>  
> NetBeans doesn't provide the fix.
> Currently manually need to add '--enable-preview" in build configuration file 
> .



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Created] (NETBEANS-3872) Exception preventing me to use latest builds

2020-02-13 Thread Alessandro Polverini (Jira)
Alessandro Polverini created NETBEANS-3872:
--

 Summary: Exception preventing me to use latest builds
 Key: NETBEANS-3872
 URL: https://issues.apache.org/jira/browse/NETBEANS-3872
 Project: NetBeans
  Issue Type: Bug
  Components: ide - UI
Affects Versions: Next
 Environment: jdk 11, ubuntu Eoan
Reporter: Alessandro Polverini


As soon as I fire up netbeans (after deleting the cache) if I move around in 
the sources I get those errors continuosly rendering me unable to use the IDE.

I've seen them consistently since latest stable builds.

This log is from build#1495

---
>Log Session: Thursday, February 13, 2020 at 9:33:37 AM Central European 
>Standard Time
>System Info: 
  Product Version = Apache NetBeans IDE DEV (Build 
dev-e198d0dade337c1dbc27adbbdfd5d12f621a7712)
  Operating System= Linux version 5.3.0-29-generic running on amd64
  Java; VM; Vendor= 11.0.6; OpenJDK 64-Bit Server VM 
11.0.6+10-post-Ubuntu-1ubuntu119.10.1; Ubuntu
  Runtime = OpenJDK Runtime Environment 
11.0.6+10-post-Ubuntu-1ubuntu119.10.1
  Java Home   = /usr/lib/jvm/java-11-openjdk-amd64
  System Locale; Encoding = it_IT (nb); UTF-8
  Home Directory  = /home/dusty
  Current Directory   = /home/dusty
  User Directory  = /home/dusty/.netbeans/dev
  Cache Directory = /home/dusty/.cache/netbeans/dev
  Installation= /home/sw/netbeans-dev/nb
/home/sw/netbeans-dev/ergonomics
/home/sw/netbeans-dev/ide
/home/sw/netbeans-dev/extide
/home/sw/netbeans-dev/java
/home/sw/netbeans-dev/apisupport
/home/sw/netbeans-dev/webcommon
/home/sw/netbeans-dev/websvccommon
/home/sw/netbeans-dev/enterprise
/home/sw/netbeans-dev/profiler
/home/sw/netbeans-dev/php
/home/sw/netbeans-dev/harness
/home/sw/netbeans-dev/groovy
/home/sw/netbeans-dev/javafx
/home/sw/netbeans-dev/platform
  Boot & Ext. Classpath   = 
  Application Classpath   = 
/home/sw/netbeans-dev/platform/lib/boot.jar:/home/sw/netbeans-dev/platform/lib/org-openide-modules.jar:/home/sw/netbeans-dev/platform/lib/org-openide-util.jar:/home/sw/netbeans-dev/platform/lib/org-openide-util-lookup.jar:/home/sw/netbeans-dev/platform/lib/org-openide-util-ui.jar
  Startup Classpath   = 
/home/sw/netbeans-dev/platform/core/org-netbeans-libs-asm.jar:/home/sw/netbeans-dev/platform/core/asm-tree-7.2.jar:/home/sw/netbeans-dev/platform/core/core-base.jar:/home/sw/netbeans-dev/platform/core/asm-commons-7.2.jar:/home/sw/netbeans-dev/platform/core/asm-7.2.jar:/home/sw/netbeans-dev/platform/core/org-openide-filesystems.jar:/home/sw/netbeans-dev/platform/core/core.jar:/home/sw/netbeans-dev/platform/core/org-openide-filesystems-compat8.jar:/home/sw/netbeans-dev/nb/core/org-netbeans-upgrader.jar:/home/sw/netbeans-dev/nb/core/locale/core_nb.jar
---
WARNING [org.netbeans.core.startup.NbEvents]: The extension 
/home/sw/netbeans-dev/ide/modules/ext/jcodings-1.0.18.jar may be multiply 
loaded by modules: 
[/home/sw/netbeans-dev/ide/modules/org-netbeans-libs-bytelist.jar, 
/home/sw/netbeans-dev/ide/modules/org-netbeans-modules-textmate-lexer.jar]; 
see: 
http://www.netbeans.org/download/dev/javadoc/org-openide-modules/org/openide/modules/doc-files/classpath.html#class-path
INFO [org.netbeans.modules.netbinox]: Install area set to 
file:/home/sw/netbeans-dev/
WARNING [org.netbeans.core.modules]: the modules 
[org.netbeans.modules.java.editor.lib, org.netbeans.modules.web.core.syntax, 
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.netbeans.core.modules]: the modules 
[org.netbeans.modules.ant.hints, org.netbeans.modules.java.hints, 
org.netbeans.modules.jshell.support, org.netbeans.modules.maven.hints, 
org.netbeans.modules.maven.j2ee, org.netbeans.modules.web.beans] use 
org.netbeans.modules.java.hints.legacy.spi which is deprecated: Use Java Hints 
SPI (org.netbeans.spi.java.hints) instead.
INFO [org.netbeans.modules.project.libraries.LibrariesStorage]: Cannot load 
library from file 
/home/dusty/.netbeans/dev/config/org-netbeans-api-project-libraries/Libraries/Java-EE-GlassFish-v3.xml,
 reason: Cannot create