[
https://issues.apache.org/jira/browse/SLING-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987588#comment-16987588
]
Carsten Ziegeler commented on SLING-8875:
-----------------------------------------
The IncludeArtifact mojo creates a feature model and adds the main artifact to
it; it's not expecting any input; it can use an existing feature model and
append the main artifact to it.
However, I see the benefit of having a separate mojo that generates a feature
model based on dependencies independent of IncludeArtifact (and yes, that
feature model could then be used as input for IncludeArtifact)
I think the current PR contains some unused code, like the addConfiguration
method in the feature manager. Also runmode handling shouldn't be part of it.
> Create new Goal to create a FM Descriptor from a Maven Module
> -------------------------------------------------------------
>
> Key: SLING-8875
> URL: https://issues.apache.org/jira/browse/SLING-8875
> Project: Sling
> Issue Type: New Feature
> Components: Feature Model
> Affects Versions: slingfeature-maven-plugin 1.1.10
> Reporter: Andreas Schaefer
> Assignee: Andreas Schaefer
> Priority: Major
> Fix For: slingfeature-maven-plugin 1.1.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In order to use FM Descriptor in projects modules should be creating and
> exposing their FM Descriptors in local / remote Maven repositories. This way
> an assembler can take these FMs and build up its Sling instance.
> To avoid making each module to write their own FM Descriptor we should have a
> Goal in the SlingFeature Maven Plugin that does that automatically.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
