A new maven web app project doesn't compile on Java 17

[OndroMih]

Apache NetBeans version

Apache NetBeans 18

What happened

A new Jakarta EE Web app (WAR) Maven project doesn't compile on Java 17. Build fails with the following error:

Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.3:war (default-war) on project mavenproject2: Execution default-war of goal org.apache.maven.plugins:maven-war-plugin:2.3:war failed: Unable to load the mojo 'war' in the plugin 'org.apache.maven.plugins:maven-war-plugin:2.3' due to an API incompatibility: org.codehaus.plexus.component.repository.exception.ComponentLookupException: null

How to reproduce

• Create a new project
• Web Application
• Click Next, Finish
• Select the new project in the Projects view
• Right-Click, then select Build

Did this work correctly in an earlier version?

No / Don't know

Operating System

Ubuntu

JDK

Zulu17.36+13-CA, OpenJDK 17.0.4

Apache NetBeans packaging

Apache NetBeans Snap Package

Anything else

This issue can be fixed by editing pom.xml file and setting the version of the WAR plugin to the latest version.

The problem is already fixed in the Maven archetype repo: juneau001/jakartaee10-archetype#2. The archetype needs to be released to Maven Central and version number updated in Netbeans.

Are you willing to submit a pull request?

Yes

[OndroMih]

Hi @juneau001 , can you please release a new version of the Jakarta EE 10 archetype https://github.com/juneau001/jakartaee10-archetype?

[juneau001]

Hi @OndroMih I will update the archetype. Sorry for the delay. I believe someone else is working on developing a different archetype for use with Apache NetBeans as well.

Thanks

[asbachb]

the "different archetype": #5969

[OndroMih]

I see this is a duplicate of #4552, so I'm closing it.

[juneau001]

I have released an update of the Jakarta EE 10 archetype including the enhancements from the PRs that were submitted by @OndroMih https://mvnrepository.com/artifact/io.github.juneau001/webapp-jakartaee10/1.1.0

[asbachb]

Should be fixed within: #6201