I am getting this error which is described in one of the AEM tutorialsGetting Started with AEM Sites Part 2 - Creating a Base Page and Template Unfortunately, the suggested fix does not work:First issue is, Eclipse does not allow removing Dynamic Web Module through the UI.Second issue is, if you forcibly remove it by editing /ui.apps/.settings/org.eclipse.wst.common.project.facet.core.xml, the actual problem is still not solved.Any other ideas?

The problem appears to be gone after the following updates are applied. The archetype has a lot of outdated references:maven-sling-plugin 2.2.0 -> 2.3.4htl-maven-plugin 1.0.6 -> 1.1.2maven-bundle-plugin 3.3.0 -> 3.5.0Do not upgrade: content-package-maven-plugin - stay on 0.5.1, because 1.0.2 causes other problemsEclipse Sling IDE Tools 1.1.0 -> 1.2.0Eclipse Neon.3 vs Oxygen doesn't seem to matter

A

alexr21

Level 3

Solved

Unable to validate node types since project ... is not associated with a server or the server is not started.

16 replies
4296 views
Translate All

I am getting this error which is described in one of the AEM tutorials

Getting Started with AEM Sites Part 2 - Creating a Base Page and Template

Unfortunately, the suggested fix does not work:

First issue is, Eclipse does not allow removing Dynamic Web Module through the UI.

Second issue is, if you forcibly remove it by editing /ui.apps/.settings/org.eclipse.wst.common.project.facet.core.xml, the actual problem is still not solved.

Any other ideas?

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

A

alexr21Accepted solution

Level 3

The problem appears to be gone after the following updates are applied. The archetype has a lot of outdated references:

maven-sling-plugin 2.2.0 -> 2.3.4
htl-maven-plugin 1.0.6 -> 1.1.2
maven-bundle-plugin 3.3.0 -> 3.5.0
Do not upgrade: content-package-maven-plugin - stay on 0.5.1, because 1.0.2 causes other problems
Eclipse Sling IDE Tools 1.1.0 -> 1.2.0
Eclipse Neon.3 vs Oxygen doesn't seem to matter

Show previous replies

smacdonald2008

Level 10

Setup the project - as described in the Lazybone article.

Then switch to AEM Perspective. THen you can click on a location in the JCR and add a new node:

I created a new node of type nt:folder

When i run Maven from Eclipse - the node is imported into AEM,

Try to re-install the AEM DEV tool in Neon eclipse. It works.

Translate

A

alexr21AuthorAccepted solution

Level 3

The problem appears to be gone after the following updates are applied. The archetype has a lot of outdated references:

maven-sling-plugin 2.2.0 -> 2.3.4
htl-maven-plugin 1.0.6 -> 1.1.2
maven-bundle-plugin 3.3.0 -> 3.5.0
Do not upgrade: content-package-maven-plugin - stay on 0.5.1, because 1.0.2 causes other problems
Eclipse Sling IDE Tools 1.1.0 -> 1.2.0
Eclipse Neon.3 vs Oxygen doesn't seem to matter

Translate

smacdonald2008

Level 10

Thanks for posting this - i have asked the author of this doc to look at making possible updates based on your post.

Translate

Daniel_Gordon

Adobe Employee

alexr2 to clarify, did updating those dependencies in WKND pom.xml fix the issue? Or were you experiencing this issue in your own project and updating those dependencies fixed it? You mention "the archetype has a lot outdated references" is that when creating a project using Lazybones or the using the Maven aem-project-archetype? Do you mind posting the relevant pom.xmls? Thanks!

Translate

A

alexr21Author

Level 3

hi dgordon86, we were experiencing this issue in our own project and updating the dependencies fixed it. The project was created by a colleague using the Maven aem-project-archetype version 12.

Translate

Daniel_Gordon

Adobe Employee

Thanks alexr2!

Translate

Sign up

Login with SSO

Login to the community

Login with SSO