Maven builds breaking due to content-package-maven-plugin | Community
Skip to main content
M
Mayank_Arora
Level 2
October 16, 2015
Solved

Maven builds breaking due to content-package-maven-plugin

  • October 16, 2015
  • 5 replies
  • 9255 views

Hello,

Recently, our project builds have started to break. Realized this when I was setting up the project on a new machine (no existing .m2 folder). It fails with the below error. Has anything changed recently? How should I go about fixing this? I tried mapping to 0.0.23 version of content-package-maven-plugin, but get a similar error.

Please advice.

[ERROR] The build could not read 2 projects -> [Help 1] [ERROR] [ERROR]   The project com.cq:UI:1.0-SNAPSHOT (C:\dir\cq5\UI\pom.xml) has 2 errors [ERROR]     Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:0.0.20 or one of its dependencies could not be resolved: Could not find artifact com.day.jcr.vault:content-package-maven-plugin:jar:0.0.20 in adobe (http://repo.adobe.com/nexus/content/groups/public/) -> [He [ERROR]     Unknown packaging: content-package @ line 19, column 13 [ERROR] [ERROR]   The project com.cq:config:1.0-SNAPSHOT (C:\dir\cq5\Config\pom.xml) has 2 errors [ERROR]     Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:0.0.20 or one of its dependencies could not be resolved: Could not find artifact com.day.jcr.vault:content-package-maven-plugin:jar:0.0.20 in adobe (http://repo.adobe.com/nexus/content/groups/public/) -> [He [ERROR]     Unknown packaging: content-package @ line 15, column 13 [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/PluginResolutionException
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by msullivan-r2i

We ran into the same thing, I think they may be switching the repo to SSL, and not everything is redirecting correctly.  I changed the repository settings references to https://repo.adobe and that seemed to resolve this.

5 replies

M
Community Advisor
MshajiCommunity Advisor
Community Advisor
October 16, 2015

If you are in eclipse, here are some ways of fixing this

1. Do project clean 

2. Right click on the project -> Maven -> Update project

msullivan-r2i
msullivan-r2iAccepted solution
Level 2
October 16, 2015

We ran into the same thing, I think they may be switching the repo to SSL, and not everything is redirecting correctly.  I changed the repository settings references to https://repo.adobe and that seemed to resolve this.

M
Mayank_AroraAuthor
Level 2
October 16, 2015

Hi,

I just received a confirmation from Adobe that they have set a redirect for http://repo.adobe.com/nexus/content/groups/public/ to point to HTTPS repo version. 

So, you can can continue to use the HTTP version of the repo. Thought it will be helpful to share.

- Mayank

M
Mayank_AroraAuthor
Level 2
October 16, 2015

Thanks MSullivan & Mshajiahmed. Updating the repo URL in pom.xml's to point to HTTPS worked.

K
Kanwaljit
Level 3
October 16, 2015

msullivan wrote...

We ran into the same thing, I think they may be switching the repo to SSL, and not everything is redirecting correctly.  I changed the repository settings references to https://repo.adobe and that seemed to resolve this.

 

 

 

Switching to https worked ! Cheers mate.

With all due respect to Adobe, I wasted couple of days scratching my head for this issue -:(

/KS

Terms & ConditionsAccessibility statement

Loading footer...