content-package-maven-plugin has gone missing from adobe repo?

On the fresh computer - try using the settings.xml example found in this article: 

https://helpx.adobe.com/experience-manager/using/creating-custom-aem-workflow-steps.html

Hi

As mentioned by Scott and Lokesh, try using settings.xml in provided helpx article.

Link:- https://helpx.adobe.com/experience-manager/using/creating-custom-aem-workflow-steps.html

// The Maven configuration file named settings.xml from [install location]\apache-maven-3.0.4\conf\ to your user profile. For example, C:\Users\scottm\.m2\.

You have to configure your settings.xml file to use Adobe’s public repository. For information, see Adobe Public Maven Repository at http://repo.adobe.com/.

Use the XML provided in the article.

I hope this would work for you.

Thanks and Regards

Kautuk Sahni

Thanks all, the settings.xml did the trick.  I really appreciate the responses!

This is going to be a huge mess to get a settings.xml on to all our build servers, developer laptops so forth on computers all over the world, since it doesn't go into source code control in a repeatably-installable place, and makes the builds unportable, but I'll see if I can work all that out.

Thanks!

So, I already had defined the Adobe repo profile in my pom.xml, just like in the Archetype.

However, despite being set to be active by default in the POM, it wasn't kicking in every time the build ran for some reason.

If I run:

mvn help:active-profiles

it kicks in every time, but on

clean install

it does not.

Which is weird, and bug-like from a maven perspective.  It also doesn't kick in reliably when running from Eclipse or IntelliJ.

That said, if I explicitly invoke 'adobe-public' as a profile on the build, it works every time.

mvn clean install -P autoInstallPackage adobe-public

This makes it so that we just need to build and POM, and not a separate settings.xml file.

Hope that helps folks,

Tim

I too faced similar issue. My POMs look good. Repo info defined in settings.xml. But still got issue.

Tim you mentioned - "explicitly invoke 'adobe-public' as a profile on the build"

This did the trick for me.

Almost June 2019 and still having the same issue here, my settings.xml is pointing to the nexus repo, the same on my pom.xml but I need to invoke 'adobe-public' as a profile in the command. Why is that? (mvn -PautoInstallPackage -Padobe-public clean install)