[jira] [Comment Edited] (NETBEANS-5143) NetBeans 12.2, 12.3, 12.4 deploys webapps twice
[ https://issues.apache.org/jira/browse/NETBEANS-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354715#comment-17354715 ] Vlad Palnik edited comment on NETBEANS-5143 at 6/1/21, 3:01 AM: Does not look like its OS specific. Can someone running Ubuntu 14 please retest version 12.1, this is the first time I see this version affected. Affected Version Win 10, Java 11 => 12.2, 12.3, 12.4 Ubuntu 14, Java 11 => All 12x versions (per Deryl Spielman)* Ubuntu 20 LTS, Java 11 => 12.4 (12.2, 12.3 not tested) (VirtualBox 6.1.22) macOS Big Sur 11.4, Java 11 => 12.4 Unaffected Versions Win 10, Java 11 => 12.1 and earlier Ubuntu 20 LTS, Java 11 => 12.1 and earlier macOS Big Sur 11.2.3 => all versions (per Josh Juneau) (VirtualBox 6.1.22) macOS Big Sur 11.4, Java 11 => 12.1 was (Author: vladpaln): Does not look like its OS specific. Can someone running Ubuntu 14 please retest version 12.1, this is the first time I see this version affected. Affected Version Win 10, Java 11 => 12.2, 12.3, 12.4 Ubuntu 14, Java 11 => All 12x versions (per Deryl Spielman)* Ubuntu 20 LTS, Java 11 => 12.4 (12.2, 12.3 not tested) (VirtualBox 6.1.22) macOS Big Sur 11.4 => 12.4 Unaffected Versions Win 10, Java 11 => 12.1 and earlier Ubuntu 20 LTS, Java 11 => 12.1 and earlier macOS Big Sur 11.2.3 => all versions (per Josh Juneau) (VirtualBox 6.1.22) macOS Big Sur 11.4 => 12.1 > NetBeans 12.2, 12.3, 12.4 deploys webapps twice > --- > > Key: NETBEANS-5143 > URL: https://issues.apache.org/jira/browse/NETBEANS-5143 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 12.2, 12.3, 12.4 > Environment: Windows 10 20H2/AMD Ryzen 7 4800H/32GB RAM > java: build 11.0.9.1+1, maven 3.6.3 > Netbeans versions tested: 12.1, 12.2, 12.3, 12.4 (12.2/12.3/1.4 are effected) > Tomcat (new installs): 8.5.60, 9.0.40, Payara (per Patrick Musembi) >Reporter: Vlad Palnik >Priority: Major > Labels: webapp, webapp-deployment > > To whomever it concerns, > > Bug in NetBeans 12.2, 12.3, 12.4. Netbeans seems to interfere with the > deployment of web apps somehow and web apps are deployed twice. > > While deploying an app it follows this pattern: deploy => undeploy => deploy > (see build log below). I tried solving this issue by undeployed any previous > versions of the app manually and restarted Tomcat, the same error occurs. The > issue appears when using NB 12.2, 12.3 > > When tested on NetBeans 12.1 using the same Java/Tomcat installation/config > no errors occur and deployment proceeds correctly. > > Steps to replicate: > 1: Create maven webapp (Java EE7, Java 11) in NetBeans 12.1 > 2 Set Tomcat Server in Properties > Run > 3. Build/Run project in 12.1, you will get a "Hello World" basic site. > 4. Check build log, only a single deploy should show up. > 5 Close 12.1 and open same project in 12.2/12.3/12.4 > 6 Before run/build make sure same server and java versions are selected > 7 Build/Run project > 8 Check build log, you will see two deploys of webapp > > > BUILD SUCCESS > > Total time: 18.211 s > Finished at: 2020-12-11T17:27:08-08:00 > > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Starting Tomcat process... > Waiting for Tomcat... > Tomcat server started. > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext6407158500266578550.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Undeploying ... > undeploy?path=/myapp > OK - Undeployed application at context path [/myapp] > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext3519987589623367889.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > > -- 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
[jira] [Comment Edited] (NETBEANS-5143) NetBeans 12.2, 12.3, 12.4 deploys webapps twice
[ https://issues.apache.org/jira/browse/NETBEANS-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354715#comment-17354715 ] Vlad Palnik edited comment on NETBEANS-5143 at 6/1/21, 2:58 AM: Does not look like its OS specific. Can someone running Ubuntu 14 please retest version 12.1, this is the first time I see this version affected. Affected Version Win 10, Java 11 => 12.2, 12.3, 12.4 Ubuntu 14, Java 11 => All 12x versions (per Deryl Spielman)* Ubuntu 20 LTS, Java 11 => 12.4 (12.2, 12.3 not tested) (VirtualBox 6.1.22) macOS Big Sur 11.4 => 12.4 Unaffected Versions Win 10, Java 11 => 12.1 and earlier Ubuntu 20 LTS, Java 11 => 12.1 and earlier macOS Big Sur 11.2.3 => all versions (per Josh Juneau) (VirtualBox 6.1.22) macOS Big Sur 11.4 => 12.1 was (Author: vladpaln): Does not look like its OS specific. Can someone running Ubuntu 14 please retest version 12.1, this is the first time I see this version affected. Affected Version Win 10, Java 11 => 12.2, 12.3, 12.4 Ubuntu 14, Java 11 => All 12x versions (per Deryl Spielman)* Ubuntu 20 LTS, Java 11 => 12.4 (12.2, 12.3 not tested) Unaffected Versions Win 10, Java 11 => 12.1 and earlier Ubuntu 20 LTS, Java 11 => 12.1 and earlier macOS Big Sur 11.2.3 => all versions (per Josh Juneau) > NetBeans 12.2, 12.3, 12.4 deploys webapps twice > --- > > Key: NETBEANS-5143 > URL: https://issues.apache.org/jira/browse/NETBEANS-5143 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 12.2, 12.3, 12.4 > Environment: Windows 10 20H2/AMD Ryzen 7 4800H/32GB RAM > java: build 11.0.9.1+1, maven 3.6.3 > Netbeans versions tested: 12.1, 12.2, 12.3, 12.4 (12.2/12.3/1.4 are effected) > Tomcat (new installs): 8.5.60, 9.0.40, Payara (per Patrick Musembi) >Reporter: Vlad Palnik >Priority: Major > Labels: webapp, webapp-deployment > > To whomever it concerns, > > Bug in NetBeans 12.2, 12.3, 12.4. Netbeans seems to interfere with the > deployment of web apps somehow and web apps are deployed twice. > > While deploying an app it follows this pattern: deploy => undeploy => deploy > (see build log below). I tried solving this issue by undeployed any previous > versions of the app manually and restarted Tomcat, the same error occurs. The > issue appears when using NB 12.2, 12.3 > > When tested on NetBeans 12.1 using the same Java/Tomcat installation/config > no errors occur and deployment proceeds correctly. > > Steps to replicate: > 1: Create maven webapp (Java EE7, Java 11) in NetBeans 12.1 > 2 Set Tomcat Server in Properties > Run > 3. Build/Run project in 12.1, you will get a "Hello World" basic site. > 4. Check build log, only a single deploy should show up. > 5 Close 12.1 and open same project in 12.2/12.3/12.4 > 6 Before run/build make sure same server and java versions are selected > 7 Build/Run project > 8 Check build log, you will see two deploys of webapp > > > BUILD SUCCESS > > Total time: 18.211 s > Finished at: 2020-12-11T17:27:08-08:00 > > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Starting Tomcat process... > Waiting for Tomcat... > Tomcat server started. > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext6407158500266578550.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Undeploying ... > undeploy?path=/myapp > OK - Undeployed application at context path [/myapp] > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext3519987589623367889.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > > -- 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] [Comment Edited] (NETBEANS-5143) NetBeans 12.2, 12.3, 12.4 deploys webapps twice
[ https://issues.apache.org/jira/browse/NETBEANS-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354715#comment-17354715 ] Vlad Palnik edited comment on NETBEANS-5143 at 5/31/21, 11:35 PM: -- Does not look like its OS specific. Can someone running Ubuntu 14 please retest version 12.1, this is the first time I see this version affected. Affected Version Win 10, Java 11 => 12.2, 12.3, 12.4 Ubuntu 14, Java 11 => All 12x versions (per Deryl Spielman)* Ubuntu 20 LTS, Java 11 => 12.4 (12.2, 12.3 not tested) Unaffected Versions Win 10, Java 11 => 12.1 and earlier Ubuntu 20 LTS, Java 11 => 12.1 and earlier macOS Big Sur 11.2.3 => all versions (per Josh Juneau) was (Author: vladpaln): Does not look like its OS specific. Affected Version Win 10, Java 11 => 12.2, 12.3, 12.4 Ubuntu 14, Java 11 => All 12x versions (per Deryl Spielman)* Ubuntu 20 LTS, Java 11 => 12.4 (12.2, 12.3 not tested) Unaffected Versions Win 10, Java 11 => 12.1 and earlier Ubuntu 20 LTS, Java 11 => 12.1 and earlier macOS Big Sur 11.2.3 => all versions (per Josh Juneau) * Can someone running Ubuntu 14 please retest version 12.1, this is the first time I see this version affected. > NetBeans 12.2, 12.3, 12.4 deploys webapps twice > --- > > Key: NETBEANS-5143 > URL: https://issues.apache.org/jira/browse/NETBEANS-5143 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 12.2, 12.3, 12.4 > Environment: Windows 10 20H2/AMD Ryzen 7 4800H/32GB RAM > java: build 11.0.9.1+1, maven 3.6.3 > Netbeans versions tested: 12.1, 12.2, 12.3, 12.4 (12.2/12.3/1.4 are effected) > Tomcat (new installs): 8.5.60, 9.0.40, Payara (per Patrick Musembi) >Reporter: Vlad Palnik >Priority: Major > Labels: webapp, webapp-deployment > > To whomever it concerns, > > Bug in NetBeans 12.2, 12.3, 12.4. Netbeans seems to interfere with the > deployment of web apps somehow and web apps are deployed twice. > > While deploying an app it follows this pattern: deploy => undeploy => deploy > (see build log below). I tried solving this issue by undeployed any previous > versions of the app manually and restarted Tomcat, the same error occurs. The > issue appears when using NB 12.2, 12.3 > > When tested on NetBeans 12.1 using the same Java/Tomcat installation/config > no errors occur and deployment proceeds correctly. > > Steps to replicate: > 1: Create maven webapp (Java EE7, Java 11) in NetBeans 12.1 > 2 Set Tomcat Server in Properties > Run > 3. Build/Run project in 12.1, you will get a "Hello World" basic site. > 4. Check build log, only a single deploy should show up. > 5 Close 12.1 and open same project in 12.2/12.3/12.4 > 6 Before run/build make sure same server and java versions are selected > 7 Build/Run project > 8 Check build log, you will see two deploys of webapp > > > BUILD SUCCESS > > Total time: 18.211 s > Finished at: 2020-12-11T17:27:08-08:00 > > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Starting Tomcat process... > Waiting for Tomcat... > Tomcat server started. > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext6407158500266578550.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Undeploying ... > undeploy?path=/myapp > OK - Undeployed application at context path [/myapp] > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext3519987589623367889.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > > -- 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-5143) NetBeans 12.2, 12.3, 12.4 deploys webapps twice
[ https://issues.apache.org/jira/browse/NETBEANS-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354715#comment-17354715 ] Vlad Palnik commented on NETBEANS-5143: --- Does not look like its OS specific. Affected Version Win 10, Java 11 => 12.2, 12.3, 12.4 Ubuntu 14, Java 11 => All 12x versions (per Deryl Spielman)* Ubuntu 20 LTS, Java 11 => 12.4 (12.2, 12.3 not tested) Unaffected Versions Win 10, Java 11 => 12.1 and earlier Ubuntu 20 LTS, Java 11 => 12.1 and earlier macOS Big Sur 11.2.3 => all versions (per Josh Juneau) * Can someone running Ubuntu 14 please retest version 12.1, this is the first time I see this version affected. > NetBeans 12.2, 12.3, 12.4 deploys webapps twice > --- > > Key: NETBEANS-5143 > URL: https://issues.apache.org/jira/browse/NETBEANS-5143 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 12.2, 12.3, 12.4 > Environment: Windows 10 20H2/AMD Ryzen 7 4800H/32GB RAM > java: build 11.0.9.1+1, maven 3.6.3 > Netbeans versions tested: 12.1, 12.2, 12.3, 12.4 (12.2/12.3/1.4 are effected) > Tomcat (new installs): 8.5.60, 9.0.40, Payara (per Patrick Musembi) >Reporter: Vlad Palnik >Priority: Major > Labels: webapp, webapp-deployment > > To whomever it concerns, > > Bug in NetBeans 12.2, 12.3, 12.4. Netbeans seems to interfere with the > deployment of web apps somehow and web apps are deployed twice. > > While deploying an app it follows this pattern: deploy => undeploy => deploy > (see build log below). I tried solving this issue by undeployed any previous > versions of the app manually and restarted Tomcat, the same error occurs. The > issue appears when using NB 12.2, 12.3 > > When tested on NetBeans 12.1 using the same Java/Tomcat installation/config > no errors occur and deployment proceeds correctly. > > Steps to replicate: > 1: Create maven webapp (Java EE7, Java 11) in NetBeans 12.1 > 2 Set Tomcat Server in Properties > Run > 3. Build/Run project in 12.1, you will get a "Hello World" basic site. > 4. Check build log, only a single deploy should show up. > 5 Close 12.1 and open same project in 12.2/12.3/12.4 > 6 Before run/build make sure same server and java versions are selected > 7 Build/Run project > 8 Check build log, you will see two deploys of webapp > > > BUILD SUCCESS > > Total time: 18.211 s > Finished at: 2020-12-11T17:27:08-08:00 > > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Starting Tomcat process... > Waiting for Tomcat... > Tomcat server started. > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext6407158500266578550.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Undeploying ... > undeploy?path=/myapp > OK - Undeployed application at context path [/myapp] > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext3519987589623367889.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > > -- 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-5143) NetBeans 12.2, 12.3, 12.4 deploys webapps twice
[ https://issues.apache.org/jira/browse/NETBEANS-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354641#comment-17354641 ] Geertjan Wielenga commented on NETBEANS-5143: - The person reporting this notes that this issue does not occur with NetBeans 12.1. So, what everyone encountering this issue is going to have to do is be very explicit about their environment as well as the very specific steps to reproduce the problem. Otherwise this will not get fixed. > NetBeans 12.2, 12.3, 12.4 deploys webapps twice > --- > > Key: NETBEANS-5143 > URL: https://issues.apache.org/jira/browse/NETBEANS-5143 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 12.2, 12.3, 12.4 > Environment: Windows 10 20H2/AMD Ryzen 7 4800H/32GB RAM > java: build 11.0.9.1+1, maven 3.6.3 > Netbeans versions tested: 12.1, 12.2, 12.3, 12.4 (12.2/12.3/1.4 are effected) > Tomcat (new installs): 8.5.60, 9.0.40, Payara (per Patrick Musembi) >Reporter: Vlad Palnik >Priority: Major > Labels: webapp, webapp-deployment > > To whomever it concerns, > > Bug in NetBeans 12.2, 12.3, 12.4. Netbeans seems to interfere with the > deployment of web apps somehow and web apps are deployed twice. > > While deploying an app it follows this pattern: deploy => undeploy => deploy > (see build log below). I tried solving this issue by undeployed any previous > versions of the app manually and restarted Tomcat, the same error occurs. The > issue appears when using NB 12.2, 12.3 > > When tested on NetBeans 12.1 using the same Java/Tomcat installation/config > no errors occur and deployment proceeds correctly. > > Steps to replicate: > 1: Create maven webapp (Java EE7, Java 11) in NetBeans 12.1 > 2 Set Tomcat Server in Properties > Run > 3. Build/Run project in 12.1, you will get a "Hello World" basic site. > 4. Check build log, only a single deploy should show up. > 5 Close 12.1 and open same project in 12.2/12.3/12.4 > 6 Before run/build make sure same server and java versions are selected > 7 Build/Run project > 8 Check build log, you will see two deploys of webapp > > > BUILD SUCCESS > > Total time: 18.211 s > Finished at: 2020-12-11T17:27:08-08:00 > > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Starting Tomcat process... > Waiting for Tomcat... > Tomcat server started. > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext6407158500266578550.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Undeploying ... > undeploy?path=/myapp > OK - Undeployed application at context path [/myapp] > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext3519987589623367889.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > > -- 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-5143) NetBeans 12.2, 12.3, 12.4 deploys webapps twice
[ https://issues.apache.org/jira/browse/NETBEANS-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354639#comment-17354639 ] Deryl Spielman commented on NETBEANS-5143: -- This happens to me on openjdk 11 and Ubuntu 14. I don't think it's an OS issue. It happens on all versions of Netbeans 12. I switched back to netbeans 11.2 and don't experience the issue. > NetBeans 12.2, 12.3, 12.4 deploys webapps twice > --- > > Key: NETBEANS-5143 > URL: https://issues.apache.org/jira/browse/NETBEANS-5143 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 12.2, 12.3, 12.4 > Environment: Windows 10 20H2/AMD Ryzen 7 4800H/32GB RAM > java: build 11.0.9.1+1, maven 3.6.3 > Netbeans versions tested: 12.1, 12.2, 12.3, 12.4 (12.2/12.3/1.4 are effected) > Tomcat (new installs): 8.5.60, 9.0.40, Payara (per Patrick Musembi) >Reporter: Vlad Palnik >Priority: Major > Labels: webapp, webapp-deployment > > To whomever it concerns, > > Bug in NetBeans 12.2, 12.3, 12.4. Netbeans seems to interfere with the > deployment of web apps somehow and web apps are deployed twice. > > While deploying an app it follows this pattern: deploy => undeploy => deploy > (see build log below). I tried solving this issue by undeployed any previous > versions of the app manually and restarted Tomcat, the same error occurs. The > issue appears when using NB 12.2, 12.3 > > When tested on NetBeans 12.1 using the same Java/Tomcat installation/config > no errors occur and deployment proceeds correctly. > > Steps to replicate: > 1: Create maven webapp (Java EE7, Java 11) in NetBeans 12.1 > 2 Set Tomcat Server in Properties > Run > 3. Build/Run project in 12.1, you will get a "Hello World" basic site. > 4. Check build log, only a single deploy should show up. > 5 Close 12.1 and open same project in 12.2/12.3/12.4 > 6 Before run/build make sure same server and java versions are selected > 7 Build/Run project > 8 Check build log, you will see two deploys of webapp > > > BUILD SUCCESS > > Total time: 18.211 s > Finished at: 2020-12-11T17:27:08-08:00 > > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Starting Tomcat process... > Waiting for Tomcat... > Tomcat server started. > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext6407158500266578550.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Undeploying ... > undeploy?path=/myapp > OK - Undeployed application at context path [/myapp] > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext3519987589623367889.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-5723) Spurious "Set sun.java2d.noddraw=true to enable transparent windows" exception in IDE log
[
https://issues.apache.org/jira/browse/NETBEANS-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke resolved NETBEANS-5723.
---
Fix Version/s: Next
Resolution: Fixed
PR was merged, marking issue resolved.
> Spurious "Set sun.java2d.noddraw=true to enable transparent windows"
> exception in IDE log
> -
>
> Key: NETBEANS-5723
> URL: https://issues.apache.org/jira/browse/NETBEANS-5723
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Window System
>Affects Versions: 12.2
> Environment: Windows 10 on OpenJDK 11.0.11.
>Reporter: Eirik Bakke
>Assignee: Eirik Bakke
>Priority: Minor
> Labels: pull-request-available
> Fix For: Next
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On Windows, when dragging window system tags with the mouse, the following
> spurious error message may appear on the console running the NetBeans IDE or
> a NetBeans Platform application:
> {noformat}
> INFO [org.netbeans.core.nativeaccess.NativeWindowSystemImpl]
> java.lang.UnsupportedOperationException: Set sun.java2d.noddraw=true to
> enable transparent windows
> at
> com.sun.jna.platform.WindowUtils$W32WindowUtils.setWindowAlpha(WindowUtils.java:796)
> at
> com.sun.jna.platform.WindowUtils.setWindowAlpha(WindowUtils.java:1940)
> [catch] at
> org.netbeans.core.nativeaccess.NativeWindowSystemImpl.setWindowAlpha(NativeWindowSystemImpl.java:88)
> at
> org.netbeans.core.windows.view.dnd.DragAndDropFeedbackVisualizer.createDragWindow(DragAndDropFeedbackVisualizer.java:89)
> at
> org.netbeans.core.windows.view.dnd.DragAndDropFeedbackVisualizer.start(DragAndDropFeedbackVisualizer.java:110)
> at
> org.netbeans.core.windows.view.dnd.TopComponentDragSupport.doStartDrag(TopComponentDragSupport.java:402)
> at
> org.netbeans.core.windows.view.dnd.TopComponentDragSupport.eventDispatched(TopComponentDragSupport.java:327)
> at
> java.desktop/java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2194)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2086)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2042)
> at
> java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4917)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843)
> at
> java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
> at
> java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4564)
> at
> java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
> at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
> at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
> at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
>
[netbeans] branch master updated: [NETBEANS-5723] Avoid a spurious error log message when dragging window system tabs on Windows.
This is an automated email from the ASF dual-hosted git repository.
ebakke pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/netbeans.git
The following commit(s) were added to refs/heads/master by this push:
new 0fb44eb [NETBEANS-5723] Avoid a spurious error log message when
dragging window system tabs on Windows.
0fb44eb is described below
commit 0fb44eb02182e92bbb654c67781358c301fada94
Author: Eirik Bakke
AuthorDate: Thu May 27 12:07:45 2021 -0400
[NETBEANS-5723] Avoid a spurious error log message when dragging window
system tabs on Windows.
---
.../core/nativeaccess/NativeWindowSystemImpl.java | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git
a/platform/core.nativeaccess/src/org/netbeans/core/nativeaccess/NativeWindowSystemImpl.java
b/platform/core.nativeaccess/src/org/netbeans/core/nativeaccess/NativeWindowSystemImpl.java
index 8eb91ae..096743a 100644
---
a/platform/core.nativeaccess/src/org/netbeans/core/nativeaccess/NativeWindowSystemImpl.java
+++
b/platform/core.nativeaccess/src/org/netbeans/core/nativeaccess/NativeWindowSystemImpl.java
@@ -78,18 +78,22 @@ public class NativeWindowSystemImpl extends
NativeWindowSystem {
if
(gd.isWindowTranslucencySupported(GraphicsDevice.WindowTranslucency.TRANSLUCENT)
) {
try {
w.setOpacity(alpha);
+return;
} catch( Exception e ) {
//ignore, we'll try JNA
}
}
}
-//try the JNA way
-try {
-WindowUtils.setWindowAlpha(w, alpha);
-} catch( ThreadDeath td ) {
-throw td;
-} catch( Throwable e ) {
-LOG.log(Level.INFO, null, e);
+// Test isWindowAlphaSupported first to avoid an unnecessary log
message.
+if (WindowUtils.isWindowAlphaSupported()) {
+//try the JNA way
+try {
+WindowUtils.setWindowAlpha(w, alpha);
+} catch( ThreadDeath td ) {
+throw td;
+} catch( Throwable e ) {
+LOG.log(Level.INFO, null, e);
+}
}
}
-
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-5143) NetBeans 12.2, 12.3, 12.4 deploys webapps twice
[ https://issues.apache.org/jira/browse/NETBEANS-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354543#comment-17354543 ] Josh Juneau commented on NETBEANS-5143: --- I have attempted to replicate this issue on Mac OS X and was unable to do so. I suspect this may be a Windows-only issue? Perhaps someone else on OS X can confirm. I did the following: 1) Create new Maven web application 2) Set Tomcat server in "Run" 3) Build and Run project. I only see the one deployment. Subsequently, I attempted to run the same application on GlassFish and had no issues. My configuration is as follows: OS: OS X 11.2.3 JDK: Java 1.8.0_171 NetBeans 12.4 Tomcat: 9.0.46.0 GlassFish 6 > NetBeans 12.2, 12.3, 12.4 deploys webapps twice > --- > > Key: NETBEANS-5143 > URL: https://issues.apache.org/jira/browse/NETBEANS-5143 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 12.2, 12.3, 12.4 > Environment: Windows 10 20H2/AMD Ryzen 7 4800H/32GB RAM > java: build 11.0.9.1+1, maven 3.6.3 > Netbeans versions tested: 12.1, 12.2, 12.3, 12.4 (12.2/12.3/1.4 are effected) > Tomcat (new installs): 8.5.60, 9.0.40, Payara (per Patrick Musembi) >Reporter: Vlad Palnik >Priority: Major > Labels: webapp, webapp-deployment > > To whomever it concerns, > > Bug in NetBeans 12.2, 12.3, 12.4. Netbeans seems to interfere with the > deployment of web apps somehow and web apps are deployed twice. > > While deploying an app it follows this pattern: deploy => undeploy => deploy > (see build log below). I tried solving this issue by undeployed any previous > versions of the app manually and restarted Tomcat, the same error occurs. The > issue appears when using NB 12.2, 12.3 > > When tested on NetBeans 12.1 using the same Java/Tomcat installation/config > no errors occur and deployment proceeds correctly. > > Steps to replicate: > 1: Create maven webapp (Java EE7, Java 11) in NetBeans 12.1 > 2 Set Tomcat Server in Properties > Run > 3. Build/Run project in 12.1, you will get a "Hello World" basic site. > 4. Check build log, only a single deploy should show up. > 5 Close 12.1 and open same project in 12.2/12.3/12.4 > 6 Before run/build make sure same server and java versions are selected > 7 Build/Run project > 8 Check build log, you will see two deploys of webapp > > > BUILD SUCCESS > > Total time: 18.211 s > Finished at: 2020-12-11T17:27:08-08:00 > > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Starting Tomcat process... > Waiting for Tomcat... > Tomcat server started. > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext6407158500266578550.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > Deploying on Tomcat 8.5.60 > profile mode: false > debug mode: false > force redeploy: true > Undeploying ... > undeploy?path=/myapp > OK - Undeployed application at context path [/myapp] > In-place deployment at C:\Users\username\Desktop\myapp\target\myapp##1.2.5 > Deployment is in progress... > > deploy?config=file%3A%2FC%3A%2FUsers%2Fusername%2FAppData%2FLocal%2FTemp%2Fcontext3519987589623367889.xml=/myapp > OK - Deployed application at context path [/myapp] > Start is in progress... > start?path=/myapp > OK - Started application at context path [/myapp] > > -- 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-5739) Issue related with nb-javac
Marco A. Cruz Quevedo created NETBEANS-5739:
---
Summary: Issue related with nb-javac
Key: NETBEANS-5739
URL: https://issues.apache.org/jira/browse/NETBEANS-5739
Project: NetBeans
Issue Type: Bug
Components: java - JShell
Affects Versions: 12.2
Environment: *UI Log*
{{}}
{{ 2021-05-31T10:03:35}}
{{ 1622473415310}}
{{ 58}}
{{ 300}}
{{ 15}}
{{ SCREEN SIZE}}
{{ 1920}}
{{ 1080}}
{{ 1}}
{{}}
{{}}
{{ 2021-05-31T10:03:35}}
{{ 1622473415310}}
{{ 59}}
{{ 700}}
{{ 15}}
{{ IDE_STARTUP}}
{{}}
{{}}
{{ 2021-05-31T10:03:38}}
{{ 1622473418670}}
{{ 74}}
{{ 800}}
{{ 15}}
{{ USG_LOOK_AND_FEEL}}
{{ Windows}}
{{ Windows}}
{{}}
{{}}
{{ 2021-05-31T10:03:43}}
{{ 1622473423638}}
{{ 106}}
{{ 800}}
{{ 14}}
{{ MEMORY}}
{{ 3664150528}}
{{}}
{{}}
{{ 2021-05-31T10:03:46}}
{{ 1622473426873}}
{{ 107}}
{{ 400}}
{{ 21}}
{{ UI_ACTION_BUTTON_PRESS}}
{{ UI_ACTION_BUTTON_PRESS}}
{{ org.openide.awt.Bundle}}
{{ org.openide.awt.Actions$MenuItem[Options]}}
{{ org.openide.awt.Actions$MenuItem}}
{{ org.openide.awt.AlwaysEnabledAction[Options]}}
{{ org.openide.awt.AlwaysEnabledAction}}
{{ Options}}
{{}}
{{}}
{{ 2021-05-31T10:03:54}}
{{ 1622473434573}}
{{ 108}}
{{ 500}}
{{ 21}}
{{ ERGO_DOWNLOAD}}
{{ ERGO_DOWNLOAD}}
{{ org.netbeans.modules.ide.ergonomics.fod.Bundle}}
{{}}
{{}}
{{ 2021-05-31T10:04:07}}
{{ 1622473447608}}
{{ 111}}
{{ 500}}
{{ 21}}
{{ ERGO_CLOSE}}
{{ ERGO_CLOSE}}
{{ org.netbeans.modules.ide.ergonomics.fod.Bundle}}
{{}}
{{}}
{{ 2021-05-31T10:04:14}}
{{ 1622473454429}}
{{ 112}}
{{ 400}}
{{ 21}}
{{ UI_ACTION_BUTTON_PRESS}}
{{ UI_ACTION_BUTTON_PRESS}}
{{ org.openide.awt.Bundle}}
{{ org.openide.awt.Actions$MenuItem[Java Platforms]}}
{{ org.openide.awt.Actions$MenuItem}}
{{ org.openide.awt.AlwaysEnabledAction[Java Platforms]}}
{{ org.openide.awt.AlwaysEnabledAction}}
{{ Java Platforms}}
{{}}
{{}}
{{ 2021-05-31T10:04:40}}
{{ 1622473480675}}
{{ 113}}
{{ 400}}
{{ 21}}
{{ UI_ACTION_BUTTON_PRESS}}
{{ UI_ACTION_BUTTON_PRESS}}
{{ org.openide.awt.Bundle}}
{{ org.openide.awt.Actions$MenuItem[Options]}}
{{ org.openide.awt.Actions$MenuItem}}
{{ org.openide.awt.AlwaysEnabledAction[Options]}}
{{ org.openide.awt.AlwaysEnabledAction}}
{{ Options}}
{{}}
{{}}
{{ 2021-05-31T10:04:52}}
{{ 1622473492846}}
{{ 114}}
{{ 500}}
{{ 21}}
{{ ERGO_CLOSE}}
{{ ERGO_CLOSE}}
{{ org.netbeans.modules.ide.ergonomics.fod.Bundle}}
{{}}
{{}}
{{ 2021-05-31T10:04:58}}
{{ 1622473498732}}
{{ 115}}
{{ 400}}
{{ 21}}
{{ UI_ACTION_BUTTON_PRESS}}
{{ UI_ACTION_BUTTON_PRESS}}
{{ org.openide.awt.Bundle}}
{{ org.openide.awt.Actions$MenuItem[Exit]}}
{{ org.openide.awt.Actions$MenuItem}}
{{ org.netbeans.core.actions.SystemExit[Exit]}}
{{ org.netbeans.core.actions.SystemExit}}
{{ Exit}}
{{}}
{{}}
{{ 2021-05-31T10:05:01}}
{{ 1622473501021}}
{{ 116}}
{{ 800}}
{{ 64}}
{{ INDEXING_STARTED}}
{{ INDEXING_STARTED}}
{{ org.netbeans.modules.parsing.impl.indexing.Bundle}}
{{ 0}}
{{}}
{{}}
{{ 2021-05-31T10:05:01}}
{{ 1622473501209}}
{{ 117}}
{{ 800}}
{{ 64}}
{{ INDEXING_FINISHED}}
{{ INDEXING_FINISHED}}
{{ org.netbeans.modules.parsing.impl.indexing.Bundle}}
{{ 172}}
{{}}
{{}}
{{ 2021-05-31T10:05:04}}
{{ 1622473504130}}
{{ 230}}
{{ 500}}
{{ 21}}
{{ LOG_WINDOW_DEACTIVATED}}
{{ LOG_WINDOW_DEACTIVATED}}
{{ org.netbeans.core.ui.warmup.Bundle}}
{{}}
{{}}
{{ 2021-05-31T10:12:05}}
{{ 1622473925641}}
{{ 97}}
{{ 300}}
{{ 15}}
{{ CPU INFO}}
{{ 4}}
{{}}
{{}}
{{ 2021-05-31T10:12:05}}
{{ 1622473925657}}
{{ 98}}
{{ 300}}
{{ 15}}
{{ SCREEN SIZE}}
{{ 1920}}
{{ 1080}}
{{ 1}}
{{}}
{{}}
{{ 2021-05-31T10:12:05}}
{{ 1622473925657}}
{{ 99}}
{{ 700}}
{{ 15}}
{{ IDE_STARTUP}}
{{}}
{{}}
{{ 2021-05-31T10:12:08}}
{{ 1622473928313}}
{{ 120}}
{{ 800}}
{{ 15}}
{{ USG_LOOK_AND_FEEL}}
{{ Windows}}
{{ Windows}}
{{}}
{{}}
{{ 2021-05-31T10:12:12}}
{{ 1622473932641}}
{{ 143}}
{{ 800}}
{{ 31}}
{{ MEMORY}}
{{ 3664150528}}
{{}}
{{}}
{{ 2021-05-31T10:12:14}}
{{ 1622473934125}}
{{ 144}}
{{ 400}}
{{ 21}}
{{ UI_ACTION_BUTTON_PRESS}}
{{ UI_ACTION_BUTTON_PRESS}}
{{ org.openide.awt.Bundle}}
{{ org.openide.awt.Actions$MenuItem[Options]}}
{{ org.openide.awt.Actions$MenuItem}}
{{ org.openide.awt.AlwaysEnabledAction[Options]}}
{{ org.openide.awt.AlwaysEnabledAction}}
{{ Options}}
{{}}
{{}}
{{ 2021-05-31T10:12:18}}
{{ 1622473938333}}
{{ 145}}
{{ 500}}
{{ 21}}
{{ ERGO_DOWNLOAD}}
{{ ERGO_DOWNLOAD}}
{{ org.netbeans.modules.ide.ergonomics.fod.Bundle}}
{{}}
{{}}
{{ 2021-05-31T10:12:20}}
{{ 1622473940333}}
{{ 146}}
{{ 500}}
{{ 21}}
{{ ERGO_CLOSE}}
{{ ERGO_CLOSE}}
{{ org.netbeans.modules.ide.ergonomics.fod.Bundle}}
{{}}
{{}}
{{ 2021-05-31T10:12:29}}
{{ 1622473949774}}
{{ 149}}
{{ 500}}
{{ 21}}
{{ ERGO_DOWNLOAD}}
{{ ERGO_DOWNLOAD}}
{{ org.netbeans.modules.ide.ergonomics.fod.Bundle}}
{{}}
{{}}
{{ 2021-05-31T10:12:37}}
{{ 1622473957453}}
{{ 160}}
{{ 500}}
{{ 21}}
{{ ERGO_CLOSE}}
{{ ERGO_CLOSE}}
{{ org.netbeans.modules.ide.ergonomics.fod.Bundle}}
{{}}
{{}}
{{ 2021-05-31T10:14:30}}
{{ 1622474070213}}
{{ 162}}
{{ 500}}
{{ 21}}
{{
[netbeans] branch master updated: Fixes NPE and potential lockup in tests.
This is an automated email from the ASF dual-hosted git repository.
sdedic pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/netbeans.git
The following commit(s) were added to refs/heads/master by this push:
new 1f6b584 Fixes NPE and potential lockup in tests.
new 392357a Merge pull request #2982 from sdedic/sdedic/ioprovider-npes
1f6b584 is described below
commit 1f6b584576c608d65596d41a7c2a04822f5f3687
Author: Svata Dedic
AuthorDate: Mon May 31 11:15:02 2021 +0200
Fixes NPE and potential lockup in tests.
---
.../src/org/openide/execution/ExecutionEngine.java | 3 ++-
platform/openide.io/src/org/openide/windows/IOProvider.java| 7 ++-
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git
a/platform/openide.execution/src/org/openide/execution/ExecutionEngine.java
b/platform/openide.execution/src/org/openide/execution/ExecutionEngine.java
index 6655b84..9ed92b5 100644
--- a/platform/openide.execution/src/org/openide/execution/ExecutionEngine.java
+++ b/platform/openide.execution/src/org/openide/execution/ExecutionEngine.java
@@ -127,13 +127,14 @@ public abstract class ExecutionEngine extends Object {
private RequestProcessor.Task task;
private int resultValue;
private final String name;
-private InputOutput io;
+private final InputOutput io;
public ET(Runnable run, String name, InputOutput io) {
super(run);
this.originalLookup = Lookup.getDefault();
this.resultValue = resultValue;
this.name = name;
+this.io = io;
task = RequestProcessor.getDefault().post(this);
}
diff --git a/platform/openide.io/src/org/openide/windows/IOProvider.java
b/platform/openide.io/src/org/openide/windows/IOProvider.java
index 53f2f3f..fbd5f21 100644
--- a/platform/openide.io/src/org/openide/windows/IOProvider.java
+++ b/platform/openide.io/src/org/openide/windows/IOProvider.java
@@ -191,7 +191,12 @@ public abstract class IOProvider {
/** Fallback implementation. */
private static final class Trivial extends IOProvider {
-private static final Reader in = new BufferedReader(new
InputStreamReader(System.in));
+private static final Reader in = new BufferedReader(new
InputStreamReader(System.in)) {
+public void close() {
+// do nothing, prevent blocking between System.in.read() and
System.in.close();
+}
+};
+
private static final PrintStream out = System.out;
private static final PrintStream err = System.err;
-
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-5732) Profiler not working with Maven Project on MacOS
[
https://issues.apache.org/jira/browse/NETBEANS-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic reassigned NETBEANS-5732:
-
Assignee: Svatopluk Dedic
> Profiler not working with Maven Project on MacOS
>
>
> Key: NETBEANS-5732
> URL: https://issues.apache.org/jira/browse/NETBEANS-5732
> Project: NetBeans
> Issue Type: Bug
> Components: profiler - IDE
>Affects Versions: 12.4
>Reporter: Peter Hull
>Assignee: Svatopluk Dedic
>Priority: Major
> Attachments: IDE_log.txt, nbactions.xml
>
>
> Profiler does not start when attempting to profile a Swing app using a maven
> project on MacOS.
> Expected: profiler does start
> Actual: Shows an error in the output tab, given below:
> cd /Users/peterhull/Projects/mavenproject2;
> JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
> "/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/java/maven/bin/mvn"
> "-Dexec.vmArgs='-agentpath:\\'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib\\'=\\'/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib\\',5140,10'
> -XX:+HeapDumpOnOutOfMemoryError
> '-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> '" "-Dexec.args=${exec.vmArgs} -classpath %classpath ${exec.mainClass}
> ${exec.appArgs}" -Dexec.mainClass=com.nowhere.mavenproject2.NewJFrame
> -Dexec.executable=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home/bin/java
> "-Dprofiler.jvmargs.all= -XX:+HeapDumpOnOutOfMemoryError
> -XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> -agentpath:'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib'='/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib',5140,10"
> "-Dprofiler.jvmargs.arg1=-agentpath:'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib'='/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib',5140,10"
> -Dprofiler.jvmargs.arg2=-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> -Dprofiler.jvmargs.arg3=-XX:+HeapDumpOnOutOfMemoryError -Dexec.appArgs=
> org.codehaus.mojo:exec-maven-plugin:3.0.0:exec
> Running NetBeans Compile On Save execution. Phase execution is skipped and
> output directories of dependency projects (with Compile on Save turned on)
> will be used instead of their jar artifacts.
> Scanning for projects...
> -< com.nowhere:mavenproject2 >--
> Building mavenproject2 1.0-SNAPSHOT
> [ jar ]-
> --- exec-maven-plugin:3.0.0:exec (default-cli) @ mavenproject2 ---
> Error occurred during initialization of VM
> Could not find agent library \/Applications/NetBeans/Apache in absolute path,
> with error: dlopen(\/Applications/NetBeans/Apache, 1): image not found
> Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:982)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:929)
> at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:457)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute
[jira] [Updated] (NETBEANS-5732) Profiler not working with Maven Project on MacOS
[
https://issues.apache.org/jira/browse/NETBEANS-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Hull updated NETBEANS-5732:
-
Attachment: nbactions.xml
> Profiler not working with Maven Project on MacOS
>
>
> Key: NETBEANS-5732
> URL: https://issues.apache.org/jira/browse/NETBEANS-5732
> Project: NetBeans
> Issue Type: Bug
> Components: profiler - IDE
>Affects Versions: 12.4
>Reporter: Peter Hull
>Priority: Major
> Attachments: IDE_log.txt, nbactions.xml
>
>
> Profiler does not start when attempting to profile a Swing app using a maven
> project on MacOS.
> Expected: profiler does start
> Actual: Shows an error in the output tab, given below:
> cd /Users/peterhull/Projects/mavenproject2;
> JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
> "/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/java/maven/bin/mvn"
> "-Dexec.vmArgs='-agentpath:\\'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib\\'=\\'/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib\\',5140,10'
> -XX:+HeapDumpOnOutOfMemoryError
> '-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> '" "-Dexec.args=${exec.vmArgs} -classpath %classpath ${exec.mainClass}
> ${exec.appArgs}" -Dexec.mainClass=com.nowhere.mavenproject2.NewJFrame
> -Dexec.executable=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home/bin/java
> "-Dprofiler.jvmargs.all= -XX:+HeapDumpOnOutOfMemoryError
> -XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> -agentpath:'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib'='/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib',5140,10"
> "-Dprofiler.jvmargs.arg1=-agentpath:'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib'='/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib',5140,10"
> -Dprofiler.jvmargs.arg2=-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> -Dprofiler.jvmargs.arg3=-XX:+HeapDumpOnOutOfMemoryError -Dexec.appArgs=
> org.codehaus.mojo:exec-maven-plugin:3.0.0:exec
> Running NetBeans Compile On Save execution. Phase execution is skipped and
> output directories of dependency projects (with Compile on Save turned on)
> will be used instead of their jar artifacts.
> Scanning for projects...
> -< com.nowhere:mavenproject2 >--
> Building mavenproject2 1.0-SNAPSHOT
> [ jar ]-
> --- exec-maven-plugin:3.0.0:exec (default-cli) @ mavenproject2 ---
> Error occurred during initialization of VM
> Could not find agent library \/Applications/NetBeans/Apache in absolute path,
> with error: dlopen(\/Applications/NetBeans/Apache, 1): image not found
> Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:982)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:929)
> at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:457)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute
[jira] [Commented] (NETBEANS-5732) Profiler not working with Maven Project on MacOS
[
https://issues.apache.org/jira/browse/NETBEANS-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354423#comment-17354423
]
Peter Hull commented on NETBEANS-5732:
--
[~sdedic] I didn't do any customisation to nbactions.xml myself (just used a
newly-created maven project as described above) I've attached it anyway.
> Profiler not working with Maven Project on MacOS
>
>
> Key: NETBEANS-5732
> URL: https://issues.apache.org/jira/browse/NETBEANS-5732
> Project: NetBeans
> Issue Type: Bug
> Components: profiler - IDE
>Affects Versions: 12.4
>Reporter: Peter Hull
>Priority: Major
> Attachments: IDE_log.txt, nbactions.xml
>
>
> Profiler does not start when attempting to profile a Swing app using a maven
> project on MacOS.
> Expected: profiler does start
> Actual: Shows an error in the output tab, given below:
> cd /Users/peterhull/Projects/mavenproject2;
> JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
> "/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/java/maven/bin/mvn"
> "-Dexec.vmArgs='-agentpath:\\'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib\\'=\\'/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib\\',5140,10'
> -XX:+HeapDumpOnOutOfMemoryError
> '-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> '" "-Dexec.args=${exec.vmArgs} -classpath %classpath ${exec.mainClass}
> ${exec.appArgs}" -Dexec.mainClass=com.nowhere.mavenproject2.NewJFrame
> -Dexec.executable=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home/bin/java
> "-Dprofiler.jvmargs.all= -XX:+HeapDumpOnOutOfMemoryError
> -XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> -agentpath:'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib'='/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib',5140,10"
> "-Dprofiler.jvmargs.arg1=-agentpath:'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib'='/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib',5140,10"
> -Dprofiler.jvmargs.arg2=-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> -Dprofiler.jvmargs.arg3=-XX:+HeapDumpOnOutOfMemoryError -Dexec.appArgs=
> org.codehaus.mojo:exec-maven-plugin:3.0.0:exec
> Running NetBeans Compile On Save execution. Phase execution is skipped and
> output directories of dependency projects (with Compile on Save turned on)
> will be used instead of their jar artifacts.
> Scanning for projects...
> -< com.nowhere:mavenproject2 >--
> Building mavenproject2 1.0-SNAPSHOT
> [ jar ]-
> --- exec-maven-plugin:3.0.0:exec (default-cli) @ mavenproject2 ---
> Error occurred during initialization of VM
> Could not find agent library \/Applications/NetBeans/Apache in absolute path,
> with error: dlopen(\/Applications/NetBeans/Apache, 1): image not found
> Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:982)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:929)
> at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:457)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at
[jira] [Commented] (NETBEANS-5732) Profiler not working with Maven Project on MacOS
[
https://issues.apache.org/jira/browse/NETBEANS-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354422#comment-17354422
]
Peter Hull commented on NETBEANS-5732:
--
It runs OK on 12.3, here is the command line that it prints:
{{cd /Users/peterhull/Projects/mavenproject2;
JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
/Users/peterhull/Downloads/netbeans/java/maven/bin/mvn -Dexec.vmArgs=
"-Dexec.args=-agentpath:/Users/peterhull/Downloads/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib=/Users/peterhull/Downloads/netbeans/profiler/lib,5140,10
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.3/mavencachedirs/1004131909/org-netbeans-modules-profiler
${exec.vmArgs} -classpath %classpath ${exec.mainClass} ${exec.appArgs}"
-Dexec.mainClass=com.nowhere.mavenproject2.NewJFrame
-Dexec.executable=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home/bin/java
"-Dprofiler.jvmargs.all= -XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.3/mavencachedirs/1004131909/org-netbeans-modules-profiler
-agentpath:/Users/peterhull/Downloads/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib=/Users/peterhull/Downloads/netbeans/profiler/lib,5140,10"
-Dprofiler.jvmargs.arg1=-agentpath:/Users/peterhull/Downloads/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib=/Users/peterhull/Downloads/netbeans/profiler/lib,5140,10
-Dprofiler.jvmargs.arg2=-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.3/mavencachedirs/1004131909/org-netbeans-modules-profiler
-Dprofiler.jvmargs.arg3=-XX:+HeapDumpOnOutOfMemoryError
org.codehaus.mojo:exec-maven-plugin:3.0.0:exec}}
> Profiler not working with Maven Project on MacOS
>
>
> Key: NETBEANS-5732
> URL: https://issues.apache.org/jira/browse/NETBEANS-5732
> Project: NetBeans
> Issue Type: Bug
> Components: profiler - IDE
>Affects Versions: 12.4
>Reporter: Peter Hull
>Priority: Major
> Attachments: IDE_log.txt
>
>
> Profiler does not start when attempting to profile a Swing app using a maven
> project on MacOS.
> Expected: profiler does start
> Actual: Shows an error in the output tab, given below:
> cd /Users/peterhull/Projects/mavenproject2;
> JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
> "/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/java/maven/bin/mvn"
> "-Dexec.vmArgs='-agentpath:\\'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib\\'=\\'/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib\\',5140,10'
> -XX:+HeapDumpOnOutOfMemoryError
> '-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> '" "-Dexec.args=${exec.vmArgs} -classpath %classpath ${exec.mainClass}
> ${exec.appArgs}" -Dexec.mainClass=com.nowhere.mavenproject2.NewJFrame
> -Dexec.executable=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home/bin/java
> "-Dprofiler.jvmargs.all= -XX:+HeapDumpOnOutOfMemoryError
> -XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> -agentpath:'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib'='/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib',5140,10"
> "-Dprofiler.jvmargs.arg1=-agentpath:'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib'='/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib',5140,10"
> -Dprofiler.jvmargs.arg2=-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> -Dprofiler.jvmargs.arg3=-XX:+HeapDumpOnOutOfMemoryError -Dexec.appArgs=
> org.codehaus.mojo:exec-maven-plugin:3.0.0:exec
> Running NetBeans Compile On Save execution. Phase execution is skipped and
> output directories of dependency projects (with Compile on Save turned on)
> will be used instead of their jar artifacts.
> Scanning for projects...
> -< com.nowhere:mavenproject2 >--
> Building mavenproject2 1.0-SNAPSHOT
> [ jar ]-
> --- exec-maven-plugin:3.0.0:exec (default-cli) @ mavenproject2 ---
> Error occurred during initialization of VM
> Could not find agent library
[netbeans] branch master updated (c47c7f2 -> 46d829a)
This is an automated email from the ASF dual-hosted git repository. sdedic pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/netbeans.git. from c47c7f2 Debugger attach in VSCode extension. (#5346) new 074e0ec Workaround: include micronaut, since we have it in the IDE. new f7fe282 ProjectConfiguration support added. new daf48ea Configurations can be extracted from actions-config.xmls. new c337f37 ActionProvider respects active or selected config. new 0929bdf Gradle/Java adds Continuous Mode support. new b29671f stdin of launched process connected to LSP evaluateRequest new f3c6dd0 Added utility to validate filenames. new 00b1df7 Bugfixes for configuration impl. new cbd631b Project Configuration UI. new bbcddf4 Some unit tests. new 5391287 Actions panel adapted. new 8367bcd Fixed wording, enabled completion for conf arguments. new 590b388 Bugfixes and polishing. new 4f7e33e Config provider now supports Customize... item. new 3fc6895 Config settings are combined with action on gradle exec. new ba8d5ab ProjectConfigurationSupport moved to private package, just effective configuration exported. new 1e90375 Stabilized order of configs. new 551c807 Allowed Continuous mode for test tasks new 414cc1a Added APL 2.0 headers. Excluded golden files from RAT. new 7ef15be Bugfix: primeProject() needs project instance if already primed. new ecf603f Allow action ordering / priorities new 8c6ab00 Documentation, arch changes, examples, bugfixes. new d49b531 Apichanges updated for isValidFileName. new 46d829a Merge pull request #2969 from sdedic/gradle/configurations3 The 5502 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: extide/gradle/apichanges.xml | 33 + extide/gradle/arch.xml | 11 + extide/gradle/licenseinfo.xml | 11 + extide/gradle/manifest.mf | 2 +- .../gradle/tooling/NbProjectInfoBuilder.groovy | 3 +- .../modules/gradle/ActionProviderImpl.java | 41 +- .../modules/gradle/DeleteOperationImpl.java| 2 +- .../modules/gradle/NbGradleProjectImpl.java| 4 +- .../gradle/actions/ActionMappingScanner.java | 75 +- .../gradle/actions/ActionPersistenceUtils.java | 198 ++ .../modules/gradle/actions/ActionToTaskUtils.java | 45 +- .../actions/ConfigurableActionsProviderImpl.java | 767 + .../actions/CustomActionRegistrationSupport.java | 181 +++-- .../actions/ProjectActionMappingProviderImpl.java | 5 +- .../modules/gradle/actions/action-mapping.dtd | 7 +- .../gradle/api/execute/GradleCommandLine.java | 2 +- .../api/execute/GradleExecConfiguration.java | 231 +++ .../modules/gradle/api/execute/RunConfig.java | 19 +- .../modules/gradle/api/execute/RunUtils.java | 47 +- .../gradle/configurations/Bundle.properties| 49 ++ .../configurations/ConfigurationSnapshot.java | 310 + .../gradle/configurations/ConfigurationsPanel.form | 224 ++ .../gradle/configurations/ConfigurationsPanel.java | 424 .../ConfigurationsPanelProvider.java | 78 +++ .../configurations/NewConfigurationPanel.form | 175 + .../configurations/NewConfigurationPanel.java | 321 + .../gradle/customizer/BuildActionsCustomizer.form | 162 +++-- .../gradle/customizer/BuildActionsCustomizer.java | 218 -- .../modules/gradle/customizer/Bundle.properties| 1 + .../customizer/GradleCustomizerProvider.java | 6 +- .../gradle/execute/AbstractGradleExecutor.java | 2 +- .../gradle/execute/ConfigPersistenceUtils.java | 180 + .../gradle/execute/ConfigurableActionProvider.java | 72 ++ .../gradle/execute/GradleDaemonExecutor.java | 40 +- .../modules/gradle/execute/GradleExecAccessor.java | 111 +++ .../modules/gradle/execute/GradleExecutor.java | 1 + .../gradle/execute/GradleExecutorOptionsPanel.java | 9 +- .../execute/GradleProjectConfigProvider.java | 379 ++ .../execute/ProjectConfigurationSupport.java | 136 .../execute/ProjectConfigurationUpdater.java | 67 ++ .../spi/actions/DefaultGradleActionsProvider.java | 101 +++ .../gradle/spi/actions/GradleActionsProvider.java | 51 +- .../test/unit/src/META-INF/generated-layer.xml | 60 ++ .../gradle/AbstractGradleProjectTestCase.java | 2 +- .../ConfigurableActionsProviderImplTest.java | 263 +++ .../modules/gradle/actions/action-mapping.xml | 76 +- .../modules/gradle/actions/declarative-actions.xml | 21 +
[jira] [Created] (NETBEANS-5738) Cannot debug jtreg tests unless java.base project is open
Jaroslav Tulach created NETBEANS-5738:
-
Summary: Cannot debug jtreg tests unless java.base project is open
Key: NETBEANS-5738
URL: https://issues.apache.org/jira/browse/NETBEANS-5738
Project: NetBeans
Issue Type: Bug
Components: java - Project
Affects Versions: 12.4
Reporter: Jaroslav Tulach
Assignee: Jan Lahoda
I've tried it in VSNetBeans, but I assume similar problem will happen with
NetBeans IDE as well. Follow the instructions for scenario 3 - e.g. OpenJDK -
at [wiki
page|https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+extension+for+Visual+Studio+Code].
Make sure *jtreg* support is enabled.
Open for example
{{test/jdk/java/lang/annotation/AnnotationType/AnnotationTypeRuntimeAssumptionTest.java}}
and debug it. It doesn't work - first of all one has to open {{src/java.base}}
is project. That's unfortunate, and especially in VSNetBeans, not very
intuitive.
--
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-4927) Error parsing of the JDK classes in editor
[ https://issues.apache.org/jira/browse/NETBEANS-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Miksik updated NETBEANS-4927: -- Affects Version/s: 12.4 > Error parsing of the JDK classes in editor > -- > > Key: NETBEANS-4927 > URL: https://issues.apache.org/jira/browse/NETBEANS-4927 > Project: NetBeans > Issue Type: Bug > Components: editor - Parsing Indexing >Affects Versions: 12.1, 12.2, 12.3, 12.4 >Reporter: Petr Miksik >Priority: Blocker > Attachments: DefaultMutableTreeNode.dump, ide.log, ui.log > > > For example _DefaultMutableTreeNode_, _AbstractButton_ or _JTree_ are ones of > the affected files. > Lots of classes are only partially parsed, so the JavaDoc is not shown for > methods in many cases. > The problem appears only with JDK 11 and later, JDK 8 classes seems to be all > properly parsed. > Clearing NetBeans cache will not help. -- 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-5736) Clicking in "Projects" tree should work along entire row
[ https://issues.apache.org/jira/browse/NETBEANS-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated NETBEANS-5736: - Labels: pull-request-available (was: ) > Clicking in "Projects" tree should work along entire row > > > Key: NETBEANS-5736 > URL: https://issues.apache.org/jira/browse/NETBEANS-5736 > Project: NetBeans > Issue Type: Improvement > Components: platform - Explorer >Affects Versions: 12.2 > Environment: All LAFs (but tested on the Windows LAFs and MacOS/Aqua > LAFs). >Reporter: Eirik Bakke >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > In the TreeView component, which is used for the "Projects" tab in the > NetBeans IDE, the user should be able to click anywhere along the width of > the component to select a given node. (Or at least, in the empty space to the > right of a component). Similarly, during drag-and-drop operations, the user > should be able to drop anywhere to the right of the node's icon. > This usability issue came up during user testing of a NetBeans Platform > application. The user complained that files with a short filename were harder > to click than files with long names. The user, a software engineer, pointed > out that the equivalent tree component in IntelliJ allows the entire row to > be clicked or dragged at to target a given node. > TreeView's behavior is derived from its superclass JTree. The OutlineView > component does not have the same problem, as it derives from ETable and in > turn JTable. > PR to follow... -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-5346) Implement debugger attach in VSCode extension
[
https://issues.apache.org/jira/browse/NETBEANS-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Entlicher resolved NETBEANS-5346.
Resolution: Fixed
Fixed.
The attach connectors are provided in a dynamic way (according to what the
current JVM provides on the current user OS).
In the VSCode UI the attach actions are available via the Run combo-box,
clicking on "Java 8+..." suggests two items on Linux ("Attach to Port" and
"Attach to Process") and three items on Windows ("Attach to Shared Memory" in
addition).
"Attach to Process" shows a quick pick with running processes eligible for
debugger attach.
The selected attach action can be added to {{launch.conf}} for customization
via a button with "Configure" icon next to the attach action.
> Implement debugger attach in VSCode extension
> -
>
> Key: NETBEANS-5346
> URL: https://issues.apache.org/jira/browse/NETBEANS-5346
> Project: NetBeans
> Issue Type: Improvement
> Components: vscode
>Affects Versions: 12.2
>Reporter: Martin Entlicher
>Assignee: Martin Entlicher
>Priority: Critical
> Labels: pull-request-available
> Fix For: 12.5
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Debugger attach to a remote process is missing in VSCode extension.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[netbeans] branch master updated: Debugger attach in VSCode extension. (#5346)
This is an automated email from the ASF dual-hosted git repository.
entl pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/netbeans.git
The following commit(s) were added to refs/heads/master by this push:
new c47c7f2 Debugger attach in VSCode extension. (#5346)
c47c7f2 is described below
commit c47c7f22bb7adc97af6c428100487ab2f82688e3
Author: Martin Entlicher
AuthorDate: Thu May 27 18:16:49 2021 +0200
Debugger attach in VSCode extension. (#5346)
---
.../lsp/server/debugging/NbProtocolServer.java | 14 +-
.../debugging/attach/AttachConfigurations.java | 222 +
.../debugging/attach/NbAttachRequestHandler.java | 222 +
.../server/debugging/launch/NbDebugSession.java| 2 +-
.../java/lsp/server/protocol/DebugConnector.java | 151 ++
.../modules/java/lsp/server/protocol/Server.java | 27 ++-
.../lsp/server/protocol/WorkspaceServiceImpl.java | 15 +-
.../java/lsp/server/protocol/ServerTest.java | 42
java/java.lsp.server/vscode/package.json | 39 +++-
java/java.lsp.server/vscode/src/extension.ts | 61 +++---
java/java.lsp.server/vscode/src/protocol.ts| 7 +
11 files changed, 758 insertions(+), 44 deletions(-)
diff --git
a/java/java.lsp.server/src/org/netbeans/modules/java/lsp/server/debugging/NbProtocolServer.java
b/java/java.lsp.server/src/org/netbeans/modules/java/lsp/server/debugging/NbProtocolServer.java
index 56f20df..6ae1497 100644
---
a/java/java.lsp.server/src/org/netbeans/modules/java/lsp/server/debugging/NbProtocolServer.java
+++
b/java/java.lsp.server/src/org/netbeans/modules/java/lsp/server/debugging/NbProtocolServer.java
@@ -19,19 +19,15 @@
package org.netbeans.modules.java.lsp.server.debugging;
import java.io.File;
-import java.net.MalformedURLException;
import java.net.URI;
import java.net.URISyntaxException;
-import java.net.URL;
import java.nio.file.Paths;
import java.util.ArrayList;
import java.util.Collections;
import java.util.List;
import java.util.Map;
import java.util.concurrent.CompletableFuture;
-import java.util.concurrent.CountDownLatch;
import java.util.concurrent.Future;
-import java.util.concurrent.atomic.AtomicReference;
import org.apache.commons.lang3.StringUtils;
import org.eclipse.lsp4j.debug.Capabilities;
@@ -41,7 +37,6 @@ import org.eclipse.lsp4j.debug.ContinueResponse;
import org.eclipse.lsp4j.debug.DisconnectArguments;
import org.eclipse.lsp4j.debug.EvaluateArguments;
import org.eclipse.lsp4j.debug.EvaluateResponse;
-import org.eclipse.lsp4j.debug.ExceptionBreakMode;
import org.eclipse.lsp4j.debug.ExceptionBreakpointsFilter;
import org.eclipse.lsp4j.debug.ExceptionInfoArguments;
import org.eclipse.lsp4j.debug.ExceptionInfoResponse;
@@ -79,10 +74,11 @@ import org.netbeans.api.debugger.jpda.ObjectVariable;
import org.netbeans.api.debugger.jpda.Variable;
import org.netbeans.modules.debugger.jpda.truffle.vars.TruffleVariable;
import org.netbeans.modules.java.lsp.server.LspSession;
+import
org.netbeans.modules.java.lsp.server.debugging.breakpoints.NbBreakpointsRequestHandler;
+import
org.netbeans.modules.java.lsp.server.debugging.attach.NbAttachRequestHandler;
import org.netbeans.modules.java.lsp.server.debugging.launch.NbDebugSession;
import
org.netbeans.modules.java.lsp.server.debugging.launch.NbDisconnectRequestHandler;
import
org.netbeans.modules.java.lsp.server.debugging.launch.NbLaunchRequestHandler;
-import
org.netbeans.modules.java.lsp.server.debugging.breakpoints.NbBreakpointsRequestHandler;
import
org.netbeans.modules.java.lsp.server.debugging.variables.NbVariablesRequestHandler;
import org.netbeans.modules.java.lsp.server.debugging.utils.ErrorUtilities;
import org.netbeans.modules.nativeimage.api.debug.EvaluateException;
@@ -99,6 +95,7 @@ public final class NbProtocolServer implements
IDebugProtocolServer, LspSession.
private final DebugAdapterContext context;
private final NbLaunchRequestHandler launchRequestHandler = new
NbLaunchRequestHandler();
+private final NbAttachRequestHandler attachRequestHandler = new
NbAttachRequestHandler();
private final NbDisconnectRequestHandler disconnectRequestHandler = new
NbDisconnectRequestHandler();
private final NbBreakpointsRequestHandler breakpointsRequestHandler = new
NbBreakpointsRequestHandler();
private final NbVariablesRequestHandler variablesRequestHandler = new
NbVariablesRequestHandler();
@@ -172,6 +169,11 @@ public final class NbProtocolServer implements
IDebugProtocolServer, LspSession.
}
@Override
+public CompletableFuture attach(Map args) {
+return attachRequestHandler.attach(args, context);
+}
+
+@Override
public CompletableFuture disconnect(DisconnectArguments args) {
return disconnectRequestHandler.disconnect(args, context);
}
diff --git
[jira] [Created] (NETBEANS-5737) Ubuntu - desktop icon not paired to ronning aplication icon
Pavel Cibulka created NETBEANS-5737: --- Summary: Ubuntu - desktop icon not paired to ronning aplication icon Key: NETBEANS-5737 URL: https://issues.apache.org/jira/browse/NETBEANS-5737 Project: NetBeans Issue Type: Improvement Components: platform - installer Affects Versions: 12.4 Environment: Ubuntu 21.04 Reporter: Pavel Cibulka Attachments: image-2021-05-31-09-26-54-474.png, image-2021-05-31-09-29-38-395.png, image-2021-05-31-09-29-47-962.png When installing Netbeans 12.4 with installer on Ubuntu, it will create desktop icon. This file doesn't contain StartupWMClass variable. System will not pair desktop icon to running aplication icon. There will be two icons in favorite bar: !image-2021-05-31-09-26-54-474.png! This can be fixed by adding correct StartupWMClass setting into desktop icon file: !image-2021-05-31-09-29-38-395.png! !image-2021-05-31-09-29-47-962.png! installer file: Apache-NetBeans-12.4-bin-linux-x64.sh desktop icon file: Apache NetBeans-12.4.desktop added line: StartupWMClass=Apache NetBeans IDE 12.4 -- 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-5736) Clicking in "Projects" tree should work along entire row
[ https://issues.apache.org/jira/browse/NETBEANS-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5736: -- Description: In the TreeView component, which is used for the "Projects" tab in the NetBeans IDE, the user should be able to click anywhere along the width of the component to select a given node. (Or at least, in the empty space to the right of a component). Similarly, during drag-and-drop operations, the user should be able to drop anywhere to the right of the node's icon. This usability issue came up during user testing of a NetBeans Platform application. The user complained that files with a short filename were harder to click than files with long names. The user, a software engineer, pointed out that the equivalent tree component in IntelliJ allows the entire row to be clicked or dragged at to target a given node. TreeView's behavior is derived from its superclass JTree. The OutlineView component does not have the same problem, as it derives from ETable and in turn JTable. PR to follow... was: In the TreeView component, which is used for the "Projects" tab in the NetBeans IDE, the user should be able to click anywhere along the width of the component to select a given node. Or at least, in the empty space to the right of a component). Similarly, during drag-and-drop operations, the user should be able to drop anywhere to the right of the node's icon. This usability issue came up during user testing of a NetBeans Platform application. The user complained that files with a short filename were harder to click than files with long names. The user, a software engineer, pointed out that the equivalent tree component in IntelliJ allows the entire row to be clicked or dragged at to target a given node. TreeView's behavior is derived from its superclass JTree. The OutlineView component does not have the same problem, as it derives from ETable and in turn JTable. PR to follow... > Clicking in "Projects" tree should work along entire row > > > Key: NETBEANS-5736 > URL: https://issues.apache.org/jira/browse/NETBEANS-5736 > Project: NetBeans > Issue Type: Improvement > Components: platform - Explorer >Affects Versions: 12.2 > Environment: All LAFs (but tested on the Windows LAFs and MacOS/Aqua > LAFs). >Reporter: Eirik Bakke >Priority: Major > > In the TreeView component, which is used for the "Projects" tab in the > NetBeans IDE, the user should be able to click anywhere along the width of > the component to select a given node. (Or at least, in the empty space to the > right of a component). Similarly, during drag-and-drop operations, the user > should be able to drop anywhere to the right of the node's icon. > This usability issue came up during user testing of a NetBeans Platform > application. The user complained that files with a short filename were harder > to click than files with long names. The user, a software engineer, pointed > out that the equivalent tree component in IntelliJ allows the entire row to > be clicked or dragged at to target a given node. > TreeView's behavior is derived from its superclass JTree. The OutlineView > component does not have the same problem, as it derives from ETable and in > turn JTable. > PR to follow... -- 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-5736) Clicking in "Projects" tree should work along entire row
Eirik Bakke created NETBEANS-5736: - Summary: Clicking in "Projects" tree should work along entire row Key: NETBEANS-5736 URL: https://issues.apache.org/jira/browse/NETBEANS-5736 Project: NetBeans Issue Type: Improvement Components: platform - Explorer Affects Versions: 12.2 Environment: All LAFs (but tested on the Windows LAFs and MacOS/Aqua LAFs). Reporter: Eirik Bakke In the TreeView component, which is used for the "Projects" tab in the NetBeans IDE, the user should be able to click anywhere along the width of the component to select a given node. Or at least, in the empty space to the right of a component). Similarly, during drag-and-drop operations, the user should be able to drop anywhere to the right of the node's icon. This usability issue came up during user testing of a NetBeans Platform application. The user complained that files with a short filename were harder to click than files with long names. The user, a software engineer, pointed out that the equivalent tree component in IntelliJ allows the entire row to be clicked or dragged at to target a given node. TreeView's behavior is derived from its superclass JTree. The OutlineView component does not have the same problem, as it derives from ETable and in turn JTable. PR to follow... -- 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-5732) Profiler not working with Maven Project on MacOS
[
https://issues.apache.org/jira/browse/NETBEANS-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354234#comment-17354234
]
Svatopluk Dedic commented on NETBEANS-5732:
---
Have you customized your maven actions (is there a nb-actions.xml in the
project directory) ? If so, pls. attach.
> Profiler not working with Maven Project on MacOS
>
>
> Key: NETBEANS-5732
> URL: https://issues.apache.org/jira/browse/NETBEANS-5732
> Project: NetBeans
> Issue Type: Bug
> Components: profiler - IDE
>Affects Versions: 12.4
>Reporter: Peter Hull
>Priority: Major
> Attachments: IDE_log.txt
>
>
> Profiler does not start when attempting to profile a Swing app using a maven
> project on MacOS.
> Expected: profiler does start
> Actual: Shows an error in the output tab, given below:
> cd /Users/peterhull/Projects/mavenproject2;
> JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
> "/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/java/maven/bin/mvn"
> "-Dexec.vmArgs='-agentpath:\\'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib\\'=\\'/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib\\',5140,10'
> -XX:+HeapDumpOnOutOfMemoryError
> '-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> '" "-Dexec.args=${exec.vmArgs} -classpath %classpath ${exec.mainClass}
> ${exec.appArgs}" -Dexec.mainClass=com.nowhere.mavenproject2.NewJFrame
> -Dexec.executable=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home/bin/java
> "-Dprofiler.jvmargs.all= -XX:+HeapDumpOnOutOfMemoryError
> -XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> -agentpath:'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib'='/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib',5140,10"
> "-Dprofiler.jvmargs.arg1=-agentpath:'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib'='/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib',5140,10"
> -Dprofiler.jvmargs.arg2=-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> -Dprofiler.jvmargs.arg3=-XX:+HeapDumpOnOutOfMemoryError -Dexec.appArgs=
> org.codehaus.mojo:exec-maven-plugin:3.0.0:exec
> Running NetBeans Compile On Save execution. Phase execution is skipped and
> output directories of dependency projects (with Compile on Save turned on)
> will be used instead of their jar artifacts.
> Scanning for projects...
> -< com.nowhere:mavenproject2 >--
> Building mavenproject2 1.0-SNAPSHOT
> [ jar ]-
> --- exec-maven-plugin:3.0.0:exec (default-cli) @ mavenproject2 ---
> Error occurred during initialization of VM
> Could not find agent library \/Applications/NetBeans/Apache in absolute path,
> with error: dlopen(\/Applications/NetBeans/Apache, 1): image not found
> Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:982)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:929)
> at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:457)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
>
