Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

AEM Eclipse Plugin Issues - AEM project is not created in Eclipse

Avatar

Level 1

Hi Everyone,

I'm new to AEM, i have configured AEM plugin in eclipse, plugin was installed successfully. im facing issue while creating AEM project after selecting the archetype. i couldn't see the next screen to enter all the project info like groupid, artifactId, appId etc... I found below exception in eclipse errorlog. 
Could you please help me to resolve this. Thanks in advance.
Note: I'm using AEM 6.5 
Java 11 is installed in my machine

!ENTRY org.eclipse.ui 4 0 2020-10-10 15:17:11.140
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.RuntimeException: Could not process archetype: null
	at com.adobe.granite.ide.eclipse.ui.wizards.np.AdvancedSettingsComponent.initialize(AdvancedSettingsComponent.java:276)
	at com.adobe.granite.ide.eclipse.ui.wizards.np.SimplerParametersWizardPage.setVisible(SimplerParametersWizardPage.java:160)
	at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1193)
	at org.eclipse.jface.wizard.WizardDialog.lambda$3(WizardDialog.java:1163)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:71)
	at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1163)
	at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:858)
	at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:407)
	at org.eclipse.jface.dialogs.Dialog.lambda$0(Dialog.java:619)
	at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:81)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4118)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3931)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3534)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
	at org.eclipse.jface.window.Window.open(Window.java:794)
	at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
	at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
	at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291)
	at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:93)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:318)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:252)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:161)
	at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
	at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
	at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
	at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:204)
	at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:393)
	at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:151)
	at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:161)
	at org.eclipse.ui.actions.NewWizardDropDownAction.run(NewWizardDropDownAction.java:175)
	at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
	at org.eclipse.jface.action.ActionContributionItem.lambda$5(ActionContributionItem.java:436)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4118)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3931)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3534)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1170)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1059)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:667)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:597)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:656)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:592)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1498)
Caused by: java.lang.NullPointerException
	at com.adobe.granite.ide.eclipse.ui.wizards.np.AdvancedSettingsComponent.initialize(AdvancedSettingsComponent.java:270)
	... 66 more

 

1 Accepted Solution

Avatar

Correct answer by
Level 1

Finally i was able to create project via command line following the steps provided in below link.

https://jimfrenette.com/2019/10/aem-maven-project/

Thank You All for your time spending on this issue.

View solution in original post

8 Replies

Avatar

Community Advisor

Hi @vrokkham ,

 

I think there is a problem with the plugin. Can you please try building the project from console and add them to the server in eclipse, hope it does work.

Link: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/can-not-create-new-aem-pro...

 

Regards,

Santosh

Avatar

Level 1

Hi @santhosh_kumark , Thanks for the above response. but i'm facing issue with creating a project, with out project i couldn't build project from console. Hope you got my concern.

Avatar

Level 5

Hi @vrokkham 

Did you restart the eclipse once the plugin is installed? If not, please restart and try creating the project. 

For reference - http://www.aemcq5tutorials.com/tutorials/adobe-aem-cq5-tutorials/create-aem-multi-module-project/#cr...

 

Hope this helps... Happy learning  

Avatar

Level 1

Hi @VeenaK , I did restart the eclipse after the plugin installation. also through  command prompt also not able to create AEM archetype project.

Below is the error 

C:\Users\180209\Desktop\testEclipse>mvn archetype:generate -B -Padobe-public -DarchetypeGroupId=com.adobe.granite.archetypes -DarchetypeArtifactId=aem-project-archetype -DarchetypeVersion=17 -DgroupId=com.adobe -Dversion=0.0.1-SNAPSHOT -DappsFolderName=myproject -DartifactId=aem-dev-myproject -Dpackage=com.adobe.aem.dev.myproject -DartifactName=myproject -DcomponentGroupName=myproject -DconfFolderName=myproject -DcontentFolderName=myproject -DcssId=myproject -DpackageGroup=myproject -DsiteName=myproject
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-archetype-plugin:3.2.0:generate (default-cli) @ standalone-pom >>>
[INFO]
[INFO] <<< maven-archetype-plugin:3.2.0:generate (default-cli) @ standalone-pom <<<
[INFO]
[INFO] --- maven-archetype-plugin:3.2.0:generate (default-cli) @ standalone-pom ---
[INFO] Generating project in Batch mode
[WARNING] Archetype not found in any catalog. Falling back to central repository.
[WARNING] Add a repository with id 'archetype' in your settings.xml if archetype's repository is elsewhere.
Downloading: https://repo1.maven.org/maven2/com/adobe/granite/archetypes/aem-project-archetype/17/aem-project-arc...
[WARNING] The POM for com.adobe.granite.archetypes:aem-project-archetype:jar:17 is missing, no dependency information available
Downloading: https://repo1.maven.org/maven2/com/adobe/granite/archetypes/aem-project-archetype/17/aem-project-arc...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17:12.346s
[INFO] Finished at: Mon Oct 12 13:33:58 IST 2020
[INFO] Final Memory: 14M/293M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.2.0:generate (default-cli) on project standalone-pom: The desired archetype does not exist (com.adobe.granite.archetypes:aem-project-archetype:17) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.

Avatar

Community Advisor

Hi @vrokkham,

In the cmd prompt, use "mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate" instead of "mvn archetype:generate" specifying the explicit archetype plugin version. 

Archetype version 17 project uses plugin version 2.4.

 

Avatar

Correct answer by
Level 1

Finally i was able to create project via command line following the steps provided in below link.

https://jimfrenette.com/2019/10/aem-maven-project/

Thank You All for your time spending on this issue.

Avatar

Level 1

Hi, Vrokkham, i get the same problem with you. So far, i still can't solve it after trying all the possible solution from network.

If we still need to use the CMD to create the project, then i am not sure what's the usage of the AEM tool.

Is it really a bug of this tool or did you get any finding on this?