[ 
https://issues.apache.org/jira/browse/ARIES-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415850#comment-15415850
 ] 

John Ross commented on ARIES-1443:
----------------------------------

I'm not sure all of the funny stuff going on in ARIES-1588, ARIES-1590, and 
ARIES-1591 are entirely due to this change (i.e. exposing feature capabilities 
at resolution time), but they may be.

This defect noted how feature capabilities are not exposed (none except 
osgi.identity, that is) after installing a feature until you restart the 
framework. I agree with the premise that the inconsistency is confusing and 
ideally should not exist. This could mean either features never expose more 
than the osgi.identity capability or always expose all capabilities. We seem to 
be in a bit of a bind because either solution causes issues. I'm pretty sure 
that if we remove the exposure of all capabilities permanently, it will cause 
some tests to fail, including in the CT. This should be confirmed, however. 
Always exposing capabilities are associated with the previously mentioned 
defects. Perhaps the best course of action would be to live with the 
inconsistency for now, assuming rolling this back would in fact fix those 
issues.

> After a restart the capabilities of a subsystem have changed (seem correct) 
> before the restart they seem wrong
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-1443
>                 URL: https://issues.apache.org/jira/browse/ARIES-1443
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>    Affects Versions: subsystem-2.0.6, subsystem-2.0.8
>         Environment: karaf pax-exam
>            Reporter: Bas
>            Assignee: John Ross
>              Labels: test-patch
>             Fix For: subsystem-2.1.0
>
>         Attachments: CapabilitiesDifferOnRestart.java.patch, 
> pax-web-jetty-bundle-4.2.5.jar
>
>
> A feature subsystem should export all capabilities of its constituents and it 
> does not do that after a fresh install. After a restart of the subsystem core 
> bundle it will export all the capabilities. 
> These seems to be a difference in parsing the capabilities of a persisted 
> subsystem and a new subsystem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to