Re: Wonder builds, frameworks etc.

From: Greg Brown (gsbrow..mich.edu)
Date: Fri Mar 20 2009 - 11:58:57 EDT

  • Next message: Ricardo J. Parada: "Re: Wonder builds, frameworks etc."

    On Mar 20, 2009, at 11:46 AM, Ricardo J. Parada wrote:

    > I think it depends on what version of WOLips you are using.
    >
    > I know that the latest and greatest this information is kept in:
    >
    > ~/Library/Application Support/WOLips/wolips.properties
    >
    > Notice it's called wolips.properties.
    >
    > It looks like you are using WebObjects 5.2.2. What Eclipse/WOLips
    > version are you using?
    >
    >
    >
    > On Mar 20, 2009, at 11:09 AM, Greg Brown wrote:
    >
    >> Just a few questions:
    >>
    >> 1. Are the instructions in the BUILD.txt file correct? So I
    >> should have a ~/Library/wobuild.properties and a ~/Library/
    >> Application Support/wobuild.properties, each with different
    >> parameters?
    >>

    Sorry, I do have a ~/Library/Application Support/wolips.properties
    and the ~/Library/wobuid.properties.

    >>> . A wobuild.properties file should be placed in, on Mac OS X, the
    >>> ~/Library directory.
    >>> On Windows, this should go into a Library folder in the
    >>> directory pointed to
    >>> by the 'user.home' Java system property. Usually, this may be at
    >>> C:\Documents and Settings\<user name>\Library.
    >>>
    >>> An example of this file is:
    >>>
    >>> ==== START wobuild.properties ====
    >>>
    >>> wo.woroot=/
    >>> wo.wosystemroot=/System
    >>> wo.wolocalroot=/
    >>>
    >>> ==== END wobuild.properties ====
    >>>
    >>> These may, or may not, be necessary for some functionality:
    >>>
    >>> ==== START wobuild.properties, perhaps ====
    >>>
    >>> wo.dir.root=/
    >>> wo.dir.user.home.library.frameworks=/User/yourname/Library/
    >>> Frameworks
    >>> wo.dir.local=/
    >>> wo.dir.library=/System/Library
    >>> wo.dir.user.home.library=/User/yourname/Library
    >>> wo.dir.local.library=/Library
    >>> wo.dir.library.frameworks=/System/Library/Frameworks
    >>> wo.dir.local.library.frameworks=/Library/Frameworks
    >>> wo.dir.system=/System
    >>>
    >>> ==== END wobuild.properties, perhaps ====
    >>>
    >>
    >> 2. What about having one wobuild.properties file? Could/Should
    >> they be merged? This could be a little confusing; having one
    >> wobuild.properties file would be less confusing.
    >>
    >> If I do an ant build, then I get things installed in the following
    >> 4 places:
    >>
    >> ~/Roots/
    >> /Library/Frameworks/
    >> /Library/WebServer/Documents/WebObjects/Frameworks/
    >> /Library/WebObjects/lib/
    >>
    >> Wow, that's a lot of places!
    >>
    >> 3. ~/Roots/ - Would Wonderworkspace or Objectstyleworkspace be a
    >> better name? Something a bit more descriptive than what is in
    >> there. Is there a reason the build products are not in the same
    >> tree as the Wonder sources? wouldn't a "build" or "target" or
    >> "bin" folder in the same tree be better?
    >>
    >> /Library/Frameworks/
    >> /Library/WebServer/Documents/WebObjects/Frameworks/ > These are
    >> for split installs, but
    >>
    >> 4. /Library/WebObjects/lib/ >> Is this needed? I see from 5.2.2:
    >>
    >> Nowwhenyoucreateaservlet/
    >> J2EEcontainerapplicationyoucanchoosetheTrueWARoption. Tobuilda
    >> TrueWARservlet, all ofyourframeworksmustbeintheNSJarBundleformat,
    >> andlocatedinthe
    >> /Library/WebObjects/lib/directory. WhenyouchoosetheTrueWARoption,
    >> all yourapplication.....
    >>
    >> So that is for xcode WARs? do we still need that?
    >>
    >> And I assume if one has different versions of a framework or jar
    >> in one of these 4 places they have fun finding it.
    >>
    >>
    >> Greg Brown
    >> gsbrow..mich.edu
    >>
    >>
    >>
    >>
    >> Greg Brown
    >> gsbrow..mich.edu
    >>
    >>
    >>
    >

    Greg Brown
    gsbrow..mich.edu



    This archive was generated by hypermail 2.0.0 : Fri Mar 20 2009 - 12:00:00 EDT