Adobe Experience Manager Repositories Update 6.3 & 6.4 | Community
Skip to main content
rockie-rocafort
rockie-rocafort
Level 2
January 31, 2019
Solved

Adobe Experience Manager Repositories Update 6.3 & 6.4

  • January 31, 2019
  • 1 reply
  • 1343 views

I would just like to ask a question regarding repositories and plugin repositories in AEM? I have a project that works perfectly in both AEM 6.3 and 6.4. Although I've updated the pom.xml and added the below snippet for the 6.4 instance. As I've checked, there were no differences with the functionalities, even if I've added the snippet or not. I'm still new to AEM and was a bit confused about the usage of this repository section. Is there anything particularly that I have to check to verify this? I would just like to check the impact of adding this.

<repositories>
        <repository>
            <id>adobe-public-releases</id>
            <name>Adobe Public Repository</name>
            <url>https://repo.adobe.com/nexus/content/groups/public/</url>
            <layout>default</layout>
        </repository>
        <repository>
            <id>apache-intermediate-release</id>
            <name>Apache Intermediate Release Repository</name>
            <url>http://wcm.io/maven/repositories/apache-intermediate-release/</url>
            <layout>default</layout>
        </repository>
    </repositories>
    <pluginRepositories>
        <pluginRepository>
            <id>adobe-public-releases</id>
            <name>Adobe Public Repository</name>
            <url>https://repo.adobe.com/nexus/content/groups/public/</url>
            <layout>default</layout>
        </pluginRepository>
        <pluginRepository>
            <id>apache-intermediate-release</id>
            <name>Apache Intermediate Release Repository</name>
            <url>http://wcm.io/maven/repositories/apache-intermediate-release/</url>
            <layout>default</layout>
        </pluginRepository>
    </pluginRepositories>

Thank you for any insights regarding this.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Gaurav-Behl

The usage of this section is to download the dependencies mentioned under <dependencyManagement> in pom.xml along with transitive dependencies. The downloaded files get saved into .m2 folder on your local machine (which is configurable).

Once you have all the dependencies downloaded and you don't make any changes to the code, it would not download the files again n again each time.

If you want to check the impact, go ahead and take a backup of local .m2 folder or simply delete it and then build the project using mvn cmd. If you have mentioned the repositories from where to download, the build would succeed else fail.

Ideally, this section should be present, you may check that fallback is in settings.xml under .m2 folder

1 reply

Gaurav-Behl
Gaurav-BehlAccepted solution
Level 10
January 31, 2019

The usage of this section is to download the dependencies mentioned under <dependencyManagement> in pom.xml along with transitive dependencies. The downloaded files get saved into .m2 folder on your local machine (which is configurable).

Once you have all the dependencies downloaded and you don't make any changes to the code, it would not download the files again n again each time.

If you want to check the impact, go ahead and take a backup of local .m2 folder or simply delete it and then build the project using mvn cmd. If you have mentioned the repositories from where to download, the build would succeed else fail.

Ideally, this section should be present, you may check that fallback is in settings.xml under .m2 folder

Terms & ConditionsAccessibility statement

Loading footer...