[Building Sakai] Automatically signed applet in Samigo

[Daniel Merino]

Hi, Anthony.

We didn't have the certificate profile added to the Maven settings file, 
neither we activated the profile when deploying Samigo. Now it's working.

It's the 2.7.1 tag of Samigo. I paste my svn info:

[csie at csie-server sam]$ svn info
Path: .
URL: https://source.sakaiproject.org/svn/sam/tags/samigo-2.7.1
Repository Root: https://source.sakaiproject.org/svn
Repository UUID: 66ffb92e-73f9-0310-93c1-f5514f145a0a
Revision: 82923
Node Kind: directory
Schedule: normal
Last Changed Author: lydial at stanford.edu
Last Changed Rev: 81249
Last Changed Date: 2010-08-13 21:22:03 +0200 (vie, 13 ago 2010)

Regards.

Anthony Whyte escribió:
> The applet is signed automatically every time Samigo is released or the trunk snapshot is updated.
>
> What version of Samigo are you using that you encountered an unsigned applet jar?
>
> Anth
>
>
> On Apr 12, 2011, at 7:11 AM, Steve Swinsburg wrote:
>
>   
>> Hi Daniel,
>>
>> It is possible to automatically sign the jar at build time via the maven-jar plugin 'sign' goal. In fact the samigo-audio pom already does this but you need to activate the profile in the pom:
>>
>> mvn clean install -Pjarsign
>>
>> You may need to provide the properties for it, like the keystore location,alias and password. Check the POM.
>>
>> It's been a while since I've used this but IIRC the Sakai Foundation used to sign it/provide the cert. Are the artifacts in the repo not signed?
>>
>> cheers,
>> Steve
>>
>>
>>
>> On 12/04/2011, at 8:06 PM, Daniel Merino wrote:
>>
>>     
>>> Hi everybody.
>>>
>>> We have been getting complaints about the audio recorder applet which is 
>>> integrated inside Samigo. As it can be seen at 
>>> https://jira.sakaiproject.org/browse/SAK-5731 , if the applet is not 
>>> signed users must change their local JVM configuration in their 
>>> computers in order to use it, a little embarrasing change that can 
>>> discourage them to use this feature.
>>>
>>> I have signed the applet with a certificate and it works nice, but every 
>>> time we redeploy the sam project, the applet is rebuilded unsigned 
>>> again, so we must sign it once and another to have it enabled.
>>>
>>> I wonder if somebody has come across a solution to automatize this. As 
>>> the command to sign the applet could be different for each institution, 
>>> I suppose that it is not possible to give a general solution with Maven, 
>>> am I wrong?
>>>
>>> Thanks in advance.
>>> Best regards.
>>> -- 
>>> Daniel Merino
>>> daniel.merino at unavarra.es
>>> Gestor de teleformación - Centro Superior de Innovación Educativa.
>>> Tfno: 948-168489 - Universidad Pública de Navarra.
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>       
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>
>>
>>     
>
>   

-- 
Daniel Merino Echeverría
daniel.merino at unavarra.es
Gestor de teleformación - Centro Superior de Innovación Educativa.
Tfno: 948-168489 - Universidad Pública de Navarra.
--
Nuestras balas tienen bajos contenidos en plomo, ya que el plomo usado 
en las municiones puede dañar el medio ambiente y supone un riesgo para 
las personas. (BAE Systems)