You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Marcel Offermans (Created) (JIRA)" <ji...@apache.org> on 2011/12/09 17:06:39 UTC
[jira] [Created] (FELIX-3264) Dependency manager shell should not
print the state of optional dependencies when not all required ones are
available
Dependency manager shell should not print the state of optional dependencies when not all required ones are available
---------------------------------------------------------------------------------------------------------------------
Key: FELIX-3264
URL: https://issues.apache.org/jira/browse/FELIX-3264
Project: Felix
Issue Type: Improvement
Components: Dependency Manager
Affects Versions: dependencymanager-3.0.0
Reporter: Marcel Offermans
Internally, the dependency manager only starts listening to optional dependencies once all required ones are available. That means that optional dependencies will always be listed as "unavailable" in that scenario. That looks somewhat funny though: a required dependency to A that is available might also be shown as an optional one to A in a different component, and it might seem unavailable there.
The fix is to not print the state of (optional) dependencies if they have not been started yet.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (FELIX-3264) Dependency manager shell should not
print the state of optional dependencies when not all required ones are
available
Posted by "Marcel Offermans (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans reassigned FELIX-3264:
---------------------------------------
Assignee: Marcel Offermans
> Dependency manager shell should not print the state of optional dependencies when not all required ones are available
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-3264
> URL: https://issues.apache.org/jira/browse/FELIX-3264
> Project: Felix
> Issue Type: Improvement
> Components: Dependency Manager
> Affects Versions: dependencymanager-3.0.0
> Reporter: Marcel Offermans
> Assignee: Marcel Offermans
>
> Internally, the dependency manager only starts listening to optional dependencies once all required ones are available. That means that optional dependencies will always be listed as "unavailable" in that scenario. That looks somewhat funny though: a required dependency to A that is available might also be shown as an optional one to A in a different component, and it might seem unavailable there.
> The fix is to not print the state of (optional) dependencies if they have not been started yet.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-3264) Dependency manager shell should not
print the state of optional dependencies when not all required ones are
available
Posted by "Marcel Offermans (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans resolved FELIX-3264.
-------------------------------------
Resolution: Fixed
Committed a fix for this.
> Dependency manager shell should not print the state of optional dependencies when not all required ones are available
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-3264
> URL: https://issues.apache.org/jira/browse/FELIX-3264
> Project: Felix
> Issue Type: Improvement
> Components: Dependency Manager
> Affects Versions: dependencymanager-3.0.0
> Reporter: Marcel Offermans
> Assignee: Marcel Offermans
>
> Internally, the dependency manager only starts listening to optional dependencies once all required ones are available. That means that optional dependencies will always be listed as "unavailable" in that scenario. That looks somewhat funny though: a required dependency to A that is available might also be shown as an optional one to A in a different component, and it might seem unavailable there.
> The fix is to not print the state of (optional) dependencies if they have not been started yet.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira