content-package-maven-plugin install fails with error 500 on Windows

[outcoxed]

We recently upgraded to AEM 5.6, which caused our build to stop working. We've been able to get the builds up and running based on Adobe's multimodule-content-package-archetype, but they don't seem to work at all when installing our app into CQ from Windows.

The build seems to be working fine, but on the very last line of the build we get the following error on Win 7:

[INFO] --- content-package-maven-plugin:0.0.20:install (install-content-package) @myApp ---

[INFO] Installing myApp-components (~/Documents/myApp/myApp-components/target/myApp-components-0.0.2-SNAPSHOT.zip) to http://localhost:4502/crx/packmgr/service.jsp

[ERROR] Request failed:
com.day.jcr.vault.packaging.PackageException: java.lang.IllegalStateException:
folder handler did not accept /apps/myApp/components/pages/global.jspx
(500)

Is there something that needs to be configured to install a .jspx file? This is the only jspx file that I know of in our build.

[outcoxed]

So, I tracked this down to the Vault tool, which is creating empty directories during "vlt up --force". In this case there was a global.jspx.dir folder created by vault, apparently to hold a completely useless .vlt file.

Is there any way I can get Vault to stop copying these .dir directories? Or to get my maven plugin build to stop including these empty directories in the jar file? 

[Yogesh_Upadhyay · Accepted solution]

Looks like error happened during installation. What version of CQ you using ? JSP engine should support jspx extension https://issues.apache.org/jira/browse/SLING-828. You can also create Daycare ticket with full stack trace to find root cause.

Yogesh