[mapguide-internals] Mapguide -> FDO dependencies?

[Jason Birch]

Using externals makes a lot of sense.  It does mean that we will have to be rigorous in ensuring that our release tags have their external set to the revision/tag of FDO used for the build.  Same applies to the existing CS-Map and Fusion externals though, so no change in procedure there.

There may be some issues with the FDO bin/lib/etc paths expected by the MapGuide solutions, but these could be adjusted.

We may also need to update the mapguide build.bat's "install" action to account for this change.

Jason

-----Original Message-----
From: Tom Fukushima
Sent: April-06-09 11:47 AM
Subject: RE: [mapguide-internals] Mapguide -> FDO dependencies?

I like this.  Automating it will keep it from getting out of date in case it is updated in one place but not the other.  Maybe we should use a svn:externals tag for this like we do for CsMap and Fusion. Other than the increased download, does anyone see a problem with adding a svn:externals property for the MgDev/Oem/FDO directory?

Actually, if we use the svn:externals tag, then the original problem goes away because there is no need to figure out which version of FDO to get anymore.