forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Commented: (FOR-489) initial run of forrest from dist fails
Date Fri, 29 Apr 2005 22:32:37 GMT
The following comment has been added to this issue:

     Author: Ross Gardler
    Created: Fri, 29 Apr 2005 5:32 PM
The docs are correct, Forrest does come with Ant (see tools/ant). This is an unusal problem,
0.6 has been in use for quite some time and noone has come across this before.

In particular your workaround should not work since when you run Forrest it uses the Forrest
bundled version of Ant so updating your local installed version should make no difference.

If you want to we will work out why this did work for you. However, since you are now up and
running you may prefer that we close this issue and let you get on with the proper work.

Let us know if you want us to close this issue.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: FOR-489
    Summary: initial run of forrest from dist fails
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Forrest
             Launch 'forrest'

   Reporter: David Jung

    Created: Fri, 29 Apr 2005 11:32 AM
    Updated: Fri, 29 Apr 2005 5:32 PM
Environment: Redhat Fedora Core 3, Sun JDK 1.5.0-b64

Initial run of forrest per install instructions failed (first time user).
Downloaded and untarred 0.6 dist.
set env var FORREST_HOME in bash
added FORREST_HOME/bin to path.
cd'd into top-level and entered 'forrest' on cmd line

Result was this:
Apache Forrest.  Run 'forrest -projecthelp' to list options

/usr/bin/build-classpath: error: could not find ant-launcher Java extension for this JVM
/usr/bin/build-classpath: error: All specified jars were not found

I downloaded and tried an Apr28 snapshot with similar results.
(it complained it needed to be built first.  Running the build script gave the same error
as above)

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