On Thu, Mar 30, 2017 at 2:58 PM, Siemen Baader <siemenbaader@gmail.com> wrote:
Below is a fileout of 'ConfigurationOfPharoJS'. I download new releases of PharoJS as they become available. Recently I found a regression - a method 'PjApplication class >> playgroundWithoutLaunch' did not work any more. What I wanted to do was to revert the whole project to an earlier version until the method worked again - then look for the code that has been changed between releases and find the bug.
In practice, even the earliest version (version 1.0 - method #version10) did have the bug and I could not roll back the project to earlier release states because there is no metadate for them. But I'd still like to learn how to do it, so let's just say I want to compare version 1.2 and 1.3:
version12: spec <version: '1.2' imports: #('0.1-baseline' )>
version13: spec <version: '1.3' imports: #('0.2-baseline' )>
I hope this makes sense. Thanks for helping me understand!
You can only directly diff the Configurations themselves. I fairly sure you can't auto-diff the packages loaded by each configuration. This is a missing feature. It would be nice to have something like the merge-diff, but there are probably other priorities. Maybe the new git workflow will open some possibilities?? cheers -ben