Managing third-party dependencies in AEM by Aanchal Sikka
Overview
When working on AEM implementations, developers often need to manage dependencies that are not available in public Maven repositories. This article explores two common scenarios:
Artifactcannot be hostedin Public/Private RepositoriesIn this scenario, you encounter a situation where the required artifact is not available in any public Maven repository, and hosting it in your organization’s repository is not an option.
Artifact hosted in Private RepositoriesHere, we assume you have the flexibility to host the required artifact in your organization’s repository but need to secure it with a password/token
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.