[
https://issues.apache.org/jira/browse/SLING-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894464#comment-16894464
]
Carsten Ziegeler commented on SLING-8541:
-----------------------------------------
I don't want the converter be part of the slingfeature plugin; it's not it's
business to convert other things into features.
I assume your features end up somewhere in a target directory, right? So you
need to configure this for the slingfeature plugin to be picked up, you can
either do this using <features> (which defaults to src/main/features) or we can
use a new <generatedFeatures> directive.
The latter allows to combine local features (from src/main/features) with
generated (or converted) features from other plugins. The cpconverter being one
of it. But the conversion should not be part of the slingfeature plugin
> slingfeature-maven-plugin should allow for generated feature model files
> ------------------------------------------------------------------------
>
> Key: SLING-8541
> URL: https://issues.apache.org/jira/browse/SLING-8541
> Project: Sling
> Issue Type: New Feature
> Components: Feature Model
> Affects Versions: slingfeature-maven-plugin 1.0.4
> Reporter: Andreas Schaefer
> Priority: Major
> Fix For: slingfeature-maven-plugin 1.0.6
>
>
> The Sling Feature Maven Plugin is checking that the feature model folder is
> containing feature model files when the plugin is started.
> This fails when the FM are generated prior to the execution of the Sling
> Feature Maven Plugin. This check should be either made optional or moved
> prior to the actual execution of the Plugin's goal.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
