Re: WOLips Development prefs

From: Chuck Hill (chil..lobal-village.net)
Date: Sun Feb 01 2009 - 14:22:07 EST

  • Next message: Lachlan Deck: "Re: WOLips Development prefs"

    On Feb 1, 2009, at 3:28 AM, Lachlan Deck wrote:

    > On 01/02/2009, at 8:44 PM, Anjo Krank wrote:
    >
    >> I don't like it.
    >
    > Well I'm looking for discussion about how to enhance wolips as a
    > tool in order to make things workable for those not using ant etc or
    > allowing wolips to just work with legacy projects... without adding
    > problems to existing projects.
    >
    > Certainly I'm not aiming to make things more difficult.

    The recent changes were an attempt to make it easier to use WO. The
    last several years of continuing problems were mostly the result of
    decisions made "in order to make things workable for those not using
    ant etc". It is case where more choice seems bad (IMO).

    >> It's yet another indirection that will eventually break for someone
    >> who in turn complains to the maling lists, it will make build
    >> scripts more complicated and provides no real gain. In fact, we
    >> have build scripts that actually use these variable and it has been
    >> a nuisance.
    >
    > Five lines and adjusting current hard-codings to use the property
    > values doesn't sound complicated to me.
    > <property file="build.properties"/>
    > <property name="projectSourcesFolder" value="Sources"/>
    > <property name="projectResourcesFolder" value="Resources"/>
    > <property name="projectComponentsFolder" value="Components"/>
    > <property name="projectWebServerResourcesFolder"
    > value="WebServerResources"/>
    >
    > You can maintain current sympathy levels for those who stray from
    > your defaults. ;-)
    >
    >>> The motives for me in doing this is primarily to fix the problem
    >>> where wolips won't create components java classes in the right dir
    >>> (for maven projects).
    >>
    >> Then by all means fix the "maven project" to recognize the "correct
    >> folder" or live with the consequences.
    >
    > The lack of recognition of the correct folder lies with wolips imo.
    > Clearly you don't agree. I don't agree with limiting wolips to such
    > a fundamental choice as a one-layout-fits-all-hard-coding. That's
    > what preferences are for. Clearly the above is not any plethora of
    > preferences.

    Again, preferences and freedom are what caused the problems. This
    looks to me like a case where convention has far more value than
    configuration.

    > There's a more dirty work around I suppose... fixing the component
    > creation wizard to put the java source in the right dir (e.g.,
    > allowing you to adjust the selected source dir) but this hard-coding
    > of the project layout just seems fundamentally limiting for wolips
    > as a tool and if the choice is exposed in one place like this it
    > ought to be configured for the project.
    >
    > with regards,
    > --
    >
    > Lachlan Deck

    Chuck

    -- 
    Chuck Hill             Senior Consultant / VP Development
    

    Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects



    This archive was generated by hypermail 2.0.0 : Sun Feb 01 2009 - 14:22:46 EST