Re: no..ERSION@ in woapp(52) template

From: Peter Pritchard (pjpritc..ac.com)
Date: Fri Nov 09 2007 - 13:44:34 EST

  • Next message: PJ Pritchard (JIRA): "[OS-JIRA] Created: (WOL-635) the woapp template for creating the Info.plist file is missing the..ERSION@ value for the CFBundleShortVersionString key"

    the template should have..ERSION@ in it ... the final Info.plist
    should have whatever I pass to the <woapplication version="">
    attribute ... which happens automatically in the AppFormat.java class
    (or should if it was there) ... FrameworkFormat does the same as
    well ... for the <woframework version=""> attribute ... (see the
    woframework/Info.plist template ... the CFBundleShortVersionString
    <key>)

    I have actually subclassed the <woapplication> and <woframework>
    tasks, but I call setVersion() ... which does (almost) the same
    thing ...

    ERXProperties uses this in its methods ... versionStringForApplication
    () and versionStringForFrameworkNamed() ...

    and the default exception log (using ERXApplication) lists all
    version numbers for all loaded bundles ...

    - PJ

    BTW >>> I will add it as a bug ... thanks ...

    On Nov 9, 2007, at 1:31 PM, Mike Schrag wrote:

    > So you're saying the final Info.plist needs..ERSION@ as the value,
    > or the template should have..ERSION@ in it? Also, please log a
    > bug for this ...
    >
    > ms
    >
    > On Nov 9, 2007, at 1:14 PM, Peter Pritchard wrote:
    >
    >> Hey guys,
    >>
    >> I found a bug (feature) in the WOProject build process (template
    >> to be more accurate) ...
    >>
    >> While in woframework template for Info.plist has..ERSION@ for the
    >> key CFBundleShortVersionString, woapp(52) does not.
    >>
    >> I hacked my copy of woproject.jar to use it, but I figured that
    >> someone else might waste a day debugging around the omission like
    >> I did ...
    >>
    >>
    >> I have been working on an svn:externals-based framework
    >> dependency, which uses <woapplication> and <woframework> as a
    >> starting point ... (I added embedded webserverresources, nested
    >> frameworks, and custom packaging ... so that I can have links
    >> other than /WebObjects/) ... and added some Scp task stuff to
    >> handle remote installation depending on the build type (local)
    >> (staging)(production) ... anyway ...
    >>
    >>
    >> The versioning aspect is of NSBundle's is of extreme importance to
    >> me in this respect ... because all the other frameworks store
    >> their version info there as well ...
    >
    >



    This archive was generated by hypermail 2.0.0 : Fri Nov 09 2007 - 13:52:58 EST