Problem facing Maven build

nilanjan_mukher

15-10-2015

When trying to apply the the instructions mentioned in the Maven configuration details for CQ5 (http://docs.adobe.com/docs/en/cq/aem-how-tos/development/how-to-build-aem-projects-using-apache-mave...), I am facing issues when trying to create the project with the following command:

mvn archetype:generate -DarchetypeRepository=http://repo.adobe.com/nexus/content/groups/public/ -DarchetypeGroupId=com.day.jcr.vault -DarchetypeArtifactId=multimodule-content-package-archetype -DarchetypeVersion=1.0.2 -DgroupId=my-group-id -DartifactId=myproject -Dversion=1.0-SNAPSHOT -Dpackage=com.mycompany.myproject -DappsFolderName=myproject -DartifactName="My Project" -DcqVersion="5.6.1" -DpackageGroup="My Company"

Following is the error:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.2:generate (default-cli) on project standalone-pom: The desired archetype does not exist (com.day.jcr.vault:multimodule-content-package-archetype:1.0.2) -> [Help 1]

 

Also, tried to configure settings.xml as mentioned in the following link:

http://helpx.adobe.com/experience-manager/kb/SetUpTheAdobeMavenRepository.html

Still getting same error. It is showing some additonal warnings, from which, it seems there is some connectivity issue with the repository.

[WARNING] Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to adobe-public-releases (http://repo.adobe.com/nexus/content/groups/public): Connect to repo.adobe.com:80 [repo.adobe.com/192.147.117.14] failed: Operation timed out

 

Please suggest.

Accepted Solutions (1)

Accepted Solutions (1)

Answers (2)

Answers (2)

Ove_Lindström

15-10-2015

It is strongly recommended that you use an internal repository, like Sonatype Nexus, and proxy the third party repositories. Then you avoid any proxy problems and you get a copy of the repo inside of your local network. Typically if you have a low bandwidth WAN and say 10 developers that all have to download about 600 Mb of artifacts from different repositories, the network will go nuts. Having a local copy makes it also possible to download it faster and if a remote repo is down, you can still download it from your company local instance.

/O