search

chonton / exists-maven-plugin

Check if artifact exists in remote maven repository
Apache License 2.0
46 stars 16 forks source link

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

Open csaoud opened 11 months ago

csaoud commented 11 months ago

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 commented 6 months ago

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

csaoud commented 5 months ago

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.