[jira] [Closed] (NETBEANS-5163) Netbeans 12.2 nb-javac can't parse correct java code (works with 12.1 and before)
[ https://issues.apache.org/jira/browse/NETBEANS-5163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Bläsing closed NETBEANS-5163. -- Resolution: Fixed > Netbeans 12.2 nb-javac can't parse correct java code (works with 12.1 and > before) > - > > Key: NETBEANS-5163 > URL: https://issues.apache.org/jira/browse/NETBEANS-5163 > Project: NetBeans > Issue Type: Bug > Components: java - Editor >Affects Versions: 12.2 > Environment: Arch Linux with Jebrains JDK 11.0.9 >Reporter: Andreas Reichel >Assignee: Akshay Gupta >Priority: Major > Attachments: ThreadListWithSemaphore.java, ThreadMap.java, > image-2020-12-17-13-20-46-760.png, image-2020-12-17-13-20-52-170.png > > > unfortunately I face some serious problems with 12.2 and the nb-javac plugin: > 2 valid Java Classes will be marked as invalid code in the UI for no reason. > It is completely valid code, which compiles fine in the shell. Also, the same > project opens perfectly fine in Netbeans 12.1 and before (see screenshots for > illustration). > > Furthermore, I can reproduce this problem with the same code on 2 different > linux machines. The interesting part is: It affects always the same 2 > classes, while hundreds of other classes validate and compile without any > issues. > Although I was unable to spot anythign exceptional about these 2 classes. I > do not understand, what is going on. > > I have attached the 2 classes, maybe someone wants to have a look at it. > Please tell me, what further information I may provide. > > > !image-2020-12-17-13-20-52-170.png! > > !image-2020-12-17-13-20-46-760.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] [Created] (NETBEANS-5892) Java Maven Web Project not created properly
Thomas Schuster created NETBEANS-5892: - Summary: Java Maven Web Project not created properly Key: NETBEANS-5892 URL: https://issues.apache.org/jira/browse/NETBEANS-5892 Project: NetBeans Issue Type: Bug Affects Versions: 12.4 Environment: *NetBeans* version 12.4 *JDK* version zulu16.32.15 (default), JDK version 8 and 11 installed as well *OS* Windows 10 pro, Version 20H2, Build 19042.1110 Reporter: Thomas Schuster Attachments: 1_used_create_dialog.png, 2_bundled_maven.png, 3_pom.png, 4_index_page_missing.png, mavenproject2.zip, mavenproject3.zip *Short description* Using the create Java Maven Web project results in a project that cannot be build for nor run on a Jakarta EE 8 server. I provided the created result (mavenproject2.zip) and an altered project which can be built and deployed (mavenproject3.zip) - I would expect the latter to be generated. *Exact steps* # Create new project (Java with Maven, Web Application) # Execute Clean & Build on this project # Build will fail because of default maven-war plugin (Version 2.2) of bundled maven. version. # Now execute Clean & Build again with success # Execute Run. # Deployment will fail because of unsupported Java version. Generator creates a project with compiler set to Java 11. # Reset compiler version to Java 8. # Now execute Clean & Build again with success. # Execute Run, project is successfully deployed. # Welcome page is triggered but not found (not created in fact). *Actual results* Web project that includes microprofile configuration and cannot be build and deployed directly from generated sources. Java compiler level is set to be 11, there are some configuration options based on IBM (Openliberty I believe) and there are microprofile configuration options being used in a sample Jax RS service. Minor: The pom.xml is not indented properly. *Expected results* Web project that is Jakarta EE 8 compliant and that can be build and run on a Jakarta EE Server (in my case: Payara Server 5.201.4). Also, in my opinion the project should deliver a welcome page and be minimal in terms of dependencies and contents (that means also removing microprofile configuration). -- 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-5892) Java Maven Web Project not created properly
[ https://issues.apache.org/jira/browse/NETBEANS-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Schuster updated NETBEANS-5892: -- Attachment: errorlog1.txt > Java Maven Web Project not created properly > --- > > Key: NETBEANS-5892 > URL: https://issues.apache.org/jira/browse/NETBEANS-5892 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.4 > Environment: *NetBeans* version > 12.4 > *JDK* version > zulu16.32.15 (default), JDK version 8 and 11 installed as well > *OS* > Windows 10 pro, Version 20H2, Build 19042.1110 >Reporter: Thomas Schuster >Priority: Major > Attachments: 1_used_create_dialog.png, 2_bundled_maven.png, > 3_pom.png, 4_index_page_missing.png, errorlog1.txt, mavenproject2.zip, > mavenproject3.zip > > > *Short description* > Using the create Java Maven Web project results in a project that cannot be > build for nor run on a Jakarta EE 8 server. I provided the created result > (mavenproject2.zip) and an altered project which can be built and deployed > (mavenproject3.zip) - I would expect the latter to be generated. > *Exact steps* > # Create new project (Java with Maven, Web Application) > # Execute Clean & Build on this project > # Build will fail because of default maven-war plugin (Version 2.2) of > bundled maven. version. > # Now execute Clean & Build again with success > # Execute Run. > # Deployment will fail because of unsupported Java version. Generator > creates a project with compiler set to Java 11. > # Reset compiler version to Java 8. > # Now execute Clean & Build again with success. > # Execute Run, project is successfully deployed. > # Welcome page is triggered but not found (not created in fact). > *Actual results* > Web project that includes microprofile configuration and cannot be build and > deployed directly from generated sources. Java compiler level is set to be > 11, there are some configuration options based on IBM (Openliberty I believe) > and there are microprofile configuration options being used in a sample Jax > RS service. > Minor: The pom.xml is not indented properly. > *Expected results* > Web project that is Jakarta EE 8 compliant and that can be build and run on a > Jakarta EE Server (in my case: Payara Server 5.201.4). > Also, in my opinion the project should deliver a welcome page and be minimal > in terms of dependencies and contents (that means also removing microprofile > configuration). -- 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-5892) Java Maven Web Project not created properly
[ https://issues.apache.org/jira/browse/NETBEANS-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Schuster updated NETBEANS-5892: -- Attachment: errorlog2.txt > Java Maven Web Project not created properly > --- > > Key: NETBEANS-5892 > URL: https://issues.apache.org/jira/browse/NETBEANS-5892 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.4 > Environment: *NetBeans* version > 12.4 > *JDK* version > zulu16.32.15 (default), JDK version 8 and 11 installed as well > *OS* > Windows 10 pro, Version 20H2, Build 19042.1110 >Reporter: Thomas Schuster >Priority: Major > Attachments: 1_used_create_dialog.png, 2_bundled_maven.png, > 3_pom.png, 4_index_page_missing.png, errorlog1.txt, errorlog2.txt, > mavenproject2.zip, mavenproject3.zip > > > *Short description* > Using the create Java Maven Web project results in a project that cannot be > build for nor run on a Jakarta EE 8 server. I provided the created result > (mavenproject2.zip) and an altered project which can be built and deployed > (mavenproject3.zip) - I would expect the latter to be generated. > *Exact steps* > # Create new project (Java with Maven, Web Application) > # Execute Clean & Build on this project > # Build will fail because of default maven-war plugin (Version 2.2) of > bundled maven. version. > # Now execute Clean & Build again with success > # Execute Run. > # Deployment will fail because of unsupported Java version. Generator > creates a project with compiler set to Java 11. > # Reset compiler version to Java 8. > # Now execute Clean & Build again with success. > # Execute Run, project is successfully deployed. > # Welcome page is triggered but not found (not created in fact). > *Actual results* > Web project that includes microprofile configuration and cannot be build and > deployed directly from generated sources. Java compiler level is set to be > 11, there are some configuration options based on IBM (Openliberty I believe) > and there are microprofile configuration options being used in a sample Jax > RS service. > Minor: The pom.xml is not indented properly. > *Expected results* > Web project that is Jakarta EE 8 compliant and that can be build and run on a > Jakarta EE Server (in my case: Payara Server 5.201.4). > Also, in my opinion the project should deliver a welcome page and be minimal > in terms of dependencies and contents (that means also removing microprofile > configuration). -- 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-5892) Java Maven Web Project not created properly
[ https://issues.apache.org/jira/browse/NETBEANS-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Schuster updated NETBEANS-5892: -- Description: *Short description* Using the create Java Maven Web project results in a project that cannot be build for nor run on a Jakarta EE 8 server. I provided the created result (mavenproject2.zip) and an altered project which can be built and deployed (mavenproject3.zip) - I would expect the latter to be generated. *Exact steps* # Create new project (Java with Maven, Web Application) # Execute Clean & Build on this project # Build will fail because of default maven-war plugin (Version 2.2) of bundled maven. version. (see errorlog1.txt) # Now execute Clean & Build again with success # Execute Run. # Deployment will fail because of unsupported Java version. Generator creates a project with compiler set to Java 11. (see errorlog2.txt) # Reset compiler version to Java 8. # Now execute Clean & Build again with success. # Execute Run, project is successfully deployed. # Welcome page is triggered but not found (not created in fact). *Actual results* Web project that includes microprofile configuration and cannot be build and deployed directly from generated sources. Java compiler level is set to be 11, there are some configuration options based on IBM (Openliberty I believe) and there are microprofile configuration options being used in a sample Jax RS service. Minor: The pom.xml is not indented properly. *Expected results* Web project that is Jakarta EE 8 compliant and that can be build and run on a Jakarta EE Server (in my case: Payara Server 5.201.4). Also, in my opinion the project should deliver a welcome page and be minimal in terms of dependencies and contents (that means also removing microprofile configuration). was: *Short description* Using the create Java Maven Web project results in a project that cannot be build for nor run on a Jakarta EE 8 server. I provided the created result (mavenproject2.zip) and an altered project which can be built and deployed (mavenproject3.zip) - I would expect the latter to be generated. *Exact steps* # Create new project (Java with Maven, Web Application) # Execute Clean & Build on this project # Build will fail because of default maven-war plugin (Version 2.2) of bundled maven. version. # Now execute Clean & Build again with success # Execute Run. # Deployment will fail because of unsupported Java version. Generator creates a project with compiler set to Java 11. # Reset compiler version to Java 8. # Now execute Clean & Build again with success. # Execute Run, project is successfully deployed. # Welcome page is triggered but not found (not created in fact). *Actual results* Web project that includes microprofile configuration and cannot be build and deployed directly from generated sources. Java compiler level is set to be 11, there are some configuration options based on IBM (Openliberty I believe) and there are microprofile configuration options being used in a sample Jax RS service. Minor: The pom.xml is not indented properly. *Expected results* Web project that is Jakarta EE 8 compliant and that can be build and run on a Jakarta EE Server (in my case: Payara Server 5.201.4). Also, in my opinion the project should deliver a welcome page and be minimal in terms of dependencies and contents (that means also removing microprofile configuration). > Java Maven Web Project not created properly > --- > > Key: NETBEANS-5892 > URL: https://issues.apache.org/jira/browse/NETBEANS-5892 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.4 > Environment: *NetBeans* version > 12.4 > *JDK* version > zulu16.32.15 (default), JDK version 8 and 11 installed as well > *OS* > Windows 10 pro, Version 20H2, Build 19042.1110 >Reporter: Thomas Schuster >Priority: Major > Attachments: 1_used_create_dialog.png, 2_bundled_maven.png, > 3_pom.png, 4_index_page_missing.png, errorlog1.txt, errorlog2.txt, > mavenproject2.zip, mavenproject3.zip > > > *Short description* > Using the create Java Maven Web project results in a project that cannot be > build for nor run on a Jakarta EE 8 server. I provided the created result > (mavenproject2.zip) and an altered project which can be built and deployed > (mavenproject3.zip) - I would expect the latter to be generated. > *Exact steps* > # Create new project (Java with Maven, Web Application) > # Execute Clean & Build on this project > # Build will fail because of default maven-war plugin (Version 2.2) of > bundled maven. version. (see errorlog1.txt) > # Now execute Clean & Build again with success > # Execute Run. > # Deployment will fail because of unsupported Java version. Generator > creates a project with compiler
[jira] [Created] (NETBEANS-5893) NB does not recognize that Glassfish 6.1 RC1 can run under JDK 11.
Kenneth Fogel created NETBEANS-5893: --- Summary: NB does not recognize that Glassfish 6.1 RC1 can run under JDK 11. Key: NETBEANS-5893 URL: https://issues.apache.org/jira/browse/NETBEANS-5893 Project: NetBeans Issue Type: Bug Environment: Windows 10 AdoptOpenJDK Java 11.0.11.9 NetBeans 2.4 & 2.5 Glassfish 6.1 RC1 Reporter: Kenneth Fogel Both NB 12.4 and 12.5, running under AdoptOpenJDK Java 11.0.11.9 will not start Glassfish 6.1 RC1. The dialog that pops up is that it cannot find a suitable JDK and refuses JDK 11 despite the fact that this version will run under Java 11. I can start GlassFish from the command line. When I started Glassfish 6.1 under JDK 11 and then added it as a service to NB, a request for the admin console displayed the readme file for Glassfish and no admin console. -- 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-5894) Cannot start Payara 6.2021.1 Alpha 1
Kenneth Fogel created NETBEANS-5894: --- Summary: Cannot start Payara 6.2021.1 Alpha 1 Key: NETBEANS-5894 URL: https://issues.apache.org/jira/browse/NETBEANS-5894 Project: NetBeans Issue Type: Bug Environment: Windows 10 AdoptOpenJDK 11.0.11.9 NetBeans 2.4 and NetBeans 2.5 Payara 6.2021.1 Alpha 1 Reporter: Kenneth Fogel Similar to my last issue with Glassfish 6.1, when I try to add Payara 6 to the Server list with Add Server Instance and select the location for Payara 6 it will not advance past Server Location. It does not complain about the version of Java, it just won't advance past Server Location and there is no indication why. NB does properly display the Payara version when I first enter the location. As I press Next, the server version disappears and nothing happens. -- 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
