Oh, yeah...

The other thing that this does is to add a classpathRef attribute on the <macrodef>s for building JPFs, controls, and XSDs. This requires that the calling build files pass in a classpath that represents the resources available to a specific application.

See the petstoreWeb/WEB-INF/src/build-dist.xml file for a specific example, but in general, it might look like this:

::::: fooWebBuild.xml
        <path id="webapp.classpath">
            <pathelement location="${webapp.dir}/WEB-INF/classes"/>
            <fileset dir="${webapp.dir}/WEB-INF/lib">
                <include name="*.jar"/>
            </fileset>
        </path>

        <build-pageflows
                     sourceDir="${webapp.dir}"
                     destdir="${webapp.dir}/WEB-INF/classes"
                     tmpdir="${webapp.dir}/WEB-INF/${tmp.sourcegen.dir}"
                     classpathRef="webapp.classpath"/>
:::::

For anyone who has existing applications, the ant/buildWebapp.xml file is now gone from the distribution and Beehive-enabled webapps are now responsible for defining their own classpaths and building the Beehive source artifacts explicitly. The one-size-fits-all buildWebapp.xml "build" target wasn't going to work in the long run. :)

If you need to migrate an app to this new Ant tools structure, take a look at:

  samples/netui-blank/WEB-INF/src/build.xml

in a Beehive distribution.

  Let me know if you've got questions.

Eddie


[EMAIL PROTECTED] wrote:
Author: ekoneil
Date: Sat Mar 12 13:52:52 2005
New Revision: 157286

URL: http://svn.apache.org/viewcvs?view=rev&rev=157286
Log:
Rename buildWebappCore.xml to beehive-tools.xml.  This adds a .properties file 
for the distribution that defines various resources needed to build a webapp 
including the JSP and Servlet APIs.

Removes some unused shell scripts and an old beehive.properties file that 
should have been deleted a while ago.

The NetUI-enabled webapps in the distribution now are structured as:

  WEB-INF/src/
              build.xml
              build.properties

where build.properties defines beehive.home. Then, the build.xml file simply imports the beehive-imports.xml file to obtain the <path>s defined there and beehive-tools.xml to define the tools used to build JPFs, controls, and XSDs.

BB: self
DRT: Beehive pass
BVT: NetUI pass
Tests: distribution tests pass

Reply via email to