Move generation of Maven repository from subsystem-core to subsystem-itests.
----------------------------------------------------------------------------
Key: ARIES-729
URL: https://issues.apache.org/jira/browse/ARIES-729
Project: Aries
Issue Type: Bug
Components: Subsystem
Reporter: John Ross
The generation of the remote repository currently occurs as part of the core
subsystems functionality. Moving forward, it will not be the responsibility of
the susbsystems implementation to generate such repositories. Rather, such
repositories will be generated externally and registered as Repository services
in the OSGi registry. Subsystems will then search these registered repositories
in service ranking order during the provisioning process. Consequently, I will
move this functionality to subsystem-itests since this repository is still
necessary for testing purposes.
For the time being, I will keep the contents of
org.apache.aries.subsystem.core.obr.felix in place, and subsystem-itests will
import the contents. However, I wonder if even this should ultimately still
reside in subsystem-core. This package contains a set of classes that
essentially create a composite Repository around RepositoryAdmin. As part of
setup, the test harness will need to generate the OBR XML based on the local
Maven repository, register the XML with RepositoryAdmin, then register the
RepositoryAdminRepository from the previously mentioned package as a Repository
service with the framework.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
