Jeff,
It looks as though the problem here was my committing an 'imagesources'
directory under resources. I am assuming that the fact that there were
.pngs with the same root name as .fig, .dia and .sxd files has confused
the file groper.
I am about to cvs rm the files there and find
This was run against a clean checkout with a recent cvs update. When I
run against my previous tree, also just cvs updated, the forrest build
proceeds. I'll try to find out why.
Peter
Peter B. West wrote:
Fopdevs,
Has anyone else tried to run forrest against a new HEAD checkout? When
I
On Thu, Mar 13, 2003 at 09:16:52PM +1000, Peter B. West wrote:
This was run against a clean checkout with a recent cvs update. When I
run against my previous tree, also just cvs updated, the forrest build
proceeds. I'll try to find out why.
At:
Jeff,
I'm running forrest locally. I assume that there is no attempt by a
locally run forrest to talk to forrestbot.cocoondev.org. Which would
mean that the forrestbot has failed at the same place that I have.
wouldn't it?
Peter
Jeff Turner wrote:
On Thu, Mar 13, 2003 at 09:16:52PM +1000,
On Thu, Mar 13, 2003 at 10:31:23PM +1000, Peter B. West wrote:
Jeff,
I'm running forrest locally. I assume that there is no attempt by a
locally run forrest to talk to forrestbot.cocoondev.org.
Nope
Which would mean that the forrestbot has failed at the same place that
I have. wouldn't
Today, it's working. Who knows? Have had a reboot since.
Peter
Jeff Turner wrote:
On Thu, Mar 13, 2003 at 10:31:23PM +1000, Peter B. West wrote:
I've just updated FOP and generated docs locally, and it all worked. I
didn't even get the RuntimeException. Weird..
--
Peter B. West [EMAIL
