1 | For MeV to work as a Java Webstart application, the JAR |
---|
2 | files in the ./resources/jar must be signed. The currently |
---|
3 | checked in JAR files have already been signed, so there is |
---|
4 | no need to do this again unless MeV itself needs to be |
---|
5 | updated. In that case, the new JAR files need to be signed. |
---|
6 | Since this is a somewhat complex task, we have tried to make |
---|
7 | easier. |
---|
8 | |
---|
9 | Follow this procedure: |
---|
10 | |
---|
11 | 1. Delete all the existing JAR files in the ./resources/jar |
---|
12 | directory. |
---|
13 | 2. Copy all JAR files from the MeV distribution into the |
---|
14 | ./resources/jar directory |
---|
15 | 3. Run 'ant signjars' |
---|
16 | 4. Commit the changes to the subversion repository. |
---|
17 | |
---|
18 | -------------------------------------------------------- |
---|
19 | Note! |
---|
20 | |
---|
21 | JAR files that have already been signed by another |
---|
22 | authority should not be re-signed. This needs to be specified |
---|
23 | as an exclustion in build.xml. Locate the <fileset> tag |
---|
24 | inside the <target name="signjars"> target and add the |
---|
25 | exceptions to the "excludes" attribute. |
---|
26 | |
---|
27 | ---------------------------------------------------------- |
---|
28 | Note! |
---|
29 | |
---|
30 | The mev-base.key is the self-signed certificate that we have |
---|
31 | used to sign the JAR files. It has the following properties: |
---|
32 | |
---|
33 | Alias: mev-base |
---|
34 | Password: mev-base |
---|
35 | Name: BASE Development team |
---|
36 | Organizational unit: BASE Development team |
---|
37 | Organization: Lund University |
---|
38 | City: Lund |
---|
39 | State: Sweden |
---|
40 | Country code: SE |
---|
41 | |
---|
42 | To re-generate the keystore execute the following command: |
---|
43 | |
---|
44 | keytool -genkey -alias mev-base -keypass mev-base -keystore mev-base.key |
---|
45 | --------------------------------------------------------------- |
---|
46 | |
---|