Skip to:

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

Configure Samigo to use released audio jar for custom builds

Description

When someone is doing a custom build of Samigo (from the .x branch) very likely they will still want to use the samigo audio jar that's signed from the release, otherwise they will need to pay $300 a year for a java signing certificate.
http://www.thawte.com/code-signing/content-signing-certificates/sun-java/index.html

I'd recommend setting this jar as a fixed version, and only updating it when changes happen to the audio jar (which is very infrequent)

This generally would only be updated every 2 years (when we have to release new jars) or when major breaking changes happen (like with https://sakaiproject.atlassian.net/browse/SAM-1779#icft=SAM-1779)

Environment

None

Test Plan

None

Activity

Show:

Sam Ottenhoff November 13, 2013 at 2:25 PM

Java applet is no longer used in Sakai 10 for recording.

Neal Caidin November 13, 2013 at 2:23 PM

Can this be closed, or does it need more testing?

Matthew Jones September 12, 2013 at 10:23 AM

This is fixed. It's hardcoded to use the latest released signed version (2.9.3) which is good for 1 year. To develop against this jar, you need to use the profile samigo-audio or the profile jarsign to sign the jar.

Matthew Jones November 26, 2012 at 7:10 AM

Yea, that would be correct. However currently this fix isn't merged into anywhere. 2.9.x and trunk should both show a certificate warning. Only the released versions on the QA servers should be signed.

This is more of an issue for people doing custom builds off of 2.9.x or 2.8.x.

Neal Caidin November 26, 2012 at 6:47 AM

How can we test this? After a build, create a Quiz with an audio question and see if we get a certificate warning/error? If no error then this is fixed?

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created October 26, 2012 at 9:32 AM
Updated April 17, 2018 at 8:17 AM
Resolved September 12, 2013 at 10:23 AM

Flag notifications