Has there has been any progress on official GIT support for SAS DI Studio since two years ago? I had a look at creating a GIT plugin using JGIT to hook into your plugin interface. However after reading through your documentation and examining your source code for the SVN/CVS implemetation. I can see possible problems with the file format for the metadata.. The current persistence/export file format you are using for your source control, looks to be the standard spk export file format. Which is a compressed binary archive file, holding subfiles(xml, properties, ...) describing the metadata exported. Merging and version difference analysis is difficult with binary files. The xml subfiles (e.g. TransportMetadata.xml) held in the spk are also single lined, instead of pretty print formatted. Sounds like a minor thing, but it makes it really hard to make sense of things with standard diff tools. Are there any plans by SAS to define new user readable xml export file formats instead of binary blobs for your SAS DI metadata?? Which makes it practical for your users to use standard source control tools on them. I have seen other vendors like Oracle do so for their metadata tools.
... View more