...
Project | Snapshots (groupId) | Third Party Libraries (groupId) | Releases (groupId) | |
|---|---|---|---|---|
Akubra | fc-snapshots (org.akubraproject) | - | fc-releases (org.akubraproject) | |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="37ddcdfb-6a93-4b31-b608-32b0334ca632"><ac:plain-text-body><![CDATA[ | DSpace | dspace-snapshots (org.dspace) [4] | dspace-repo (org.dspace) [4] | dspace-repo (org.dspace) [4] |
DuraCloud | - | fc-thirdparty (org.duracloud) | - | |
Fedora | - | fc-thirdparty (org.fcrepo) | fc-releases (org.fcrepo) | |
Mulgara | - | - | - | <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro - id="adda786f-9275-4468-b082-2fc28d426294"><ac:plain-text-body><![CDATA[ |
Topaz | topaz-repo (org.topazproject) | topaz-repo ([2]) | topaz-repo (org.topazproject) | ]]></ac:plain-text-body></ac:structured-macro> |
...
\[1\] Currently, libraries that are "third party" to the FCRepo project are split between the fc-thirdparty repository (for libs authored by projects outside DuraSpace) and the fc-releases repository (for libs authored by other DuraSpace projects). The current FCRepo groupId/artifactId naming convention is further [documented here|https://fedora-commons.org/confluence/display/FCREPO/Maven+Ids+and+Repositories].
Wiki Markup
\[4\] DSpace release artifacts are not exposed via local dspace-repo, all release builds use the central repo at [http://repo1.maven.org/maven2/org/dspace/|http://repo1.maven.org/maven2/org/dspace/] unless the developer configures maven to behave differently. All third party requirements not already in the central repo or other popular repository such as java.net or codehaus (excluding oracle JDBC drivers) are published under the org.dspace groupId so they will be properly rynced to the central repository after release.
Repository details
Repository | Hosted At | Browsable? | Write Access? | GroupIds Published to Central | Repository Platform | Deployment | |
|---|---|---|---|---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="07078542-eeaf-43fe-98b8-93089ae23032"><ac:plain-text-body><![CDATA[ | [dspace-repohttp://maven.dspace.org/] | OSU OSL | Yes | Manually granted by mdiggory | [org.dspacehttp://repo2.maven.org/maven2/org/dspace/] , [org.duraspacehttp://repo2.maven.org/maven2/org/duraspace/] [3], [org.fedora-commonshttp://repo2.maven.org/maven2/org/fedora-commons/] [3] | Apache HTTPD Filesystem, WEB-DAV can be made available | SCP Wagon |
OSU OSL | Yes | " | None | " | " | ||
Cornell | Yes | Manually granted by cwilper | None |
|
| ||
Cornell | Yes | " | None |
|
| ||
Cornell | Yes | " | None |
|
| ||
PLoS | Yes | Manually granted by Ronald? | None |
|
|
...
\[3\] These groupIds are not used. Generally, groupIds of projects within DuraSpace are tied to the project, not the overarching organization. Also, the Fedora Repository project has now standardized on using org.fcrepo as its groupId. (MRD: I agree)
What Repository Platform might be utilized
...