Solving the error of creating a new Maven project pom file in Eclipse

Dec 7, 2015#dynamic-web-module-3-0 #elcipse #failonmissingwebxml #jdk #maven130

AI Translation

This post is translated from Chinese into English through AI.View Original

AI-generated summary

The article discusses how to resolve an error in Eclipse when creating a Maven project. The error is related to the missing web.xml file and is caused by newer versions of JDK and Eclipse. The article suggests two methods to resolve the error, one by copying and modifying an existing web.xml file, and another by adding specific code to the pom.xml file. The article concludes that the failOnMissingWebXml setting should be set to false, as Dynamic Web Module 3.0 projects do not require a web.xml file by default.

Recently, when creating a Maven project in Eclipse, an error occurred in the pom.xml file: web.xml is missing and is set to true.

After careful investigation, the reason is that the project did not generate the web.xml file, which is related to the newer versions of JDK and Eclipse, where the default mechanism is to generate projects with Dynamic Web Module 3.0.

In general, you would choose to copy a web.xml file and modify it for your own project. However, there is a simpler method:

org.apache.maven.plugins

maven-war-plugin

false

By adding these lines of code, you won't need the web.xml file anymore.

Okay, the problem is resolved! Setting failOnMissingWebXml to false means ignoring the detection mechanism for the missing web.xml file. It is worth mentioning that in the era of Dynamic Web Module 3.0 projects, there is no need for web.xml file to register related content, so the project does not generate web.xml by default.