Additional menu

Crunchify

Largest free Technical and Blogging resource site for Beginner. We help clients transform their great ideas into reality!

Crunchify   Eclipse IDE Tutorials   How to fix Cannot change version of project facet Dynamic Web Module t ...

How to fix Cannot change version of project facet Dynamic Web Module to 3.0 Error in Eclipse

Updated on by App   62

Cannot change version of project facet Dynamic Web Module to 3.0

Today while converting Dynamic Web Project to Maven project I got below Error:

Cannot change version of project facet Dynamic Web Module to 3.0 
One or more constraints have not been satisfied

What steps I’ve performed to fix this?

In order to fix this first thing I did is to change Project Facets settings.

  1. Right click on Project in Eclipse
  2. Click on Properties
  3. Click on Project Facets Tab
  4. Change value from 3.1 to 3.0 for Dynamic Web Module as mentioned in below image.

Eclipse Project facets - Dynamic Web Module

Did it fix my problem? Unfortunately No

I was not able to apply setting as Apply and OK button was grayed out with error msg: Cannot change version of project facet Dynamic Web Module to 3.0.

I was literally stuck at this point, then How did I fix this issue?

Step-1

  • Go to your Eclipse Workspace location
  • If you don’t find location then
    • Right click on project
    • Click on Resource
    • Go to your Location

Find Workspace Resource Properties - Crunchify Workspace

Step-2

Go to location and open file <workspace>/.settings/org.eclipse.wst.common.project.facet.core.xml.

Find Eclipse org.eclipse.wst.common.project.facet.core.xml Path

Step-3

Modify version for jst.web property to 3.0 from 3.1 and save file.

<?xml version="1.0" encoding="UTF-8"?>
<faceted-project>
  <fixed facet="wst.jsdt.web"/>
  <installed facet="jst.jaxrs" version="2.0"/>
  <installed facet="wst.jsdt.web" version="1.0"/>
  <installed facet="java" version="1.8"/>
  <installed facet="jst.web" version="3.0"/>
</faceted-project>

Step-4

  • Refresh project
    • Right click on Project
    • Refresh (F5)
  • Clean project
    • Click on Project
    • Select Clean
  • Again
    • Right-click on project name
    • Click on Maven
    • Update project
  • Now checkout Project Facets screen again and error should be gone for you.

There will not be any error for Dynamic Web Module - Crunchify

Let me know if this solution doesn’t work for you, I’ll debug more.

If you liked this article, then please share it on social media. Have a question or suggestion? Please leave a comment to start the discussion.

Suggested Articles...

  1. How to solve “Dynamic Web Module 3.1 requires Java 1.7 or newer” in Eclipse
  2. Ever wondered difference between Dynamic Web Module 3.0 and 3.1? How to Setup 3.1 Correct way in Eclipse?
  3. How to Install and Configure Elasticsearch on your Dev/Production environment?
  4. Simplest Spring MVC Framework Tutorial – Hello World Example with UI (JSP) Page
  5. What is pom.xml (Project Object Model)? Sample pom.xml for you to use in your Dynamic Web Project (Java / J2EE)
  6. How to Create a .war file using Eclipse Maven Plugin? Apache ‘maven-war-plugin’ usage

About App

I'm an Engineer by profession, Blogger by passion & Founder of Crunchify, LLC, the largest free blogging & technical resource site for beginners. Love SEO, SaaS, #webperf, WordPress, Java. With over 16 millions+ pageviews/month, Crunchify has changed the life of over thousands of individual around the globe teaching Java & Web Tech for FREE.

Reader Interactions

  62 Comments...

  2. Federico Cauti says

    From time to time I have to apply this procedure in my Eclipse 4.14.0, thank you very much!

    Reply

  5. hemanshu says

    Check the Java version in the Java Build libraries – JRE system library – this could be old JRE 1.5 library , change it to 1.8 or above

    Reply

    • App Shah says

      Hi Hemanshu – I double checked. Thanks for your suggestion but it is upto individual user. They may not have JRE 1.5 install at all.

      Depends on their setup, please update to latest JRE and it should solve an issue.

      Reply

  11. Marcos Feijó de Almeida says

    I’m still having problems with this. Eclipse complains about “project Cannot change version of project facet Dynamic Web Module to 2.3”,

    The application runs normally, though.

    The project consists only of the basic strucure that was create by Maven:
    https://uploads.disquscdn.com/images/08412339d66fb88855c1efd60e01f5d0047e3aba176ffd0fd03d703c9dd0ce63.jpg

    The error message is this:

    https://uploads.disquscdn.com/images/9655c8f188299bbd4ad331d1870ced78fe1410f9d045cfc67c20619f13f4ef8d.jpg

    This is the pom.xml:


    4.0.0

    com.example.group
    artifact war 0.0.1-SNAPSHOT
    artifact Maven Webapp
    http://maven.apache.org

    UTF-8 1.8
    1.8



    junit
    junit
    4.12
    test


    javax.servlet
    javax.servlet-api
    4.0.0
    provided



    artifact org.apache.maven.plugins
    maven-war-plugin
    3.2.2

    false

    Finally, this is the web.xml:

    < ?xml version="1.0" encoding="UTF-8"?>

    artifact

    index.html

    I think that there is a bug in Eclipse or in M2.

    Thanks!

    Reply

    • App Shah says

      Hi Marcos – Thanks for sharing pictures and detailed code.

      Both pom.xml and web.xml looks correct. Could you try changing Dynamic Web Project to version 3.1?

      Also, try following this tips:
      – Right click on error
      – Click on Quick fix

      I hope that helps.

      Reply

      • Marcos Feijó de Almeida says

        As far I’m concerned, there is an only way to completely avoid this problem: create your own project structure from scratch, with all the directories needed, place an deployment descriptor in the src/main/webapp/WEB-INF and the pom.xml in the root directory.

        Next, you import it to Eclipse (as an existing Maven project) and you’re going to get rid of all these problems.

        The directories needed under the project root directory are:

        a) src/main/java
        b) src/main/resources
        c) src/main/webapp/WEB-INF
        d) src/test/java
        e) src/test/resources

        You can start from a web.xml file like this:




        index.html


        You´ll also need a pom.xml from where to begin to work with:

        4.0.0

        some.groupid
        your-new-project
        1.0-SNAPSHOT

        war

        Project Name

        UTF-8 1.8
        1.8
        4.12
        3.1.0


        your-new-project



        junit
        junit
        ${junit.version}


        javax.servlet
        javax.servlet-api
        ${javax.servlet.version}
        provided

        Do it once, use it many times!

        Best regards,
        Marcos

        Reply

    • App Shah says

      Thanks Subramanya for your comment.

      Yeah. It’s Eclipse bug. I would say with hundreds of custom setting sometimes it failed to update some setting and causes this kind of issue.

      I’ve personally noticed quite a few over last few years. Definitely with each latest version it’s been very stable.

      Reply

  13. wheeliebin says

    My understanding is that you are just disguising the problem – is it safe telling the setup that a different version is installed? A solution I found elsewhere which I believe is a cleaner solution is to uncheck the Dynamic Web Module in the Project Facets and then update the Maven project (project->Maven->Update Project)

    Reply

  17. amit rawat says

    Hi, i tried your solution and after clean it shows version 3.0 but after Right-click on project name…maven…update project… i am falling back to dynamic web module version 3.1

    Reply

    • App Shah says

      Hi Amit Rawat – hmm.. you are right. I’ve just updated above tutorial with your steps too. Appreciate your feedback.

      Reply

  19. Doug says

    Solution was perfect, and well detailed. I was looking everywhere for answer. I only had to do one additional step at very end: Right-click on project name…maven…update project…select project from list…click OK.
    Thanks.

    Reply

  20. Johan says

    It still shows the error.
    Cannot change version of project facet Dynamic Web Module to 3.0. Maven Java EE Configuration Problem

    Reply

      • App Shah says

        Hi Johan and Archana – can you share exception/error screenshot please? Would like to debug. For almost all my readers above solution worked great.

        Must be something related to Eclipse workspace.

        Reply

  21. Chad says

    Thanks for this. However, my issue was something more sinister. I did find it while following your post. Turns out my jst. web entry appeared more than once. I removed the duplicate and updated the maven project and it fixed itself right off.

    Reply

  26. cyberglad says

    As specified below, this only fixes Eclipse error, but now you can’t build using Maven without compiler plugin. You can still create WAR using a normal Eclipse export.And above all, how the heck Maven Compiler block in pom.xml is related to Dynamic Facet error, anyone can clearly explain that?

    Reply

    • App Shah says

      Very valid point. I revisited the tutorial again and updated steps. Could you try following steps 1 to 4 again? Let me know if you have any more question.

      Happy coding and have a great day.

      Reply

  27. Roland says

    This fixes the eclipse error, but now that you deleted the maven-war-plugin from pom.xml, the build fails because it’s unable to create the war file. So is this the right solution?

    Reply

    • App Shah says

      Hi Roland – I’m able to create .war file even with above changes. Could you please share screenshot or some log? I might have some other war dependency and didn’t face this issue. I need to debug more.

      Reply

    • App Shah says

      Hi Roland – I’ve updated steps again which will not create maven-war-plugin error any more. Can you try one more time and let me know?

      Reply

  28. App Shah says

    I just tried that. It didn’t work for me. Instead threw below error:

    Description	Resource	Path	Location	Type
Referenced file contains errors (http://java.sun.com/xml/ns/javaee/web-app_3_1.xsd).  For more information, right click on the message in the Problems View and select "Show Details..."	web.xml	/CrunchifySpringMVCTutorial/WebContent/WEB-INF	line 1	XML Problem
    Reply

  30. alain touret says

    Following these steps I continued to get stuck because I previously generated the web.xml (with a right clic on /Deployment Descriptor + Generate Deployment Descriptor Stub). I resolved this issue deleting the src/main/webapp/WEB-INF/web.xml file. Note that web.xml is not mandatory anymore with servlet version later than 3.0 if you use annotations.

    Reply

Leave a Reply

Comment Policy: We welcome relevant and respectful comments. All comments are manually moderated and those deemed to be spam or solely promotional will be deleted.