Service not registering for Maven Archetype 12

13 seems to work better

Hi Rajnish,

  I did try, even after getting an error , it actually created the project.

Yeah Jorg. I am not sure exactly why such an issue appeared. I am working with archetype 13 now and I am able to create projects successfully. 12 also shud work fine I believe.

What do you mean with "none of our services were getting registered"? How did you check that? Can you share a minimal projcect setup including POM files and source code? I recently started a test with version 12 and it worked well.

Jörg

smacdonald2008 Since you got in touch with Adobe folks in Aug 2017, is there any fresh update on the guidance about with Archetype to use for 6.3 and 6.4.

Now Archetypes 12, and 13 are available: GitHub - Adobe-Marketing-Cloud/aem-project-archetype: Maven template to create a new Adobe Experience Manager (AEM) proj…

However, Archetype 11 is the only one that works for me.

For Archetypes 12, and 13, I am getting:

Unable to create project from archetype [com.adobe.granite.archetypes:aem-project-archetype:12 -> https://repo.adobe.com/nexus/content/groups/public]

The link that I shared suggests to use archetype 12 for 6.3, and  archetype 13 for 6.3 SP2 and 6.4

Veena_07​ seems like you had some partial success with 12. Did you try any time after that. Anyone else had better luck than mine using archetype 12 or 13?

Update 5/8/18:

I could get the Archetype 13 working by following command line invocation of mvn as documented in: Getting Started with AEM Sites Part 1 - Project Setup

mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate -DarchetypeGroupId=com.adobe.granite.archetypes -DarchetypeArtifactId=aem-project-archetype -DarchetypeVersion=13 -DarchetypeCatalog=https://repo.adobe.com/nexus/content/groups/public/

There was an issue with SSL certs for https://repo.adobe.com but that was resolved by saving the cert from the site and adding it to the maven's java key store.

Subsequently, I was able to create the archetype 13 based project within Eclipse as well. The Configure Archetype Properties step requires completing all Parameters. Parameters like confFolderName, cssId, and componentGroupName are left by the wizard. The blank values can only be seen when you hit Next to Select or Create Server tab and then return back to Configure Archetype Properties step.

It appears that either I am not using the right AEM Development Tools or the AEM Dev Tools is not yet compatible with archetype 13 parameters. I git the latest and greatest AEM Dev Tools from AEM Developer Tools, so unsure what is wrong. Anyway, I am glad things have progressed.

Just heard back from internal Adobe ppl - they siad:

I see only up to 11… so that’s the best one to use.

Github has a SNAPSHOT for 12 but that’s a snapshot and isn’t necessary intended for use (rather for development of the archetype itself).

Sounds like that - why not use 11 that works?