adobe / aem-spa-project-archetype

Maven Archetype for creating new AEM SPA projects
Apache License 2.0
61 stars 32 forks source link

Archetype should be published and publicly available #59

Closed godanny86 closed 4 years ago

godanny86 commented 5 years ago

When attempting to generate a new SPA project the archetype doesn't seem to be found in any public catalogs. I assume it should be uploaded to nexus.adobe.com, i.e https://repo.adobe.com/nexus/content/groups/public/com/adobe/granite/archetypes/aem-project-archetype/

Command:

mvn archetype:generate 
-DarchetypeGroupId=com.adobe.cq.spa.archetypes     
-DarchetypeArtifactId=aem-spa-project-archetype       
-DarchetypeVersion=1.0.4

Error:

[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] >>> maven-archetype-plugin:3.0.1:generate (default-cli) > generate-sources @ standalone-pom >>>
[INFO] 
[INFO] <<< maven-archetype-plugin:3.0.1:generate (default-cli) < generate-sources @ standalone-pom <<<
[INFO] 
[INFO] --- maven-archetype-plugin:3.0.1:generate (default-cli) @ standalone-pom ---
[INFO] Generating project in Interactive mode
[INFO] Archetype repository not defined. Using the one from [com.adobe.cq.spa.archetypes:aem-spa-project-archetype:1.0.3-SNAPSHOT] found in catalog local
[WARNING] The POM for com.adobe.cq.spa.archetypes:aem-spa-project-archetype:jar:1.0.4 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.259 s
[INFO] Finished at: 2019-02-27T18:02:03-08:00
[INFO] Final Memory: 18M/316M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate (default-cli) on project standalone-pom: The desired archetype does not exist (com.adobe.cq.spa.archetypes:aem-spa-project-archetype:1.0.4) -> [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.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
DiegoVanBelle commented 5 years ago

I'm getting the same issue. Any fix on the way?

pfauchere commented 5 years ago

Could it relate to [0]? Is someone curious enough to investigate?

[0] https://issues.apache.org/jira/browse/ARCHETYPE-529

godanny86 commented 5 years ago

hi @pfauchere, irrespective of interactive mode vs batch mode, I don't think the archetype has ever been uploaded to the public nexus repo:

Downloading: https://repo.adobe.com/nexus/content/groups/public/com/adobe/cq/spa/archetypes/aem-spa-project-archetype/1.0.4/aem-spa-project-archetype-1.0.4.pom
[WARNING] The POM for com.adobe.cq.spa.archetypes:aem-spa-project-archetype:jar:1.0.4 is missing, no dependency information available

Checkout: https://repo.adobe.com/nexus/content/groups/public/com/adobe/cq/ there is no spa folder.

The standard aem project archetype has been uploaded and deployed to nexus: https://repo.adobe.com/nexus/content/groups/public/com/adobe/granite/archetypes/aem-project-archetype/17/

pfauchere commented 5 years ago

I confirm that we haven't uploaded yet the artifact of the archetype to the nexus. Thanks for the project-archetype reference. We will align the current project accordingly ASAP

pfauchere commented 5 years ago

issue tracked internally by CQ-4266179

anandkilli commented 5 years ago

Hello @pfauchere , Is there an ETA on when the Archetype will be available? Is there a way we can track it or get notified when it's ready?

Jdruwe commented 5 years ago

Seems to be still an issue.

pfauchere commented 5 years ago

There is some latency as we are moving away from our nexus and are considering public repositories. Thank you for refreshing the conversation