[
https://issues.apache.org/jira/browse/SLING-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656754#comment-16656754
]
David Bosschaert commented on SLING-8042:
-----------------------------------------
I think that when you are looking at a feature then you should have the whole
feature, including its ID. The ID should be part of the feature declaration
IMHO.
Having said that, I have no objection to simple template style variable
substitution that is used when 'building' the feature file. As long as what is
deployed in maven as the feature has the ID in it.
Having a variable that is understood by the slingfeature-maven-plugin (e.g.
${file.name} or something like that) could be used as a placeholder. Then, once
the feature ends up in the Maven repo, all these variables are replaced with
real values and the feature there is fully defined.
> The slingfeature-maven-plugin should be able to derive the name of a feature
> from the file name
> -----------------------------------------------------------------------------------------------
>
> Key: SLING-8042
> URL: https://issues.apache.org/jira/browse/SLING-8042
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model
> Reporter: Radu Cotescu
> Assignee: David Bosschaert
> Priority: Major
>
> The {{slingfeature-maven-plugin}} should be able to derive the name of a
> feature from the file name, if the name is missing from the feature
> definition.
> Assuming a file called {{my-feature.json}}, with the following contents:
> {noformat}
> {
> "id" :
> "${project.groupId}:${project.artifactId}:slingfeature:${project.version}",
> "bundles" :[
> ...
> ]
> }
> {noformat}
> then the {{slingfeature-maven-plugin}} should infer that the feature it's
> building is called {{my-feature}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
