You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Table of Contents

This document describes the conventions and rationale for the maven groupIds, artifactIds, and repository layout used by the Fedora Repository Project.

Maven GroupIds and ArtifactIds

General Conventions

  • groupId:
    • identifies the project responsible for publishing the artifacts
    • begins with org.projectname, which corresponds directly to a domain name under the project's control
  • artifactId
    • identifies the artifact released by the project.

org.fedorarepo

This is the groupId reserved for software that is either:

  • A core artifact of the Fedora Repository Project.
    • In this case, by convention, the artifactId begins with fedorarepo-
  • A dependency of the Fedora Repository Project that does not yet exist in a public maven repository, and was therefore packaged by the Fedora Repository team.

Maven Repositories

We currently host a set of publicly-accessible repositories using Nexus.

DuraSpace Releases

Contains officially released artifacts that are both authored and packaged by the same DuraSpace project.

URL: https://fedora-commons.org/m2/content/repositories/releases

DuraSpace Snapshots

Snapshots for above.

URL: https://fedora-commons.org/m2/content/repositories/snapshots

DuraSpace ThirdParty

Artifacts not otherwise available in a public maven repository.  The groupId used for any of these artifacts identifies the DuraSpace project that authored the pom -- not the project that authored the software.

URL: https://fedora-commons.org/m2/content/repositories/thirdparty

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels