forrest-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Howard Lewis Ship <>
Subject Re: Upgrade to 0.6: validation issues
Date Wed, 20 Oct 2004 11:47:37 GMT
I kind of object to "bad" being equated with "non-standard".  Forrest
is the non-standard here, since it's a very common practice to put all
derived/compiled/generated files somewhere under target (which
simplifies any implementation of a clean target).



Thanks for pointing me towards this; I just changed


And I'm much closer to it working now (though I had to use my earlier
approach ... re-running Forrest's Ant using <java> task).

On 20 Oct 2004 11:31:21 +1000, David Crossley <> wrote:
> Howard Lewis Ship wrote:
> > No. I cannot. The structure is very important to the build files,
> > which automatically download forrest.  If forrest has a problem with
> > this, then it is broken.
> Oh, that certainly makes things complicated. At least
> we might have found your issue.
> I suppose that you have needed to change many settings
> in to get that layout to work.
> Please double-check that that file still correlates
> with a fresh obtained from doing
> a 'forrest seed' in some other new directory workspace
> (or just compare with
> apache-forrest-0.6/src/core/fresh-site/
> I see from your "echo-settings" list that the "project.temp-dir"
> has a bad setting. Normally it would be at ${project.home}/build/tmp/
> Try adding a specific entry to
> project.temp-dir=/some/hard-coded/pathname/foo
> or somewhere underneath your project, e.g.
> project.temp-dir=${project.home}/foo
> --
> David Crossley

Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind

View raw message