Maven error building with profile `autoInstallPackage`
See original GitHub issueI’m getting a maven dependency error for plugin com.day.jcr.vault:content-package-maven-plugin:1.0.2
when trying to build after creating a new project. I’m running 6.4 locally.
I try building with mvn clean install -PautoInstallPackage
then get an error.
Full error:
[INFO] Scanning for projects...
[WARNING] The POM for com.day.jcr.vault:content-package-maven-plugin:jar:1.0.2 is missing, no dependency information available
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:1.0.2 or one of its dependencies could not be resolved: Failure to find com.day.jcr.vault:content-package-maven-plugin:jar:1.0.2 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced @
[ERROR] Unknown packaging: content-package @ com.andy.nbapageflow:nbaPageFlow.ui.apps:[unknown-version], /home/andy/Dev/nbaPageFlow/ui.apps/pom.xml, line 34, column 16
[ERROR] Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:1.0.2 or one of its dependencies could not be resolved: Failure to find com.day.jcr.vault:content-package-maven-plugin:jar:1.0.2 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced @
[ERROR] Unknown packaging: content-package @ com.andy.nbapageflow:nbaPageFlow.ui.content:[unknown-version], /home/andy/Dev/nbaPageFlow/ui.content/pom.xml, line 34, column 16
@
[ERROR] The build could not read 2 projects -> [Help 1]
[ERROR]
[ERROR] The project com.andy.nbapageflow:nbaPageFlow.ui.apps:1.0-SNAPSHOT (/home/andy/Dev/nbaPageFlow/ui.apps/pom.xml) has 2 errors
[ERROR] Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:1.0.2 or one of its dependencies could not be resolved: Failure to find com.day.jcr.vault:content-package-maven-plugin:jar:1.0.2 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 2]
[ERROR] Unknown packaging: content-package @ com.andy.nbapageflow:nbaPageFlow.ui.apps:[unknown-version], /home/andy/Dev/nbaPageFlow/ui.apps/pom.xml, line 34, column 16
[ERROR]
[ERROR] The project com.andy.nbapageflow:nbaPageFlow.ui.content:1.0-SNAPSHOT (/home/andy/Dev/nbaPageFlow/ui.content/pom.xml) has 2 errors
[ERROR] Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:1.0.2 or one of its dependencies could not be resolved: Failure to find com.day.jcr.vault:content-package-maven-plugin:jar:1.0.2 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 2]
[ERROR] Unknown packaging: content-package @ com.andy.nbapageflow:nbaPageFlow.ui.content:[unknown-version], /home/andy/Dev/nbaPageFlow/ui.content/pom.xml, line 34, column 16
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/PluginManagerException
Steps to reproduce:
I created a new project based on the archtype via the command line:
mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate \
-DarchetypeGroupId=com.adobe.granite.archetypes \
-DarchetypeArtifactId=aem-project-archetype \
-DarchetypeVersion=15 \
-DarchetypeCatalog=https://repo.adobe.com/nexus/content/groups/public/
then I try to build using:
mvn clean install -P autoInstallBundle,autoInstallPackage
to AEM 6.4 and get the error
I don’t get the error when I do a plain mvn clean install
The repo for the project is here: https://github.com/andyklimczak/AEM-NBA-create-page-flow. It’s a prototype project and doesn’t contain any changes from the mvn archetype.
Thank you!
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Requested profile "autoInstallSinglePackage" does not exist
Solved: I am currently trying to import my project to AEM. I can use the profile "autoInstallPackage" just fine, and the package -...
Read more >WARNING The requested profile "projectname" could not be ...
The build is successful, but when I try to deploy the war file it doesen't work (no error message). The only warning I...
Read more >Maven Build Error : Missing Dependancy - CodeRanch
Under the content module there is pom.xml having profile "autoInstallPackage" to deploy whole project. local profile have some properties ...
Read more >How To Build AEM Projects With Maven - Bounteous
The run configuration defined above uses a profile of 'autoInstallPackage'. Below is how that build profile is defined inside the POM file for ......
Read more >How to build a new project in AEM | by Suren Konathala
mvn clean install -PautoInstallPackage "autoInstallPackage" is a default maven profile included in pom.xml which will build and deploy your project to AEM ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@vladbailescu, an alternative we have seen is to add the
adobe-public
profile to the command line argument i.e:Is there any downside to this approach (vs. updating
settings.xml
) ?You need to add the Adobe Nexus to your Maven
settings.xml
as described here: https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/ht-projects-maven.html