Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

WKND Maven Project Import to Eclipse fails with "The set of natures is not valid. Nature does not exist" Error

ISCBorisB
Level 1
Level 1

Environment: 
Linux Mint 18.2 'Sofia', KDE 64. Java 11.0.8, AEM 6.5, Local instance. Eclipse 4.15.0 (2020-03)

Problem:

While importing WKND Maven Project to Eclipse I am getting an error "The set of natures is not valid. Nature does not exist: org.eclipse.wst.jsdt.core.jsNature."

Any proposals to what I can try to fix the issue will be appreciated. 

 

The following is the top of Eclipse stack trace fragment from the "Problems" Tab:
Description Resource Path Location Type
Could not add all necessary WTP natures: The set of natures is not valid. pom.xml /aem-guides-wknd.all line 1 Project Configurator Problem

java.io.FileNotFoundException: /home/mberezet/component-basics/aem-guides-wknd/repository-structure/target/classes (Is a directory) (org.apache.jackrabbit:filevault-package-maven-plugin:1.0.3:generate-metadata:default-generate-metadata:process-classes)

org.apache.maven.plugin.MojoExecutionException: java.io.FileNotFoundException: /home/mberezet/component-basics/aem-guides-wknd/repository-structure/target/classes (Is a directory)
at org.apache.jackrabbit.filevault.maven.packaging.GenerateMetadataMojo.execute(GenerateMetadataMojo.java:458)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:332)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.lambda$8(MavenImpl.java:1379)
...

Forum's Search showed practically identical issue reported by ritikr94196144 on Nov 2018. Unfortunately, there are no resonses to this query. There are also few recommendations to somewhat similar issues to upgarde filevault-package-maven-pluginto version 1.1.4. I've tried that just in case but with these POM changes I cannot even build the Prject.

 

 

1 Accepted Solution
Nikhil-Kumar
Correct answer by
Community Advisor
Community Advisor

@ISCBorisB - It seems to be some Eclipse issue not AEM Project issue, can you try using Java 8 or try upgrading the eclipse version.

View solution in original post

2 Replies
Nikhil-Kumar
Correct answer by
Community Advisor
Community Advisor

@ISCBorisB - It seems to be some Eclipse issue not AEM Project issue, can you try using Java 8 or try upgrading the eclipse version.

View solution in original post

ISCBorisB
Level 1
Level 1
Thanks Nikhi. Yes, I do realize it's an Eclipse issue. AEM 6.5 requires Java 11 so I can't downgrade JDK. As to Eclipse, I've used that last stable version, 4.15 from March 2020. The latest Eclipse is 4.17, it's SWT requires GTK 3.20 and my OS has 3.18. It looks like I am stuck here, unless I start from scratch, upgrade Linux and all that...