Ticket #1117 (closed task: fixed)

Opened 3 years ago

Last modified 2 years ago

Maven build separation of Ambra and Topaz

Reported by: rich Assigned to: pag
Priority: high Milestone: 0.9.3_rc2
Component: topaz-fedora Version: 0.9.1_rc1
Keywords: Cc:
Blocking: Blocked By:

Description

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.

Dependency Graph

Change History

03/09/09 14:16:46 changed by rich

  • milestone changed from 0.9.2 to 0.9.3.

Moving out of 0.9.2 and into 0.9.3 as part of the Topaz transition to Fedora Commons.

04/29/09 11:48:31 changed by rich

  • milestone changed from 0.9.3_rc1 to 0.9.3_rc2.

Moving into 0.9.3_rc2.

08/13/09 15:23:14 changed by npeterson

  • status changed from new to closed.
  • resolution set to fixed.