Eclipse AEM Plugin not working | Community
Skip to main content
L
LKAemNewbie
New Participant
December 7, 2023
Solved

Eclipse AEM Plugin not working

  • December 7, 2023
  • 4 replies
  • 1788 views

Hi,

 

I am a newbie to AEM and installed AEM dev tool for eclipse whose version is below.

 

Eclipse IDE for Java Developers

Version: 2023-06 (4.28.0)
Build id: 20230608-1333

Added 2022-09 as well.

 

Post installation, when trying to create new project in eclipse, after selecting AEM Sample Multi module Project it isn't going to next screen where we would enter archetype details ect. Instead it is stuck on new project screen and below are the error details from error log. Please suggest how to resolve this.

 

 

An error has occurred. See error log for more details.
org/eclipse/m2e/core/internal/index/IndexListener
Problems occurred when invoking code from plug-in: "org.eclipse.jface".
 
java.lang.NoClassDefFoundError: org/eclipse/m2e/core/internal/index/IndexListener
Caused by: java.lang.ClassNotFoundException: org.eclipse.m2e.core.internal.index.IndexListener cannot be found by org.apache.sling.ide.eclipse-m2e-ui_1.2.2
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 EstebanBustamante

Make sure your Eclipse can read MAVEN, meaning that your MAVEN is installed globally and you have an environment variable. It looks like if you could generate the project via CMD then the IDE is the problem, please check this thread which explains how to use eclipse with AEM projects:
https://experienceleague.adobe.com/docs/experience-manager-65/developing/devtools/howto-projects-eclipse.html?lang=en#:~:text=In%20the%20Import%20Dialog%2C%20choose,%2Flibs%2Ffoundation%2Fglobal. 

Hope this helps

4 replies

D
DatHuynh
New Participant
February 4, 2024

Hi,
I am still experiencing the exact same original issue of this post. May I ask if there is thorough solution?

Notes: using maven cmd can do the work but i believe the reported error comes with other errors / inconveniences in the IDE as well, for example: there is no "import from server" option when you want to import content from Author back to IDE.

TIA

    kautuk_sahni
    kautuk_sahni
    Employee
    December 11, 2023

    @lkaemnewbie Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

    Kautuk Sahni
    EstebanBustamante
    EstebanBustamanteAccepted solution
    New Participant
    December 7, 2023

    Make sure your Eclipse can read MAVEN, meaning that your MAVEN is installed globally and you have an environment variable. It looks like if you could generate the project via CMD then the IDE is the problem, please check this thread which explains how to use eclipse with AEM projects:
    https://experienceleague.adobe.com/docs/experience-manager-65/developing/devtools/howto-projects-eclipse.html?lang=en#:~:text=In%20the%20Import%20Dialog%2C%20choose,%2Flibs%2Ffoundation%2Fglobal. 

    Hope this helps

    Esteban Bustamante
      arunpatidar
      arunpatidar
      New Participant
      December 7, 2023

      Hi @lkaemnewbie 
      Please use CMD to generate AEM project with correct archtype

      https://github.com/adobe/aem-project-archetype 

      Arun Patidar
        L
        LKAemNewbieAuthor
        New Participant
        December 7, 2023

        Thank you for responding. I tried that way.. build was successful in command prompt and while importing or updating maven project in eclipse it gave below error. 

         

        An internal error occurred during: "Updating Maven Project".
         
        java.lang.NoSuchMethodError: 'org.eclipse.core.resources.IProject org.eclipse.m2e.core.project.configurator.ProjectConfigurationRequest.getProject()'
        at org.apache.sling.ide.eclipse.m2e.internal.ContentPackageProjectConfigurator.configure(ContentPackageProjectConfigurator.java:71)
        at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:123)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$6(ProjectConfigurationManager.java:503)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:394)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:275)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:497)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$4(ProjectConfigurationManager.java:425)
        at java.base/java.util.Collection.removeIf(Collection.java:576)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:413)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$3(ProjectConfigurationManager.java:339)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:394)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:275)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:214)
        at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1097)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:338)
        at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:80)
        at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:43)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
          Terms & ConditionsAccessibility statement

          Loading footer...