Changes between Version 3 and Version 4 of MapGuideRfc111

Timestamp:

01/10/12 21:23:42 (13 years ago)

Author:

jng

Comment:

--

MapGuideRfc111

@@ -43 +43 @@
 Update installer build to include subversion attributes
 
-Check in a compiled version of fusion into the mapguide svn repo 
+Check in a compiled version of fusion into the mapguide svn repo. A separate build_fusion.bat will do the following:
 
-This will be an optional install feature, with a dedicated page in the windows installer
+ 1. Build fusion via ant
+ 2. ant deploy into a svn-tracked fusion_build directory under Oem
+ 3. svn commit any changes under the fusion_build directory
+ 4. Copy fusion_build to the staging area as part of installer preparations with svn metadata intact
 
 == Implications ==
@@ -55 +58 @@
 full builds to be created only to update a few text files
 
+This RFC imposes some constraints on the build infrastructure that will produce the MapGuide installer.
+
+ 1. Due to working copy metadata changes [introduced with Subversion 1.7 http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng], the build machine that will produce the MGOS installer needs to use Subversion 1.6 or older. This way, WC compatibility is retained with SVN 1.6 or older clients. For SVN 1.7 or newer clients, they can detect that these .svn directories are older versions and will direct the user to upgrade said working copies to the 1.7 format.
+
+ 2. The installer build must be performed against a SVN working copy (<= 1.6) and not an ***export*** of an SVN repo/working copy. Exported copies lose all svn metadata that this RFC aims to preserve.
+
 == Test Plan ==
 
-N/A beyond existing test procedures for builds
+Verify the affected viewer files are under svn control when installed via the installer. An easy way to check is having TortoiseSVN installed. Files/Directories under svn control will have icon overlays in Windows Explorer.
 
 == Funding / Resources ==