Skip to main content
Juan_Camacho_I_
Level 2
Mar 15, 2016 12:58 PM UTC
Solved

Eclipse Development tools error

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.
squid267Accepted solution
Level 3
Mar 27, 2016 11:19 PM UTC

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

Feike_Visser1
Adobe Employee
Adobe Employee
Mar 30, 2016 8:44 PM UTC

great!

Translate
ronnyfm
Level 4
Apr 8, 2016 2:24 PM UTC

I submitted a pull request to fix the archetype versions that create conflicts when using the Eclipse plugin: https://github.com/Adobe-Marketing-Cloud/aem-project-archetype/pull/60

You can see there what I modified, so you can do it in your projects too.

Translate
Adobe Employee
Apr 14, 2016 7:59 AM UTC

Thanks for the submission! For the sake of being complete, this is an error in how Maven projects are auto-configured by version 1.1 of the AEM Developer Tools, tracked at https://github.com/Adobe-Marketing-Cloud/aem-eclipse-developer-tools/issues/67 and already fixed.

The next release version will no longer require this workaround.

Translate
ShakilAhmed
Level 2
Jul 30, 2016 3:58 PM UTC

it works fine only if you dont forget to clean after making changes ;)

Translate