[jira] [Updated] (NETBEANS-5902) Generate Web Service Client fails on build
[ https://issues.apache.org/jira/browse/NETBEANS-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Schuster updated NETBEANS-5902: -- Description: Using the Dialog (see picture) to create a new Web Service Client (SOAP) ends up with source that won't build. Issue is create because of plugin configuration for jaxws maven plugin. Instead of: {color:#808080}<{color}{color:#569cd6}groupId{color}{color:#808080}>{color}{color:#d4d4d4}org.jvnet.jax-ws-commons{color}{color:#808080}{color} {color:#808080}<{color}{color:#569cd6}artifactId{color}{color:#808080}>{color}{color:#d4d4d4}jaxws-maven-plugin{color}{color:#808080}{color} {color:#808080}<{color}{color:#569cd6}version{color}{color:#808080}>{color}{color:#d4d4d4}2.3{color}{color:#808080}{color} The generator should use: {color:#808080}<{color}{color:#569cd6}groupId{color}{color:#808080}>{color}{color:#d4d4d4}org.codehaus.mojo{color}{color:#808080}{color} {color:#d4d4d4} {color}{color:#808080}<{color}{color:#569cd6}artifactId{color}{color:#808080}>{color}{color:#d4d4d4}jaxws-maven-plugin{color}{color:#808080}{color} {color:#d4d4d4} {color}{color:#808080}<{color}{color:#569cd6}version{color}{color:#808080}>{color}{color:#d4d4d4}2.6{color}{color:#808080}{color} Additionally the metro dependency could be updated from 2.3 to 2.4.6. was: Using the Dialog (see picture) to create a new Web Service Client (SOAP) ends up with source that won't build. Issue is create because of plugin configuration for jaxws maven plugin. !image-2021-08-06-17-03-43-405.png! Instead of: {color:#808080}<{color}{color:#569cd6}groupId{color}{color:#808080}>{color}{color:#d4d4d4}org.jvnet.jax-ws-commons{color}{color:#808080}{color} {color:#808080}<{color}{color:#569cd6}artifactId{color}{color:#808080}>{color}{color:#d4d4d4}jaxws-maven-plugin{color}{color:#808080}{color} {color:#808080}<{color}{color:#569cd6}version{color}{color:#808080}>{color}{color:#d4d4d4}2.3{color}{color:#808080}{color} The generator should use: {color:#808080}<{color}{color:#569cd6}groupId{color}{color:#808080}>{color}{color:#d4d4d4}org.codehaus.mojo{color}{color:#808080}{color} {color:#d4d4d4} {color}{color:#808080}<{color}{color:#569cd6}artifactId{color}{color:#808080}>{color}{color:#d4d4d4}jaxws-maven-plugin{color}{color:#808080}{color} {color:#d4d4d4} {color}{color:#808080}<{color}{color:#569cd6}version{color}{color:#808080}>{color}{color:#d4d4d4}2.6{color}{color:#808080}{color} Additionally the metro dependency could be updated from 2.3 to 2.4.6. > Generate Web Service Client fails on build > -- > > Key: NETBEANS-5902 > URL: https://issues.apache.org/jira/browse/NETBEANS-5902 > Project: NetBeans > Issue Type: Bug > Environment: Apache NetBeans 12.4 > OpenJDK 16 (default) as well as 8 and 11 as Java Platforms in NetBeans > Windows 10 Pro H2 > >Reporter: Thomas Schuster >Priority: Minor > Attachments: jaxws.png > > > Using the Dialog (see picture) to create a new Web Service Client (SOAP) ends > up with source that won't build. > Issue is create because of plugin configuration for jaxws maven plugin. > Instead of: > > {color:#808080}<{color}{color:#569cd6}groupId{color}{color:#808080}>{color}{color:#d4d4d4}org.jvnet.jax-ws-commons{color}{color:#808080}{color} > > {color:#808080}<{color}{color:#569cd6}artifactId{color}{color:#808080}>{color}{color:#d4d4d4}jaxws-maven-plugin{color}{color:#808080}{color} > > {color:#808080}<{color}{color:#569cd6}version{color}{color:#808080}>{color}{color:#d4d4d4}2.3{color}{color:#808080}{color} > The generator should use: > > {color:#808080}<{color}{color:#569cd6}groupId{color}{color:#808080}>{color}{color:#d4d4d4}org.codehaus.mojo{color}{color:#808080}{color} > {color:#d4d4d4} > {color}{color:#808080}<{color}{color:#569cd6}artifactId{color}{color:#808080}>{color}{color:#d4d4d4}jaxws-maven-plugin{color}{color:#808080}{color} > {color:#d4d4d4} > {color}{color:#808080}<{color}{color:#569cd6}version{color}{color:#808080}>{color}{color:#d4d4d4}2.6{color}{color:#808080}{color} > Additionally the metro dependency could be updated from 2.3 to 2.4.6. -- 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-5902) Generate Web Service Client fails on build
[ https://issues.apache.org/jira/browse/NETBEANS-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Schuster updated NETBEANS-5902: -- Attachment: jaxws.png > Generate Web Service Client fails on build > -- > > Key: NETBEANS-5902 > URL: https://issues.apache.org/jira/browse/NETBEANS-5902 > Project: NetBeans > Issue Type: Bug > Environment: Apache NetBeans 12.4 > OpenJDK 16 (default) as well as 8 and 11 as Java Platforms in NetBeans > Windows 10 Pro H2 > >Reporter: Thomas Schuster >Priority: Minor > Attachments: jaxws.png > > > Using the Dialog (see picture) to create a new Web Service Client (SOAP) ends > up with source that won't build. > Issue is create because of plugin configuration for jaxws maven plugin. > !image-2021-08-06-17-03-43-405.png! > > Instead of: > {color:#808080}<{color}{color:#569cd6}groupId{color}{color:#808080}>{color}{color:#d4d4d4}org.jvnet.jax-ws-commons{color}{color:#808080}{color} > {color:#808080}<{color}{color:#569cd6}artifactId{color}{color:#808080}>{color}{color:#d4d4d4}jaxws-maven-plugin{color}{color:#808080}{color} > {color:#808080}<{color}{color:#569cd6}version{color}{color:#808080}>{color}{color:#d4d4d4}2.3{color}{color:#808080}{color} > The generator should use: > {color:#808080}<{color}{color:#569cd6}groupId{color}{color:#808080}>{color}{color:#d4d4d4}org.codehaus.mojo{color}{color:#808080}{color} > {color:#d4d4d4} > {color}{color:#808080}<{color}{color:#569cd6}artifactId{color}{color:#808080}>{color}{color:#d4d4d4}jaxws-maven-plugin{color}{color:#808080}{color} > {color:#d4d4d4} > {color}{color:#808080}<{color}{color:#569cd6}version{color}{color:#808080}>{color}{color:#d4d4d4}2.6{color}{color:#808080}{color} > Additionally the metro dependency could be updated from 2.3 to 2.4.6. -- 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-5902) Generate Web Service Client fails on build
Thomas Schuster created NETBEANS-5902: - Summary: Generate Web Service Client fails on build Key: NETBEANS-5902 URL: https://issues.apache.org/jira/browse/NETBEANS-5902 Project: NetBeans Issue Type: Bug Environment: Apache NetBeans 12.4 OpenJDK 16 (default) as well as 8 and 11 as Java Platforms in NetBeans Windows 10 Pro H2 Reporter: Thomas Schuster Using the Dialog (see picture) to create a new Web Service Client (SOAP) ends up with source that won't build. Issue is create because of plugin configuration for jaxws maven plugin. !image-2021-08-06-17-03-43-405.png! Instead of: {color:#808080}<{color}{color:#569cd6}groupId{color}{color:#808080}>{color}{color:#d4d4d4}org.jvnet.jax-ws-commons{color}{color:#808080}{color} {color:#808080}<{color}{color:#569cd6}artifactId{color}{color:#808080}>{color}{color:#d4d4d4}jaxws-maven-plugin{color}{color:#808080}{color} {color:#808080}<{color}{color:#569cd6}version{color}{color:#808080}>{color}{color:#d4d4d4}2.3{color}{color:#808080}{color} The generator should use: {color:#808080}<{color}{color:#569cd6}groupId{color}{color:#808080}>{color}{color:#d4d4d4}org.codehaus.mojo{color}{color:#808080}{color} {color:#d4d4d4} {color}{color:#808080}<{color}{color:#569cd6}artifactId{color}{color:#808080}>{color}{color:#d4d4d4}jaxws-maven-plugin{color}{color:#808080}{color} {color:#d4d4d4} {color}{color:#808080}<{color}{color:#569cd6}version{color}{color:#808080}>{color}{color:#d4d4d4}2.6{color}{color:#808080}{color} Additionally the metro dependency could be updated from 2.3 to 2.4.6. -- 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
[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: -- 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] [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] [Created] (NETBEANS-4321) Install Feature during silent install
Thomas Schuster created NETBEANS-4321: - Summary: Install Feature during silent install Key: NETBEANS-4321 URL: https://issues.apache.org/jira/browse/NETBEANS-4321 Project: NetBeans Issue Type: New Feature Affects Versions: Next, 11.3 Reporter: Thomas Schuster Attachments: Screenshot_20200510_224836.png I try to distribute NetBeans within a vritual machine. Therefore I install it via vagrant shell commands during the VM setup and I use the silent option of the NetBeans installer. While this is working, the VM user still has to download and activate features (such as Java SE, see screenshot) afterwards. In order to ship NetBeans ready to go, I would like to see an option to download and activate features during installation and without ui (which I do not have during vagrant setup). Thus, I'd like to suggest extending the installers commandline options to download and install features during installation. -- 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