Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Release RSF Version 10.0 for Sakai 10 release

Description

Before Sakai 10 can be released, we have to release RSF version 0.8.0 as a library and set up the dependencies for that. It's currently binding against snapshot which had some issues and merges missing. I'd probably reorganize the git branches as well and make the master the 0.8 branch and move out the 0.7 to a branch.

This is going to take a little work as there are a lot of RSF projects so I'm creating it as a separate task and it will be a blocker.

Ideally we will also get RSF onto sonatype/maven central rather than the Sakai repo when this happens.

Environment

None

Test Plan

None

is related to

relates to

Activity

Show:

Matthew Jones July 2, 2014 at 1:17 PM

Yes, RSF 0.8.0 was changed to 10.0 and released.

Neal Caidin July 2, 2014 at 12:22 PM

This is resolved with the release of Sakai 10.0, correct?

Hudson CI Server May 8, 2014 at 7:07 PM

Integrated in sakai-trunk-java-1.7 #225 (See http://builds.sakaiproject.org:8080/job/sakai-trunk-java-1.7/225/)

Result = UNSTABLE

Matthew Buckett May 8, 2014 at 11:55 AM

Yep, it fixed it. Maven does try to locate the missing artifact but only tries the repository into which it was previously deployed (source.sakaiproject.org). As Matt suggests the -U option forces maven to check for the artifact in ALL repositories and so finds it on oss.sonatype.org

Matthew Jones May 8, 2014 at 11:36 AM

Yeah, try again, I changed it before I had the new versions correctly deployed. I didn't realize that the transitive dependencies of
SakaiRSFComponents->RSFComponents

If maven complains about wanting to wait for a refresh you can build with the -U option, though it should be okay.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created March 21, 2014 at 9:28 AM
Updated October 6, 2014 at 12:16 PM
Resolved July 2, 2014 at 1:16 PM

Flag notifications