Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Eclipse Development tools error

Avatar

Level 2

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

1 Accepted Solution

Avatar

Correct answer by
Level 4

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

View solution in original post

24 Replies

Avatar

Level 4

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.

Avatar

Level 1

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.

Avatar

Level 2

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