When adding a new dependency in the POM file of an OSGI bundle (which is deployed inside an AEM package to CRX) I will often see a number of unresolved dependencies in the OSGI console. The bundle will fail to activate.Example:org.jaxen.dom -- Cannot be resolvedorg.jaxen.dom4j -- Cannot be resolvedo...

Apologies: Can't seem to edit posts on here, the actions drop down just spins around indefinitely.We actually see the problem even just adding the filters element at all. Here's our full parent pom which is shared by 3 content packages<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="htt...

Our full parent POM looks like this:

It doesn't work at all on publish instances. It causes our deploys to fail with internal server error and no clues in the logs at all. Even just adding the following causes the error:

To be more specific, as soon as we add the mode "update" AEM becomes very unhappy and we just see internal server output with nothing in the error.log

The error occurs when I try to add a filter that allows existing values to be updated:<plugin>                    <groupId>com.day.jcr.vault</groupId>                    <artifactId>content-package-maven-plugin</artifactId>                    <version>0.5.24</version>                    <extensions>...

Sorry, now the error has changed:[ERROR] Request to http://...:4503/crx/packmgr/service.jsp failed, response=Internal Server Error

No this wasn't the issue it is a red herring. I still get the same 500 error when deploying to publish 2 now even as admin.

I can now deploy by deploying as our admin user. Why would the permissions suddenly have changed on our other user?

Hi Vishu,Thank you for your help.We are deploying use maven content plugin with bundle auto install. This has been working for a while.On the publish instances, CRX does not allow me to log in with the user who is deploying it says unknown username and password.When I log in as admin and upload the ...