We are using content-package-maven-plugin 1.0.6 version for AEM 6.5.22
[ERROR] Missing response status information in response: <?xml version="1.0" encoding="UTF-8"?>
<html>
<head>
<title>Content modified /crx/packmgr/service.jsp</title>
</head>
<body>
<h1>Content modified /crx/packmgr/service.jsp</h1>
<table>
<tbody>
<tr>
<td>Status</td>
<td>
<div id="Status">200</div>
</td>
</tr>
<tr>
<td>Message</td>
<td>
<div id="Message">OK</div>
</td>
</tr>
<tr>
<td>Location</td>
<td>
<a href="/crx/packmgr/service.jsp" id="Location">/crx/packmgr/service.jsp</a>
</td>
</tr>
<tr>
<td>Parent Location</td>
<td>
<a href="/crx/packmgr" id="ParentLocation">/crx/packmgr</a>
</td>
</tr>
<tr>
<td>Path</td>
<td>
<div id="Path">/crx/packmgr/service.jsp</div>
</td>
</tr>
<tr>
<td>Referer</td>
<td>
<div id="Referer">about:blank</div>
</td>
</tr>
<tr>
<td>ChangeLog</td>
<td>
<div id="ChangeLog"><pre>modified("/crx/packmgr/service.jsp/file/jcr:lastModified");<br/>modified("/crx/packmgr/service.jsp/file/jcr:mimeType");<br/>modified("/crx/packmgr/service.jsp/file/jcr:data");<br/>modified("/crx/packmgr/service.jsp/install");<br/></pre></div>
</td>
</tr>
</tbody>
</table>
<p>
<a href="/crx/packmgr/service.jsp">Modified Resource</a>
</p>
<p>
<a href="/crx/packmgr">Parent of Modified Resource</a>
</p>
</body>
</html>
Views
Replies
Total Likes
Can anyone suggest how to resolve it.
Views
Replies
Total Likes
The error indicates that the content-package-maven-plugin is unable to parse the response from the AEM Package Manager properly. This issue is common when the plugin expects a specific JSON response format, but the server returns an HTML response instead.
The content-package-maven-plugin version 1.0.6 is outdated. Upgrade to a newer version (e.g., 1.0.8 or later) that may have fixes for response parsing issues:
<plugin>
<groupId>com.day.jcr.vault</groupId>
<artifactId>content-package-maven-plugin</artifactId>
<version>1.0.8</version>
</plugin>
AEM Package Manager can return responses in JSON format. Ensure that the plugin is configured to request JSON responses by adding the jsonResponse parameter:
<configuration>
<jsonResponse>true</jsonResponse>
</configuration>
Check Maven Configuration:
Verify the pom.xml configuration for the plugin. Ensure the correct URL, credentials, and parameters are set:
<plugin>
<groupId>com.day.jcr.vault</groupId>
<artifactId>content-package-maven-plugin</artifactId>
<version>1.0.8</version>
<configuration>
<url>http://localhost:4502/crx/packmgr/service.jsp</url>
<user>admin</user>
<password>admin</password>
<jsonResponse>true</jsonResponse>
</configuration>
</plugin>
Check AEM Logs:
Review the AEM error logs (error.log) for any issues related to the Package Manager or permissions.
Test with CURL:
Use CURL to test the /crx/packmgr/service.jsp endpoint and verify the response format:
curl -u admin:admin -X POST http://localhost:4502/crx/packmgr/service.jsp
This is the error after updating version to 1.0.8,
[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.8 or one of its dependencies could not be resolved: Could not find artifact com.day.jcr.vault:content-package-maven-plugin:jar:1.0.8 in adobe-public-releases (https://repo.adobe.com/nexus/content/groups/public)
Views
Replies
Total Likes
@SaiSreedevi I dont see 1.0.8 version in adobe public repository my bad. But can you try
<plugin>
<groupId>com.day.jcr.vault</groupId>
<artifactId>content-package-maven-plugin</artifactId>
<version>1.0.6</version>
<configuration>
<jsonResponse>true</jsonResponse>
</configuration>
</plugin>
and try in local once. I am suspect some issue with your content package
Use CURL to test the /crx/packmgr/service.jsp endpoint and verify the response format:
curl -u admin:admin -X POST http://localhost:4502/crx/packmgr/service.jsp
Current version is 1.0.6 only, but while adding
<jsonResponse>true</jsonResponse>
this element to pom.xml it is showing error that
Element jsonResponse is not allowed here
Views
Replies
Total Likes
@SaiSreedevi but did you try installing the generated package manually to your AEM server ? Let me try on WKND project and will update you
Packages are uploading successfully there is no issue during installing the generated package manually to the Servers.
Issue is only during the deployment of code to PROD servers, we don't have any issue with other servers.
Views
Replies
Total Likes
Views
Like
Replies
Views
Likes
Replies
Views
Likes
Replies