https://repo.adobe.com/nexus/content/groups/public/archetype-catalog.xml Not available. | Adobe Higher Education
Skip to main content
Level 3
December 3, 2021
해결됨

https://repo.adobe.com/nexus/content/groups/public/archetype-catalog.xml Not available.

  • December 3, 2021
  • 3 답변들
  • 2416 조회

I am trying to get the new archetype for my aem 6.5.10 project and see if it works fine. But looks like it is down. Can some help with the link?

 

Even this is not available https://repo.adobe.com/nexus/content/groups/public/ . 

 

이 주제는 답변이 닫혔습니다.
최고의 답변: joerghoh

I cannot reproduce it. I just bootstrapped 2 versions of the aem archetype 32 with these parameters:

 

mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=32 -D appTitle="My Site" -D appId="mysite" -D groupId="com.mysite" -D aemVersion=cloud

 

mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=32 -D appTitle="My Site" -D appId="mysite" -D groupId="com.mysite" -D aemVersion=6.5.10

 

After that I ran both with "mvn clean install" and it worked fine, no complaints about missing artifacts. Did you use the latest archetype version when bootstrapping your project?

 

3 답변

Level 2
December 3, 2021

I am facing similar issue with the repo. Nothing is available.

joerghoh
Adobe Employee
joerghohAdobe Employee답변
Adobe Employee
December 4, 2021

I cannot reproduce it. I just bootstrapped 2 versions of the aem archetype 32 with these parameters:

 

mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=32 -D appTitle="My Site" -D appId="mysite" -D groupId="com.mysite" -D aemVersion=cloud

 

mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=32 -D appTitle="My Site" -D appId="mysite" -D groupId="com.mysite" -D aemVersion=6.5.10

 

After that I ran both with "mvn clean install" and it worked fine, no complaints about missing artifacts. Did you use the latest archetype version when bootstrapping your project?

 

RandyKr123
March 7, 2022

Hello Jörg. I am a bit of a novice but I tried your updated archetype & aem version but am receiving these errors when attempting the build below:

BUILD FAILURE message:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate (default-cli) on project standalone-pom: startup failed:

[ERROR] General error during conversion: Conflicting module versions. Module [groovy-all is loaded in version 2.4.16 and you are trying to load version 2.4.8

[ERROR] groovy.lang.GroovyRuntimeException: Conflicting module versions. Module [groovy-all is loaded in version 2.4.16 and you are trying to load version 2.4.8
[ERROR] at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl$DefaultModuleListener.onModule(MetaClassRegistryImpl.java:529)
[ERROR] at org.codehaus.groovy.runtime.m12n.ExtensionModuleScanner.scanExtensionModuleFromProperties(ExtensionModuleScanner.java:81)
[ERROR] at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.registerExtensionModuleFromProperties(MetaClassRegistryImpl.java:174)
[ERROR] at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl$registerExtensionModuleFromProperties.call(Unknown Source)


Commands:
mvn archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=32 -D groupId=com.adobe -D version=0.0.1-SNAPSHOT -D appsFolderName=learning -D artifactId=learning -D artifactName="Learning project" -D language_country=en_us -D optionAemVersion=6.5.10 -D optionDispatcherConfig=none -D optionIncludeErrorHandler=n -D optionIncludeExamples=y -D optionIncludeFrontendModule=n -D siteName="Learning Site"

joerghoh
Adobe Employee
Adobe Employee
March 11, 2022

I can reproduce this problem as well with the settings your provided. But when I switch to archetype version 35 (which is the most current one), it works fine.

 

Nikhil-Kumar
Community Advisor
Community Advisor
December 6, 2021

@gvaem - Works fine for me. Try checking your settings.xml file. And specify the AEM version while creating your project.