forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [issues] Closed: (FOR-152) documentation: integrating forrest tasks with a project build process
Date Thu, 01 Jan 1970 00:00:00 GMT

   The following issue has been closed.

   Resolver: Dave Brondsema
       Date: Wed, 26 May 2004 4:18 PM

replaced the antproxy section of your-project with this documentation
View the issue:

Here is an overview of the issue:
        Key: FOR-152
    Summary: documentation: integrating forrest tasks with a project build process
       Type: Task

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Forrest
  Component: None

   Reporter: David Crossley

    Created: Fri, 21 May 2004 11:27 AM
    Updated: Wed, 26 May 2004 4:18 PM

Quoting Dave Brondsema ...
Actually if you don't want any of the forrestbot features (getsrc, 
deploy, notify, etc) you can import instead of the 
forrestbot.  Then the 'site' target and any other forrest target can be used in your project.
 Here's a very small example, let me know if you need more explanation (somebody remind me
to put this as a FAQ...)

<project name="myproject" default="hello">
    <property environment="env"/>
    <import file="${env.FORREST_HOME}/"/>

    <target name="hello">

    <!-- site is a target imported from -->
    <target name="post-build" depends="site">
      <echo>something here</echo>

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message