Forums

For those interested in an update on this, the work is currently parked.

What could spring it back into life is an enhancement to the Jade product where a new type of file format is provided which does the job that scm and ddb files currently do. The ideal would be a readable/editable format which allowed for easy compares & merge of code and that largely ignored environmental info.

As per the demo it’s possible to roll our own format, but I’d just be concerned with the maintenance overhead and undocumented edge cases that may leave it unfit for commercial use.

Hi All,

One of the cohorts John referred to in an earlier post here,

I've now converted my pet project for this to an open-source project, aptly called jade-git (borrowed for John's original video).

If you'd like to jump to the good bit, start with the latest project blog post which includes a link to a demo video

Cheers,
Kevin

Interesting, how does it handle schema changes? Or is it source code only? (forgive me if that's explained in a readme somewhere that I haven't read)

By schema changes, I take it you're asking how are re-org's are handled without losing data due to rename's, etc ?

The aim is to make this work for environments with data in them, not just source code.

When retrieving/loading changes in from the git repo, it goes through a build process which compares one version to another. Using which, it constructs partial schema files, along with determining the JCF commands required for any renames, etc, that need to be performed before schema files are loaded and re-org subsequently performed.

Nice