For the Topaz transition to Fedora Commons, the Topaz codebase will need to be extracted in such a way that Ambra dependencies on Topaz/Mulgara do not fail. The resulting modules will need to be provided as public Maven packages so Ambra can access the non-local modules over the internet.
Tasks (from Paul):
- Maven
- Identify the Maven repository where Topaz will be providing Maven modules to the public.
- Set the public repository up for distribution. This may involve an account for a public system, or a sysadmin task to configure an in-house system.
- Ambra
- Remove the topaz and mulgara modules.
- Refer to the extracted modules in the public repository instead.
- Topaz
- Set up a new Maven build for the modules extracted from Ambra.
- Configure the build to publish to the public Maven repository.
- Mulgara
- Set up the build to create a module suitable for Maven, and publish to the public Maven repository.