Re: Converting Frameworks into path-like structures in ant

From: Mike Schrag (mschra..dimension.com)
Date: Tue Oct 11 2005 - 09:17:51 EDT

  • Next message: Mike Schrag: "Re: Converting Frameworks into path-like structures in ant"

    Try:

                                     <fileset dir="$
    {wo.dir.user.home.library.frameworks}" includesfile = "woproject/
    ant.frameworks.user.home">
                                             <include name = "**/*.jar"/>
                                     </fileset>
                                     <fileset dir="${wo.wolocalroot}"
    includesfile = "woproject/ant.frameworks.wo.wolocalroot">
                                             <include name = "**/*.jar"/>
                                     </fileset>
                                     <fileset dir="${wo.wosystemroot}"
    includesfile = "woproject/ant.frameworks.wo.wosystemroot">
                                             <include name = "**/*.jar"/>
                                     </fileset>
                                     <fileset dir = "yourotherfolder">
                                             <include name="**/*.jar"/>
                                     </fileset>

    On Oct 11, 2005, at 9:12 AM, Bill Michell wrote:

    > I’m trying to add unit tests to my ant automated build scripts.
    >
    > The unit testing framework provides its own custom ant task, which
    > expects to be told the runtime classpath for the unit tests using a
    > path-like structure.
    >
    > Obviously, the task knows nothing about the <frameworks> element.
    >
    >
    > Superficially, the following seems to work:
    > <classpath>
    > <fileset dir="${wo.wosystemroot}/Library/Frameworks">
    > <include name="**/*.jar" />
    > <include name="**/*.zip" />
    > </fileset>
    > <fileset dir="${wo.wolocalroot}/Library/Frameworks">
    > <include name="**/*.jar" />
    > <include name="**/*.zip" />
    > </fileset>
    > <fileset dir="${dest.dir}">
    > <include name="**/*.jar" />
    > <include name="**/*.zip" />
    > </fileset>
    > </classpath>
    >
    > Unfortunately, I then hit a problem with the SecurityManager when
    > referring to certain classes in JavaFoundation.framework, notably
    > NSBundle.
    >
    > There also seems to be a version of NSBundle in
    > Foundation.framework, and incompatible signatures mean the test
    > simply won't execute; the java runtime aborts it with a
    > SecurityException.
    >
    > Obviously, traversing such large directory structures also takes
    > significant time.
    >
    > So my question is how best I can convert the dependencies expressed
    > in the woproject/ant.frameworks.wo.wosystemroot into a path-like
    > structure for my testing task to use.
    >
    > I notice that the wocompile task actually goes so far as to
    > subclass the javac task in order to add this framework classpath
    > expansion. Is there some simpler way for me to achieve my goal?
    >
    >
    >
    > --
    > Bill Michell
    > Development Team Leader, Broadcast Platforms, BBC News Interactive.
    > Work: 020 8 752 6850
    > Room 1468, BBC White City, Wood Lane, London. W12 7TS
    > mailto:Bill.Michel..bc.co.uk (Work)
    > mailto:bil..ics.org.uk (Home)
    > mailto:billm..range.net (Mobile)
    >
    >
    >
    > http://www.bbc.co.uk/
    >
    > This e-mail (and any attachments) is confidential and may contain
    > personal views which are not the views of the BBC unless specifically
    > stated.
    > If you have received it in error, please delete it from your system.
    > Do not use, copy or disclose the information in any way nor act in
    > reliance on it and notify the sender immediately. Please note that the
    > BBC monitors e-mails sent or received.
    > Further communication will signify your consent to this.
    >



    This archive was generated by hypermail 2.0.0 : Tue Oct 11 2005 - 09:18:24 EDT