[ https://issues.apache.org/jira/browse/FELIX-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks resolved FELIX-4857. --------------------------------- Resolution: Fixed Assignee: David Jencks This is fixed in the recent scr 2 release. > SCR Gogo commands outputs wrong infos when a component is unsatisfied because > of missing configuration > ------------------------------------------------------------------------------------------------------ > > Key: FELIX-4857 > URL: https://issues.apache.org/jira/browse/FELIX-4857 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) > Affects Versions: scr-1.8.2 > Reporter: Simon Chemouil > Assignee: David Jencks > > The Gogo scr:info command doesn't show when a DS component has > Configuration.REQUIRE and is unsatisfied because the configuration is > missing. Instead, it marks a reference as unsatisfied even though it is > available and consumed elsewhere in the same bundle. > {noformat} > $ scr:info 0 > ID: 0 > Name: my-component > Bundle: my-bundle (56) > State: unsatisfied > Default State: enabled > Activation: delayed > Configuration Policy: require > Activate Method: activate (declared in the descriptor) > Deactivate Method: deactivate > Modified Method: - > Configuration Pid: my-component > Services: io.lambdacube.service.MyService > Service Type: service > Reference: JsonMapper > Satisfied: unsatisfied > Service Name: io.lambdacube.core.json.JsonMapper > Multiple: single > Optional: mandatory > Policy: static > Policy option: reluctant > (unbound) > Properties: > component.id = 0 > component.name = my-component > {noformat} > In that example, JsonMapper is actually available. Instead, the scr:info > command should state it's unsatisfied because the configuration entry is > missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)