Eclipse Development tools error | Community
Skip to main content
Juan_Camacho_I_
Juan_Camacho_I_
March 15, 2016
Solved

Eclipse Development tools error

  • March 15, 2016
  • 24 replies
  • 10284 views

Hi, I started having problems yesterday with my eclipse installation, I am trying to set up Eclipse again with AEM development tools and I don't stop getting this error when creating a project (I have tried both Mars and Luna version that its supposed to be supported by AEM tools):

"The server does not support version 2.4 of the J2EE Web module specification."

I don't know if this is a known error whether it is caused by the new version of the tools.

I attach a pic of the warnings that Eclipse shows after trying to create a new Project

 

I don't know if you could help me with this

Thanks in advance for your help

Juan

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by squid267

    Feike Visser wrote...

    I have figured out a workaround...

    1. Don't deploy when creating a new project.

    2. Once the project is created, create a new server (switch to AEM-perspective), make sure to change the port (default is 8080)

    3. Select the modules you want to deploy

     

    Thanks Feike! For some reason I was not able to edit the server port on the new server screen but after I created it I changed it following this guide. Hope it helps anyone else encountering this issue.

    http://www.codejava.net/servers/tomcat/how-to-change-port-numbers-for-tomcat-in-eclipse

    24 replies

    Show previous replies
    S
    squid267
    March 24, 2016

    Same issue here. Was following steps from a Hand On Lab at Adobe Summit. Not sure why I'm getting this error.

      Lokesh_Shivalingaiah
      Lokesh_Shivalingaiah
      March 24, 2016

      @ronnyfm, have you added your core, apps modules to the server ?? Once you add, right click and do clean aswell which will resynchronize everything. 

        Lokesh_Shivalingaiah
        Lokesh_Shivalingaiah
        March 24, 2016

        @juan, which version of maven archetype are you using ?

          C
          Adobe Employee
          chaikelsAdobe Employee
          Adobe Employee
          March 25, 2016

          I'm having the same issue: "The server does not support version 2.4 of the J2EE Web module specification".

          Tried on both Luna and Mars. In case helpful: JDK / JRE info:

          java -version
          java version "1.8.0_65"
          Java(TM) SE Runtime Environment (build 1.8.0_65-b17)
          Java HotSpot(TM) 64-Bit Server VM (build 25.65-b01, mixed mode)

           

          javac -version
          javac 1.8.0_65
           
            Hemant_arora
            Hemant_arora
            March 26, 2016

            Hi Juan

            Make sure you have the correct JAVA_HOME path .

            >echo %path%

            I faced a somewhat similar issue and checked the java -version, the result was 

            java version "1.8.0_73"
            Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
            Java HotSpot(TM) Client VM (build 25.73-b02, mixed mode, sharing)

            But my JAVA_HOME was never set, the java auto updater keeps updating and the system was referring to jre build 1.8.0 and not JDK

            To fix it, I had to install JDK1.7 and set the path in environment variables.

            You can try the same...

              Feike_Visser1
              Adobe Employee
              Feike_Visser1Adobe Employee
              Adobe Employee
              March 27, 2016

              I have figured out a workaround...

              1. Don't deploy when creating a new project.

              2. Once the project is created, create a new server (switch to AEM-perspective), make sure to change the port (default is 8080)

              3. Select the modules you want to deploy

                S
                squid267Accepted solution
                March 27, 2016

                Feike Visser wrote...

                I have figured out a workaround...

                1. Don't deploy when creating a new project.

                2. Once the project is created, create a new server (switch to AEM-perspective), make sure to change the port (default is 8080)

                3. Select the modules you want to deploy

                 

                Thanks Feike! For some reason I was not able to edit the server port on the new server screen but after I created it I changed it following this guide. Hope it helps anyone else encountering this issue.

                http://www.codejava.net/servers/tomcat/how-to-change-port-numbers-for-tomcat-in-eclipse

                  Feike_Visser1
                  Adobe Employee
                  Feike_Visser1Adobe Employee
                  Adobe Employee
                  March 28, 2016

                  thanks for sharing!, I didn't encounter that error.

                    ronnyfm
                    ronnyfm
                    March 29, 2016

                    Thanks Feike, I didn't have the chance to post here, but I also found that workaround, but not only that, but the real cause is the archetype itself.

                    That is, as you stated the best is not to deploy to the server when creating the project, but creating the server after that.

                    The message about the Servlet 2.4 API specification is fixed by upgrading the definition in the pom.xml, the same applies to the Java JDK, event the most recent archetype (10) is using JDK 1.6, when in fact, the recommended JDK for AEM is 1.7 or greater, that also must to be updated.

                    After that, I create a new Server (updating the port numbers too) and add the modules, after all of this being done Eclipse effectively publish to the AEM instance.

                      Juan_Camacho_I_
                      Juan_Camacho_I_Author
                      March 30, 2016

                      Hi, thank you all for your help, I also get to make it work by creating a project, and using the Add and Remove to select the folders I want to sync. I still have the problem with error 500 when publishing in 1 of my mates computer and I don't know what to do to fix it.

                        Show more replies
                        Terms & ConditionsAccessibility statement

                        Loading footer...