[
https://issues.apache.org/jira/browse/SLING-9232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-9232.
-------------------------------------
Resolution: Fixed
Implemented in [1] as a general mechanism. Each selection can now contain one
or more <refsInclude> statements - which is a pattern to select refs files like
"src/main/references/*.refs"
Added basic test cases, enhanced test covered for feature selection
[1]
https://github.com/apache/sling-slingfeature-maven-plugin/commit/791df0e6289b25f5476f2993c869faf18016693f
> Support ref files in aggregates and other mojos
> -----------------------------------------------
>
> Key: SLING-9232
> URL: https://issues.apache.org/jira/browse/SLING-9232
> Project: Sling
> Issue Type: New Feature
> Components: Feature Model, Maven Plugins and Archetypes
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: slingfeature-maven-plugin 1.1.22
>
>
> The selection for the aggregate mojo (and all other mojos which allow to
> select feature files) currently only allows to select features from files
> within the project, a classifier (again a feature of the project) or
> artifacts (external feature files).
> This mechanism makes it complicated to let other maven plugins generate a
> list of features and then use them as input in the slingfeature maven plugin,
> for example to form an aggregate.
> However, the feature model already contains the concept of ref files - text
> files containing a list of features.
> If we now allow to select features from ref files in addition to the already
> available selection mechanism, other plugins can write such a ref file and it
> can be included.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
