>> Erik,
>>
>> Just to make sure I understand this correctly... As technically
>> subclass
>> is never generated if it already exists in the target location, is it
>> fair
>> to rephrase this as "'cgen' must allow a different destination folder
>> for
>> subclasses and superclasses"?
>
> That would work too. That would be handy in that new classes would get
> generated there, and then I'd add them to my version control.
>
> Erik
And this would be in line with cgen "generation gap pattern" approach
(http://www.research.ibm.com/designpatterns/pubs/gg.html - reference to
the pattern mysteriously disappeared from Cayenne docs :-)).
Andrus
This archive was generated by hypermail 2.0.0 : Wed Apr 27 2005 - 18:29:25 EDT