dueling mogenerators

[irons]

My two computers' copies of mogenerator perpetually overwrite one another's machine files. This sounds like the definition of user error, and it presumably is, but I've ruled out the obvious explanations so far.

mogenerator 1.15 is installed on both machines, via the final package installer. 'md5 /usr/bin/mogenerator' returns the same hash on both machines. The projects live at the same path, and I invoke mogenerator by hand, using the same command. The two machines are a Mac Pro and a Macbook Pro, each with 10.6.1 and Xcode 3.2.1, sharing an up-to-date Xcode project through svn.

The machine files generated by 1.15 on the Mac Pro are identical (against unchanged entities) to those I first committed using 1.13, when I initially mogeneratified this project in September.

'locate' indicates no other copies of mogenerator on the Mac Pro, and in any case I'm now using the full /usr/bin/ path in my invocation. MD5 evidence aside, there was no change in behavior after I downloaded and reinstalled a fresh copy of 1.15 this morning.

The differences between the two sets of output span the newInManagedObjectContext/insertInManagedObjectContext change, so I effectively can't use mogenerator on the Mac Pro until I sort out the problem.

I thought I'd realize what I was doing wrong before I finished writing this out, but you're reading it, so that didn't work. Any suggestions would be warmly appreciated.

[rentzsch]

Sounds like you have ≤1.13-era templates on one machine and ≥1.14-era templates on another machine. I bet cd /Library/Application\ Support/mogenerator && cksum * yields different answers on both machines.

Solution: re-run the 1.15 installer on the machine that's generating newInManagedObjectContext code. If that doesn't work, please file a bug against the installer, delete Library/Application Support/mogenerator and re-run the installer again.

[irons]

Thanks very much. Unfortunately, the quartet of templates also match; both machine.m.motemplate files contain insertInManagedObjectContext language, and they all share the same Nov 2 timestamp.

I re-ran the 1.15 installer this morning, with no change in behavior.

[rentzsch]

1. Is there a ~/Application Support/mogenerator folder that's overriding the system-wide one?
2. Have you tried explicitly specifying --template-path?

[irons]

Thanks for the help. ~/Application Support/mogenerator on the Mac Pro had the outdated templates, datestamped Apr 10. After removing that folder, all is sweetness and light.

Is there any reason to think an older installer created the user-specific folder? I don't recollect having set it up myself, though it's possible. There's no user-specific folder on the laptop, which has been behaving correctly throughout.

[rentzsch]

I don't think I ever installed into user's directory, but I'd need to read through the commit logs to be sure.