Re: Issues with <frameworks>

From: Dov Rosenberg (drosenber..nquira.com)
Date: Sun Mar 22 2009 - 22:22:01 EDT

  • Next message: Mike Schrag: "change logs"

    The <frameworks> task still does not seem to be functional. I am not exactly
    sure what it is trying to even do. It doesn't add anything to the classpath
    as far as I can tell.

    I had to get around my problems by adding a <classpath> task inside my
    <wocompile> task

    Dov Rosenberg

    On 3/21/09 8:28 PM, "Chuck Hill" <chil..lobal-village.net> wrote:

    >
    > On Mar 21, 2009, at 1:42 PM, Dov Rosenberg wrote:
    >
    >> Not sure if I am doing something wrong but I am updating the
    >> build.xml for our projects that had been using an older version of
    >> woproject.jar. It seems that the <frameworks> tag is really broken.
    >>
    >> If I create a brand new empty Project Wonder framework and use the
    >> generated build.xml as a template, the <wocompile> tag has an
    >> embedded attribute in it that looks like :
    >>
    >> <frameworks root="ProjectLocal" embed="false" eclipse="true" /
    >>> <frameworks root="External" embed="false" eclipse="true" />
    >> <frameworks root="Local" embed="false" eclipse="true" />
    >> <frameworks root="User" embed="false" eclipse="true" />
    >> <frameworks root="System" embed="false" eclipse="true" />
    >> <frameworks root="Network" embed="false" eclipse="true" />
    >>
    >> It seems that no matter what values I end up configuring in the
    >> woliips.properties the frameworks being referenced do not get added
    >> to the compile time classpath. In addition, the older version of the
    >> build.xml is now broken and doesnšt work. This is a sample from my
    >> old build.xml that used to work. Now it throws errors because the
    >> root=˛Webobjects˛ attribute is not being recognized
    >>
    >> <frameworks root="WebObjects">
    >> <include name="JavaWebObjects.framework"/>
    >> <include name="JavaFoundation.framework"/>
    >> <include name="JavaXML.framework"/>
    >> <include name="JavaEOAccess.framework"/>
    >> <include name="JavaEOControl.framework"/>
    >> <include name="ERJars.framework"/>
    >> <include name="ERExtensions.framework"/>
    >> <include name="ERJGroupsSynchronizer.framework"/>
    >> </frameworks>
    >
    >
    >
    > Here is how I have been using frameworks and wopath for a while now:
    >
    > <!-- Non-source Classpath for project-->
    > <wopath id="project.classpath">
    > <frameworks root="User" eclipse="true" />
    > <frameworks root="Local" eclipse="true" />
    > <frameworks root="System" eclipse="true" />
    > <path refid="cadre.jars" />
    >
    >
    > <!-- Distribution WOProject compilation -->
    > <target name="compile" depends="init.all">
    > <wocompile destdir="bin"
    > debug="${wocompile.debug.flag}"
    > optimize="${wocompile.optimize.flag}"
    > deprecation="on">
    > <src refid="${project.source.path}"/>
    > <classpath refid="project.classpath"/>
    > </wocompile>
    > </target>
    >
    >
    > Chuck
    >



    This archive was generated by hypermail 2.0.0 : Sun Mar 22 2009 - 22:23:17 EDT