[
https://issues.apache.org/jira/browse/SLING-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905902#comment-16905902
]
Carsten Ziegeler commented on SLING-8541:
-----------------------------------------
[~schaefa] I've tested with your project and fixed some issues in the branch
and now merged everything into master.
Now, if you generated the feature files into "target/generated-features" you
don't need to configure anything in the slingfeature plugin
I still believe that supporting generated features in the slingfeature plugin
is the better option. This way we can for example convert other things like
karaf features into feature files and then use them in aggregation etc. It's
way more flexible
> 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
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: slingfeature-maven-plugin 1.0.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
