[
https://issues.apache.org/jira/browse/SLING-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891801#comment-16891801
]
Carsten Ziegeler commented on SLING-8541:
-----------------------------------------
As discussed in the mailing list I don't want to remove the usage of the
DependencyLifecycleParticipant as this is the only way to work in a multi
project setup with inter dependencies between features. The DLP is also useful
for scenarios where you want to have the artifacts of a feature as project
dependencies (although this could be moved to a separate plugin)
The use case described here is about generated features - which obviously are
not available when the DLP runs.
How about we add a new configuration option
<generatedFeatures>...</generatedFeatures>
and this allows to specify a directory in the target folder and this option is
evaluated (once) when the first mojo needing features is invoked
> 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)
