Changes between Version 2 and Version 3 of MapGuideRfc165
- Timestamp:
- 02/20/18 02:40:20 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MapGuideRfc165
v2 v3 28 28 * Apache: 2.4.29 29 29 * PHP: 5.6.33 30 * Tomcat: 7.0.8 230 * Tomcat: 7.0.85 31 31 32 32 == Motivation == … … 40 40 Upgrade PHP to 5.6.33. Windows binaries will be sourced from windows.php.net. We are staying on the 5.6.x series because it is not possible to upgrade to the current PHP 7.x series as our copy of SWIG cannot generate PHP7-compatible language bindings for the MapGuide API. 41 41 42 Upgrade Tomcat to 7.0.8 2. We are staying on the 7.x series so that our Java installation requirements do not have to change for this release of MapGuide.42 Upgrade Tomcat to 7.0.85. We are staying on the 7.x series so that our Java installation requirements do not have to change for this release of MapGuide. 43 43 44 44 As the 3.1 release has been using the same series of Apache/PHP/Tomcat, the 3.1 branch will also be recipients of this component upgrade. 45 45 46 Due to the adoption of [wiki:MapGuideRfc166], we will only keep 64-bit Apache/PHP/Tomcat binary artifacts for the windows installer project for 3.3, but retain 32 and 64-bit copies for the 3.1 windows installer.46 Due to the adoption of [wiki:MapGuideRfc166], we will only keep 64-bit Apache/PHP/Tomcat binary artifacts for the windows installer project for trunk (that the 3.3 release will branch from when ready), but retain 32 and 64-bit copies for the windows installer on the 3.1 branch. 47 47 48 48 == Implications ==