SPADS update procedure for new Spring version: Difference between revisions
From Spring
Jump to navigationJump to search
Created page with "This document describes how to update SPADS to use a new Spring version. You need to replace <spadsRelease> by your actual SPADS release (stable, testing, unstable or contrib)..." |
m Add category |
||
| Line 15: | Line 15: | ||
*if it doesn't work, you may need to update SPADS manually with: | *if it doesn't work, you may need to update SPADS manually with: | ||
perl update.pl <spadsRelease> -A | perl update.pl <spadsRelease> -A | ||
[[Category:Autohosts]] | |||
Revision as of 19:03, 10 November 2013
This document describes how to update SPADS to use a new Spring version. You need to replace <spadsRelease> by your actual SPADS release (stable, testing, unstable or contrib) in the commands listed below.
Linux
- update the "springServer" and "springDataDir" paths in spads.conf for new Spring version if needed
- update your SPADS installer script so that it contains the latest changes which could be required to recompile the unitsync interface from latest Spring sources:
./update.pl <spadsRelease> -a
- launch the PerlUnitSync module generation:
./spadsInstaller.pl -g
Windows
- update the "springDataDir" path in spads.conf for new Spring version if needed
- restart SPADS
- if it doesn't work, you may need to update SPADS manually with:
perl update.pl <spadsRelease> -A
