Bug 6003: Create config-filtering-parent
The Bug requests an addition of resource filtering functionality to config-parent.
There are several issues with replacing config-parent functionality:
- It is a top-level non-karaf feature, subject to API freeze.
- maven-resource-plugin operates on directories (as opposed to files).
- Users (ODL or otherwise) may change config.file value.
+ Groovy script can be used to extract directory name...
- but it is not easy propagate computed values to sibling plugins.
http://stackoverflow.com/questions/
21867095/setting-properties-in-maven-with-gmaven
- Using two profiles in config-parent does not work easily
http://stackoverflow.com/questions/
1504850/maven-activate-child-profile-based-on-property
(unless creation of temporary files in local filesystem is abused).
Therefore, a descendant parent pom is defined in this Change.
Presence of ${config.file} activates profiles in both config-parent and config-filtering-parent.
Small edits to config-plugin:
+ Add profile ID to distinguish filtering and non-filtering profiles.
Change-Id: Ia9ef770be232e04e4ba73f634a51b50665ee18ab
Signed-off-by: Vratko Polak <vrpolak@cisco.com>