...
Project | Snapshots (groupId) | Third Party Libraries (groupId) | Releases (groupId) | ||
|---|---|---|---|---|---|
Akubra | fc-snapshots (org.akubraproject) | - | fc-releases (org.akubraproject) | ||
DSpace | dspace-snapshots (org.dspace) | dspace-repo (org.dspace) | dspace-repo (org.dspace) | ||
DuraCloud | - | fc-thirdparty (org.duracloud) | - | ||
Fedora | - | fc-thirdparty (org.fcrepo) | fc-releases (org.fcrepo) | ]]></ac:plain-text-body></ac:structured-macro> | |
Mulgara | - | - | - | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="078b819f636d23e8-84221ed7-400d4f5c-81068e3b-d3695e0983905e22fe2787c2"><ac:plain-text-body><![CDATA[ | Topaz | topaz-repo (org.topazproject) | topaz-repo ([2]) | topaz-repo (org.topazproject) | ]]></ac:plain-text-body></ac:structured-macro> |
...
Repository | Hosted At | Browsable? | Write Access? | GroupIds Published to Central ? | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f89daca8-7046-4282-b953-e3f7abb04d0a"><ac:plain-text-body><![CDATA[ | [dspace-repo | http://maven.dspace.org/] | OSU OSL | No | Manually granted by mdiggory? | [org.dspace | http://repo2.maven.org/maven2/org/dspace/] , [org.duraspace | http://repo2.maven.org/maven2/org/duraspace/] [3], [org.fedora-commons | http://repo2.maven.org/maven2/org/fedora-commons/] [3] | ]]></ac:plain-text-body></ac:structured-macro> |
OSU OSL | No | " ? | None No | |||||||
Cornell | Yes | Manually granted by cwilper | None No | |||||||
Cornell | Yes | " | None No | |||||||
Cornell | Yes | " | None No | |||||||
PLoS | Yes | Manually granted by Ronald? | None |
| Wiki Markup |
|---|
\[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. |
What Merged Repositories Might Look Like
Repository | Hosted At | Browsable? | Write Access? | Published to Central? |
|---|---|---|---|---|
duraspace-repo | OSU OSL | Yes | Granted by admin(s) for each project, under that project's groupId | Yes |
duraspace-snapshots | OSU OSL | Yes | " | No |
Participating Projects:
Should:
- Comply with central requirements; all artifacts published by each project (third-party or not):
- Need to be under the groupId of the project responsible for authoring/publishing the POM.
- Need to be freely distributable.
- Designate admin(s) who can delegate write access to the portion of the repository under that project's control.