Re: Do we really need an option to enable/disable the eogenerator? n/t

From: Mike Schrag (mschra..dimension.com)
Date: Wed Oct 11 2006 - 08:17:41 EDT

  • Next message: Guido Neitzer: "Re: Re: Do we really need an option to enable/disable the eogenerator? n/t"

    How about we default it to true, but it only runs in the builder if
    you have an eogenerator path set. That might solve the problem?

    ms

    On Oct 11, 2006, at 8:01 AM, Ulrich Köster wrote:

    > We have to support my laziness. ;-) Do I have to tell people that
    > they have to enable it? Again and again and again.
    >
    >
    > Uli
    >
    > Am 11.10.2006 um 13:37 schrieb Mike Schrag:
    >
    >> Actually it would change things. If the option was removed, then
    >> eogenerator would ALWAYS execute when an eomodel changes. Because
    >> EOGenerating isn't always actually necessary when the model
    >> changes, there are times it runs when it doesn't really have to.
    >> This shouldn't break things, but you do take a performance hit as
    >> it regenerates and rebuilds java files.
    >>
    >> Is there a problem that it needs to be removed to support?
    >>
    >> ms
    >>
    >> On Oct 11, 2006, at 4:23 AM, Ulrich Köster wrote:
    >>
    >>> The builder requires one or more eogen files. Without them it
    >>> does nothing. Removing the option won't change anything for you.
    >>>
    >>> Uli
    >>>
    >>> Am 11.10.2006 um 10:13 schrieb Guido Neitzer:
    >>>
    >>>> Yes please. I have a very slow Powerbook and I don't like Eclipse /
    >>>> WOLips deciding to build something not necessary when it just
    >>>> thinks
    >>>> it's useful.
    >>>>
    >>>> It might be on by default, but I prefer to have the option to
    >>>> disable
    >>>> automatic builds as much as I can.
    >>>>
    >>>> cug
    >>>
    >>
    >



    This archive was generated by hypermail 2.0.0 : Wed Oct 11 2006 - 08:17:50 EDT