[ https://issues.apache.org/jira/browse/SLING-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656789#comment-16656789 ]
Carsten Ziegeler commented on SLING-8042: ----------------------------------------- So my suggestion is: * If an id is set in the feature file, group id, artifact id, version have to match the project * We still support the variable replacement * If no id is set, it will be set to the group id, artifact id, version of the project and the classifier is set to the name of the file * if no id is set *and* the project is a slingosgifeature project *and* the file is named "feature.json", then this becomes the main artifact The first two are what is implemented now > 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)