New Participant

Solved

Eclipse Development tools error

Forum|Forum|10 years ago
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

ShakilAhmed

New Participant

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

R

RobertMu10

Employee

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.

ronnyfm

New Participant

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.

Feike_Visser1

Employee

great!

Juan_Camacho_I_Author

New Participant

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.

ronnyfm

New Participant

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.

Feike_Visser1

Employee

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

S

squid267Accepted solution

New Participant

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