[JCRVLT-232] Enforce constraints for package types

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: package-maven-plugin-1.0.0
• Fix Version/s: 3.4.2, package-maven-plugin-1.1.0
• Component/s: package maven plugin
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 18/Nov/17 14:37
• Updated: 16/Jan/20 07:55
• Resolved: 08/Oct/19 15:35

Description

Currently the package type only affects how the dependencies are considered to check for invalid filter rules (and only for package type "application"). This contradicts the javadoc of the parameter which states that

'application' and 'content' packages are not allowed to contain sub packages or embedded bundles.

(https://github.com/apache/jackrabbit-filevault-package-maven-plugin/blob/02a853e64d985f075fe88d19101d7c66d741767f/src/main/java/org/apache/jackrabbit/filevault/maven/packaging/AbstractPackageMojo.java#L104)
As long as this is not enforced during package build time please only list the enforced limitations of the according package types.

Issue Links

• causes: JCRVLT-400 '/etc/packages' should be a valid root
• is related to: JCRVLT-236 Package Maven Plugin: Improve packageType param documentation
• relates to: JCRVLT-170 Introduce the concept of package types