Issues with <frameworks>

From: Dov Rosenberg (drosenber..nquira.com)
Date: Sat Mar 21 2009 - 16:42:26 EDT

  • Next message: Chuck Hill: "Re: Issues with <frameworks>"

    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>

    Dov



    This archive was generated by hypermail 2.0.0 : Sat Mar 21 2009 - 16:43:51 EDT