Good point, Laurel. I wasn't aware that my changes broke compatibility with older curnits. The building code is independent of the produced curnit. I suppose the breaker was fixing the typo in the "reponses" property to "responses". Sorry for not realizing that would break old curnits.
It certainly is important to know whether a code edit breaks old curnits. That would make an excellent unit test. JIRA-TASK Unit test for curnit backwards compatibility //Assignee:turadg Store in the src/test/resources a curnit made with a previous build and have a unit test that unmarshalls and validates it. That way Continuum can catch when such an edit happens. Developers can then decide whether it's a bug or improvement. If it's a bug, fix it. If it's an improvement, update the "old" curnit and notify SAIL-Dev. fwiw, I write the above in that syntax so my discussion-processor tool can find it. I hope to have that working next week for us to use. -Turadg On 1/11/07, laurel <[EMAIL PROTECTED]> wrote: > > Tony tells me that your email above implies that my curnits need to be > rebuilt in order to use with the PAR. I have spent the last couple of > days trying to figure out why my curnits wouldn't open in the authoring > tool. If changes are made that do require curnits to be rebuilt, can > you please specifically say that next time, since I really didn't know > that is what I needed to do until Tony let me know today. > > Thanks! > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
