Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Looking for the wrong artifact when using <packaging>content-package</packaging> #44

Open
csaoud opened this issue Aug 17, 2023 · 2 comments

Comments

@csaoud
Copy link

csaoud commented Aug 17, 2023

When using content-package in my pom, the artifact cannot be found as content-package is amended to the name. See error message below

[INFO] --- exists-maven-plugin:0.12.0:remote (default) @ project-aem-all.all ---
181[INFO] Checking for artifact at https://nexus-url/repository/maven-releases/au/com/project/aem/project-aem-all/project-aem-all.all/9.7.1/project-aem-all.all-9.7.1.content-package
182[INFO] au.com.project.aem.project-aem-all:project-aem-all.all:9.7.1 does not exist
 

@chonton
Copy link
Owner

chonton commented Jan 14, 2024

What is the expected remote url? Which plugin are you using for the content-package lifecycle?

@csaoud
Copy link
Author

csaoud commented Jan 21, 2024

Hi
The content-package lifecycle is used as part of a getting the package ready to be deployed for AEM,
I resolved the issue using the project and artifact parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants