[
https://issues.apache.org/jira/browse/SLING-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656729#comment-16656729
]
Carsten Ziegeler commented on SLING-8042:
-----------------------------------------
We're going on circles on this one. In the past I've said several times that we
don't need the "id" at all in the feature file, but there was resistance
against this. So I stopped talking about it.
Having only half of the id in the file is even worse.
So either we leave it the way it is or we support not having the id in there at
all.
It still looks strange that I have to use maven variables just to put
information in there which is known already. These files belong to the maven
project.
> 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)
