sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mika Goeckel (Jira)" <>
Subject [jira] [Created] (SLING-8842) CP Converter creates packaging "slingfeature" instead of "slingosgifeature"
Date Wed, 13 Nov 2019 08:04:00 GMT
Mika Goeckel created SLING-8842:

             Summary: CP Converter creates packaging "slingfeature" instead of "slingosgifeature"
                 Key: SLING-8842
             Project: Sling
          Issue Type: Bug
          Components: Feature Model
    Affects Versions: Feature Model IO 1.1.2
            Reporter: Mika Goeckel

I used the sling-feature-converter-maven-plugin to create features.json files from the sling-starter provisioning
txt files.
The converter creates feature files with packaging „slingfeature“ but installes them
using „slingosgifeature“.
Then I use the slingfeature-maven-plugin to create a „full“ version from the files created
above. The -full file has an „assembled-features“ section containing the single feature
files with packaging „slingfeature“, itself on the other hand declares a packaging „slingosgifeature“.
Now I try to use the -full feature json as prototype for my own feature.json.
When I now use slingfeature-maven-plugin to assemble the artifacts, it tries to find them with
packaging „slingfeature“ (as declared in the assembled-section) – but can't find them
as they have been installed as „slingosgifeature“.
Could it be, that this is coming from FeatureJSONWriter Line 519:
// When providing a classifier a type must be provided and so we set it to 'slingfeature'
           idString =
               groupId + "/" +
               (nameOption.isEmpty() ? name : nameOption) + "/" +
               version +
               (nameOption.isEmpty() ? "" :
                   "/slingfeature/" + name );

This message was sent by Atlassian Jira

View raw message