Key: FCREPO-825
URL: https://jira.duraspace.org/browse/FCREPO-825
Project: Fedora Repository Project
Issue Type: Improvement
Components: Fedora, java-client, Trippi
Reporter: Chris Wilper
Assignee: Chris Wilper
Fix For: Fedora 3.5
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Chris Wilper updated FCREPO-825:
--------------------------------
Status: Open (was: Received)
Chris Wilper commented on FCREPO-825:
-------------------------------------
Begin deploying Fedora maven release artifacts to Sonatype's maven repository. When finished, start publishing to central if possible.
Chris Wilper updated FCREPO-825:
--------------------------------
Description:
The goal is to move to Sonatype Maven hosting, so that
1) The Fedora build no longer depends on any DuraSpace repository.
2) The artifacts we build (both releases and snapshots) can be deployed to Sonatype.
A longer-term goal is to get our artifacts in line with central sync up requirements, so that we can publish future releases to central.
For reference, here is the Sonatype OSS Maven Repository Usage Guide, which also includes a section on the latest Central sync requirements:
http://docs.sonatype.org/x/SQBl
...and here is the original Sonatype hosting ticket for org.fcrepo:
https://issues.sonatype.org/browse/OSSRH-307
> Move to Sonaype with automated snapshots triggered by Bamboo
> ------------------------------------------------------------
>
> Key: FCREPO-825
> URL: https://jira.duraspace.org/browse/FCREPO-825
> Project: Fedora Repository Project
> Issue Type: Improvement
> Components: Fedora, java-client, Trippi
> Reporter: Chris Wilper
> Assignee: Chris Wilper
> Fix For: Fedora 3.5
>
>
> The goal is to move to Sonatype Maven hosting, so that
> 1) The Fedora build no longer depends on any DuraSpace repository.
> 2) The artifacts we build (both releases and snapshots) can be deployed to Sonatype.
> A longer-term goal is to get our artifacts in line with central sync up requirements, so that we can publish future releases to central.
> For reference, here is the Sonatype OSS Maven Repository Usage Guide, which also includes a section on the latest Central sync requirements:
> http://docs.sonatype.org/x/SQBl
> ...and here is the original Sonatype hosting ticket for org.fcrepo:
> https://issues.sonatype.org/browse/OSSRH-307
Chris Wilper updated FCREPO-825:
--------------------------------
Fix Version/s: (was: Fedora 3.5)
Fedora 3.6
> Move to Sonaype with automated snapshots triggered by Bamboo
> ------------------------------------------------------------
>
> Key: FCREPO-825
> URL: https://jira.duraspace.org/browse/FCREPO-825
> Project: Fedora Repository Project
> Issue Type: Improvement
> Components: Fedora, java-client, Trippi
> Reporter: Chris Wilper
> Assignee: Chris Wilper
> Fix For: Fedora 3.6
>
>
> The goal is to move to Sonatype Maven hosting, so that
> 1) The Fedora build no longer depends on any DuraSpace repository.
> 2) The artifacts we build (both releases and snapshots) can be deployed to Sonatype.
> A longer-term goal is to get our artifacts in line with central sync up requirements, so that we can publish future releases to central.
> For reference, here is the Sonatype OSS Maven Repository Usage Guide, which also includes a section on the latest Central sync requirements:
> http://docs.sonatype.org/x/SQBl
> ...and here is the original Sonatype hosting ticket for org.fcrepo:
> https://issues.sonatype.org/browse/OSSRH-307
--
Chris Wilper updated FCREPO-825:
--------------------------------
Comment: was deleted
(was: Begin deploying Fedora maven release artifacts to Sonatype's maven repository. When finished, start publishing to central if possible.)
> Complete Maven hosting migration to Sonatype with sync to Maven Central
> -----------------------------------------------------------------------
>
> Key: FCREPO-825
> URL: https://jira.duraspace.org/browse/FCREPO-825
> Project: Fedora Repository Project
> Issue Type: Epic
> Components: Fedora, java-client, Trippi
> Reporter: Chris Wilper
> Priority: Major
>
> The primary goal of this epic is to migrate Fedora's Maven artifacts completely to Sonatype and sync them to Maven Central, adhering to as much of the Sonatype Central Sync Requirements as possible. In particular, we aspire to have no library dependencies that are not hosted in Maven Central. We also want to take advantage of Sonatype's snapshot repository hosting option as an automatic part of our continuous integration builds that run at bamboo.duraspace.org.
> For reference, here is the Sonatype OSS Maven Repository Usage Guide, which also includes a section on the latest Central sync requirements:
> http://docs.sonatype.org/x/SQBl
> ...and here is the original Sonatype hosting ticket for org.fcrepo:
> https://issues.sonatype.org/browse/OSSRH-307
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
Chris Wilper updated FCREPO-825:
--------------------------------
Description:
The primary goal of this epic is to migrate Fedora's Maven artifacts completely to Sonatype and sync them to Maven Central, adhering to as much of the Sonatype Central Sync Requirements as possible. In particular, we aspire to have no library dependencies that are not hosted in Maven Central. We also want to take advantage of Sonatype's snapshot repository hosting option as an automatic part of our continuous integration builds that run at bamboo.duraspace.org.
For reference, here is the Sonatype OSS Maven Repository Usage Guide, which also includes a section on the latest Central sync requirements:
http://docs.sonatype.org/x/SQBl
...and here is the original Sonatype hosting ticket for org.fcrepo:
https://issues.sonatype.org/browse/OSSRH-307
was:
The goal is to move to Sonatype Maven hosting, so that
1) The Fedora build no longer depends on any DuraSpace repository.
2) The artifacts we build (both releases and snapshots) can be deployed to Sonatype.
A longer-term goal is to get our artifacts in line with central sync up requirements, so that we can publish future releases to central.
For reference, here is the Sonatype OSS Maven Repository Usage Guide, which also includes a section on the latest Central sync requirements:
http://docs.sonatype.org/x/SQBl
...and here is the original Sonatype hosting ticket for org.fcrepo:
https://issues.sonatype.org/browse/OSSRH-307
Priority: Major (was: Minor)
Rank: (was: 1460000000)
Fix Version/s: (was: Fedora 3.6)
Assignee: (was: Chris Wilper)
Issue Type: Epic (was: Story)
Summary: Complete Maven hosting migration to Sonatype with sync to Maven Central (was: Move to Sonaype with automated snapshots triggered by Bamboo)
> Complete Maven hosting migration to Sonatype with sync to Maven Central
> -----------------------------------------------------------------------
>
> Key: FCREPO-825
> URL: https://jira.duraspace.org/browse/FCREPO-825
> Project: Fedora Repository Project
> Issue Type: Epic
> Components: Fedora, java-client, Trippi
> Reporter: Chris Wilper
> Priority: Major
>
> The primary goal of this epic is to migrate Fedora's Maven artifacts completely to Sonatype and sync them to Maven Central, adhering to as much of the Sonatype Central Sync Requirements as possible. In particular, we aspire to have no library dependencies that are not hosted in Maven Central. We also want to take advantage of Sonatype's snapshot repository hosting option as an automatic part of our continuous integration builds that run at bamboo.duraspace.org.
> For reference, here is the Sonatype OSS Maven Repository Usage Guide, which also includes a section on the latest Central sync requirements:
> http://docs.sonatype.org/x/SQBl
> ...and here is the original Sonatype hosting ticket for org.fcrepo:
> https://issues.sonatype.org/browse/OSSRH-307
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
Chris Wilper updated FCREPO-825:
--------------------------------
Priority: Minor (was: Major)
> Complete Maven hosting migration to Sonatype with sync to Maven Central
> -----------------------------------------------------------------------
>
> Key: FCREPO-825
> URL: https://jira.duraspace.org/browse/FCREPO-825
> Project: Fedora Repository Project
> Issue Type: Epic
> Components: Fedora, java-client, Trippi
> Reporter: Chris Wilper
>
> The primary goal of this epic is to migrate Fedora's Maven artifacts completely to Sonatype and sync them to Maven Central, adhering to as much of the Sonatype Central Sync Requirements as possible. In particular, we aspire to have no library dependencies that are not hosted in Maven Central. We also want to take advantage of Sonatype's snapshot repository hosting option as an automatic part of our continuous integration builds that run at bamboo.duraspace.org.
> For reference, here is the Sonatype OSS Maven Repository Usage Guide, which also includes a section on the latest Central sync requirements:
> http://docs.sonatype.org/x/SQBl
> ...and here is the original Sonatype hosting ticket for org.fcrepo:
> https://issues.sonatype.org/browse/OSSRH-307
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
Chris Wilper reassigned FCREPO-825:
-----------------------------------
Assignee: Chris Wilper
> Complete Maven hosting migration to Sonatype with sync to Maven Central
> -----------------------------------------------------------------------
>
> Key: FCREPO-825
> URL: https://jira.duraspace.org/browse/FCREPO-825
> Project: Fedora Repository Project
> Issue Type: Epic
> Components: Fedora, java-client, Trippi
> Reporter: Chris Wilper
> Assignee: Chris Wilper
>
> The primary goal of this epic is to migrate Fedora's Maven artifacts completely to Sonatype and sync them to Maven Central, adhering to as much of the Sonatype Central Sync Requirements as possible. In particular, we aspire to have no library dependencies that are not hosted in Maven Central. We also want to take advantage of Sonatype's snapshot repository hosting option as an automatic part of our continuous integration builds that run at bamboo.duraspace.org.
> For reference, here is the Sonatype OSS Maven Repository Usage Guide, which also includes a section on the latest Central sync requirements:
> http://docs.sonatype.org/x/SQBl
> ...and here is the original Sonatype hosting ticket for org.fcrepo:
> https://issues.sonatype.org/browse/OSSRH-307
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa