Maven Build Issue | Community
Skip to main content
Jai1122
Jai1122
October 16, 2015
Solved

Maven Build Issue

  • October 16, 2015
  • 4 replies
  • 1786 views

Hi All,

   I am getting the exact issue mentioned here

Looks like the post is for tag management. How far this is true for AEM?

Please post your comments.

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 Alex Collignon

Hi Jai,

I am not sure I understand why you refer to a proxy situation. If you're facing the following known issue

Failed to execute goal com.day.jcr.vault:content-package-maven-plugin:0.0.20:package (default-package) on project smarter-content: Execution default-package of goal com.day.jcr.vault:content-package-maven-plugin:0.0.20:package failed: A required class was missing while executing com.day.jcr.vault:content-package-maven-plugin:0.0.20

then you need to bump the version of content-package-maven-plugin to 0.0.24 which addresses the problem.

Cheers,

Alex

4 replies

A
Adobe Employee
Alex CollignonAdobe Employee
Adobe Employee
October 16, 2015

Hi Jail,

I would recommend you upgrade your content-package-maven-plugin to the latest version (0.0.24). This should solve the problem.

Hope that helps,

Alex

Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
October 16, 2015

I am using maven 3.3 without a problem for AEM.

Jai1122
Jai1122Author
October 16, 2015

I am stilling facing the issue. I do not think it as a proxy issue also.

A
Adobe Employee
Alex CollignonAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Hi Jai,

I am not sure I understand why you refer to a proxy situation. If you're facing the following known issue

Failed to execute goal com.day.jcr.vault:content-package-maven-plugin:0.0.20:package (default-package) on project smarter-content: Execution default-package of goal com.day.jcr.vault:content-package-maven-plugin:0.0.20:package failed: A required class was missing while executing com.day.jcr.vault:content-package-maven-plugin:0.0.20

then you need to bump the version of content-package-maven-plugin to 0.0.24 which addresses the problem.

Cheers,

Alex

Terms & ConditionsAccessibility statement

Loading footer...