adobe / adobe/aem-project-archetype

AEM Developer Tools Could not process archetype: null

Open
#1,201 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
596
Forks
431
Avg merge
10d 6h
Merged PRs (30d)
1

Description

### Expected Behaviour
I have Eclipse Luna Release 4.4 with the AEM Developer Tools plugin. When I select File – New – Project and try to create an AEM Sample Multi-Module Project, I expect the Wizard to work.

### Actual Behaviour
When I select File – New – Project and try to create an AEM Sample Multi-Module Project, the following error occurs.
java.lang.RuntimeException: Could not process archetype: null

Caused by: java.lang.NullPointerException at com.adobe.granite.ide.eclipse.ui.wizards.np.AdvancedSettingsComponent.initialize(AdvancedSettingsComponent.java:270)

### Reproduce Scenario (including but not limited to)
Install Eclipse Luna Release 4.4 and the AEM Developer Tools plugin
#### Steps to Reproduce
1. Select File – New – Project.
2. Expand the AEM category.
3. Select the AEM Sample Multi-Module Project and click Next.
4. Click the Archetype drop-down and select com.adobe.granite.archetypes : aem-project-archetype:15.
5. Click Next.

#### Platform and Version
Windows with Eclipse Luna Release 4.4 and the AEM Developer Tools plugin
#### Sample Code that illustrates the problem
N/A
#### Logs taken while reproducing problem
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:1289)
at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1268)
at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1257)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1254)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:942)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:434)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
at org.eclipse.jface.window.Window.open(Window.java:808)
at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:117)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
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:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
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:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
Caused by: java.lang.NullPointerException
at com.adobe.granite.ide.eclipse.ui.wizards.np.AdvancedSettingsComponent.initialize(AdvancedSettingsComponent.java:270)
... 48 more

Contributor guide

Open the contributing guide

Research direction

Reproduce the failure in Eclipse Luna 4.4 using the AEM Sample Multi-Module Project and archetype com.adobe.granite.archetypes:aem-project-archetype:15. Start at AdvancedSettingsComponent.initialize, especially lines 270-276, using the reported stack trace. Done means the wizard proceeds past the archetype selection without the RuntimeException or NullPointerException.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.