Too late, it's already checked in :) But you can just choose not to
use it by not filling in an eogenerator path or eogenerator args on
your project. I personally find it to be really handy just in the
short time it has existed. As far as auto-running, I've never had
eogenerator cause problems for me with the code it generates. And it
was always the case that i would just manually run code generation
every time i made a change to the model, anyway. So at least for my
workflow, it only makes development quicker. But then I detest
having to use ant build files from inside of eclipse for anything
other than deployment, so I may be biased :)
On Sep 26, 2005, at 12:21 PM, Ian McDougall wrote:
> Personally, I don't believe the incremental builder should do any
> code generation. Plus, code generation from eomodeler has always
> been a manual process, and should probably continue to be so.
>
> It would be nice, however, to have a wizard that generates entity
> class pairs from the UI with the ability to specify/edit
> templates. At the very least it could generate an ant build file.
>
> _ _
> Ian
>
> On Sep 25, 2005, at 3:20 PM, Mike Schrag wrote:
>
>
>> So I'm toying with the idea of an incremental builder that calls
>> eogenerator when eomodels get updated ... My question is whether
>> people would rather have just a text field where they can put in
>> the commandline or should i automagically find all the prototype
>> models and call eogenerator on each of the eomodels in your
>> project? Or would people rather not have this at all?
>>
>> ms
>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Mon Sep 26 2005 - 12:30:19 EDT