[
https://issues.apache.org/jira/browse/ARIES-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Ross resolved ARIES-728.
-----------------------------
Resolution: Fixed
Assignee: John Ross
> Check in initial baseline for subsystems implementation based on latest RFCs.
> -----------------------------------------------------------------------------
>
> Key: ARIES-728
> URL: https://issues.apache.org/jira/browse/ARIES-728
> Project: Aries
> Issue Type: New Feature
> Components: Subsystem
> Reporter: John Ross
> Assignee: John Ross
>
> Checking in the initial baseline for the subsystems implementation based on
> the latest Subsystems (RFC 152) and OBR (RFC 112) working drafts. Note that
> subsystems is not currently part of the build. Moving forward, work will be
> completed in more discrete, well-defined chunks.
> I would describe the current states of RFC 112 and 152 as mature and
> maturing, respectively. A lot of work remains to be done on the
> implementation and, particularly, on the testing, however.
> One major necessity is an implementation of the Resolver. Currently,
> subsystems wraps the Resolver interface around the existing Felix OBR
> RepositoryAdmin as a placeholder in order to have support for pulling in
> content and transitive dependencies from remote repositories. However, this
> leaves out the wiring state which will be used for things such as computing
> certain headers in the subsystem and deployment manifests. Presumably, Felix
> will have a Resolver implementation at some point in the future. We are also
> looking at the possibility of implementing a Resolver on top of Equinox.
> Over the next few weeks, I will be focusing primarily on hardening support
> for features.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
