This is due to an issue with specific versions of Maven (2.2.1 I believe). This should be fixed by simply using the latest content-package-maven-plugin version (0.0.20). And potentially upgrade Maven to the latest (3.1.1) as well, although I recognize that this can be more challenging in some enviro...