This document describes the conventions and rationale for the maven groupIds, artifactIds, and repository layout used by the Fedora Repository Project.
Note |
---|
This document is out of date. Starting with Fedora 3.5, released Fedora artifacts are now available at Maven central, with the help of Sonatype OSS Hosting. Third-party artifacts are still hosted in the DuraSpace repositories as noted below. |
Contents:
Table of Contents |
---|
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.
Group: org.
...
fcrepo
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 fcrepo-
- 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, in which case the artifactId does not begin with fcrepo-.
Maven Repositories
We currently host a set of repositories using Nexus.
...
three public maven repositories, providing artifacts relevant to the Fedora Repository Project as well as other DuraSpace projects.
Releases
Contains officially released artifacts that are both authored and packaged by the same a DuraSpace project.
...
URL: https://m2.duraspace.org/content/repositories/releases
Snapshots
Snapshots for above.
URL: https://m2.duraspace.org/content/repositories/snapshots
ThirdParty
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://m2.duraspace.org/content/repositories/thirdpartyStuff we haven't written but depend on.