sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dirk Rudolph (Jira)" <j...@apache.org>
Subject [jira] [Updated] (SLING-10575) Bundles without feature-origin result in empty bundle to feature mapping
Date Wed, 30 Jun 2021 15:56:00 GMT

     [ https://issues.apache.org/jira/browse/SLING-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dirk Rudolph updated SLING-10575:
---------------------------------
    Description: 
When installing a feature archive of a feature similar to the following

{code:json}
{
  "id":"com.exmaple:my-feature-pkg:slingosgifeature:tiera:12345-SNAPSHOT",
  "bundles":[
    {
      "id":"com.example:my-bundle:1.2.3-SNAPSHOT",
      "start-order":"20"
    }
  ],
  "api-regions:JSON|false":[
    {
      "name":"global",
      "exports":[
        "com.example.my"
      ]
    }
  ]
} {code}

A bundle to feature mapping like 

{code}
com.example:my-bundle:1.2.3-SNAPSHOT=
{code}

will be created in the feature's {{org.apache.sling.feature.apiregions.factory}} configuration.
This is because the bundle does not specify any feature-origin(s).

For those cases the feature it self should be the origin of the bundle. The current version
of the api regions runtime will otherwise not find the feature a bundle belongs to and so
may not be able to resolve the api regions the bundle belongs to. 

An example where that can happen is the usage of the slingfeature-maven-plugin without using
the aggregation feature. When just building far from a hand-crafted feature model the feature-origin
may not be set on the api-region(s).


  was:
When installing a feature archive of a feature similar to the following

{code:json}
{
  "id":"com.exmaple:my-feature-pkg:slingosgifeature:tiera:12345-SNAPSHOT",
  "bundles":[
    {
      "id":"com.example:my-bundle:1.2.3-SNAPSHOT",
      "start-order":"20"
    }
  ],
  "api-regions:JSON|false":[
    {
      "name":"global",
      "exports":[
        "com.example.my"
      ]
    }
  ]
} {code}

A bundle to feature mapping like 

{code}
com.example:my-bundle:1.2.3-SNAPSHOT=
{code}

will be created in the feature's {{org.apache.sling.feature.apiregions.factory}} configuration.
This is because the bundle does not specify any feature-origin(s).

For those cases the feature it self should be the origin of the bundle. 

An example where that can happen is the usage of the slingfeature-maven-plugin without using
the aggregation feature. When just building far from a hand-crafted feature model the feature-origin
may not be set on the api-region(s).



> Bundles without feature-origin result in empty bundle to feature mapping
> ------------------------------------------------------------------------
>
>                 Key: SLING-10575
>                 URL: https://issues.apache.org/jira/browse/SLING-10575
>             Project: Sling
>          Issue Type: Bug
>          Components: Feature Model
>    Affects Versions: Installer Factory Feature Model 0.5.0
>            Reporter: Dirk Rudolph
>            Assignee: Dirk Rudolph
>            Priority: Major
>
> When installing a feature archive of a feature similar to the following
> {code:json}
> {
>   "id":"com.exmaple:my-feature-pkg:slingosgifeature:tiera:12345-SNAPSHOT",
>   "bundles":[
>     {
>       "id":"com.example:my-bundle:1.2.3-SNAPSHOT",
>       "start-order":"20"
>     }
>   ],
>   "api-regions:JSON|false":[
>     {
>       "name":"global",
>       "exports":[
>         "com.example.my"
>       ]
>     }
>   ]
> } {code}
> A bundle to feature mapping like 
> {code}
> com.example:my-bundle:1.2.3-SNAPSHOT=
> {code}
> will be created in the feature's {{org.apache.sling.feature.apiregions.factory}} configuration.
This is because the bundle does not specify any feature-origin(s).
> For those cases the feature it self should be the origin of the bundle. The current version
of the api regions runtime will otherwise not find the feature a bundle belongs to and so
may not be able to resolve the api regions the bundle belongs to. 
> An example where that can happen is the usage of the slingfeature-maven-plugin without
using the aggregation feature. When just building far from a hand-crafted feature model the
feature-origin may not be set on the api-region(s).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message