[JCRVLT-230] Allow to give an explicit directory as source for META-INF/vault

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: package-maven-plugin-1.0.0
• Fix Version/s: package-maven-plugin-1.0.1
• Component/s: package maven plugin
• Assignee: Tobias Bocanegra
• Reporter: Konrad Windszus
• Created: 17/Nov/17 15:18
• Updated: 20/Dec/17 09:29
• Resolved: 11/Dec/17 20:36

Description

Currently the META-INF/vault structure within the packages is built from <workDirectory>/META-INF/vault.

This directory is used for two purposes

1. It receives the generated filter.xml, the merged properties.xml, the config.xml and the settings.xml
2. It acts as a source for the resulting package's META-INF/vault

Not all meta files below META-INF/vault are being generated through the plugin itself. Some need to be written manually to workDirectory with the help of the maven-resource-plugin.

It would be good to allow to give an explicit source directory for the META-INF/vault directory (similar to jcrSourceDirectory) separated from workDirectory. This would allow to e.g. specify the packages thumbnail image, without being forced to copy it over to from src to target.
In addition this parameter should clearly define which meta files are always generated by the filevault-package-maven-plugin and are therefore never considered, even if they are located in the given META-INF/vault source directory.

Issue Links

• is related to: JCRVLT-210 Allow to define excludes for the ContentPackageArchiver to prevent copying of script files from src to target