I suddenly realised the issue with "cocoon-trunk". It needs
to run its 'build docs' before running 'forrest'. It generates
some extra source documentation before forrest starts.
There is a global parameter "forrest-exec" which can call
a shell script to do other things, then call forrest.
I have t
Johannes Schaefer wrote:
Has this something to do with the linkmap?
See
http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=1617
Yes and no :-)
They are two different things that together with skinconf.xml and
forrest.properties form the basic config documents that Forrest uses.
A
Has this something to do with the linkmap?
See
http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=1617
Johannes
Nicola Ken Barozzi wrote:
Reinhard Poetz wrote:
Nicola Ken Barozzi wrote:
...
IMHO they will change in 0.8, with the introduction of the locationmap.
Can you give me a po
Reinhard Poetz wrote:
Nicola Ken Barozzi wrote:
...
IMHO they will change in 0.8, with the introduction of the locationmap.
Can you give me a pointer to "locationmap"?
Hmmm... it's in the mail archives ;-)
Ok, well it's about describing where the sources for Forrest are with a
special "sitemap" c
Nicola Ken Barozzi wrote:
Reinhard Poetz wrote:
Do you consider the structure of Forrest 0.6 repositories as stable?
No.
I've seen that forrestbot on brutus, that uses Forrest 0.7, builds my
Forrest 0.6 project perfectly.
That's nice to hear :-)
Can I trust that Forrest 1.0 will build my 0.6 pr
Reinhard Poetz wrote:
Do you consider the structure of Forrest 0.6 repositories as stable?
No.
I've seen that forrestbot on brutus, that uses Forrest 0.7, builds my
Forrest 0.6 project perfectly.
That's nice to hear :-)
Can I trust that Forrest 1.0 will build my 0.6 projects *without* having
to
Do you consider the structure of Forrest 0.6 repositories as stable? I've seen
that forrestbot on brutus, that uses Forrest 0.7, builds my Forrest 0.6 project
perfectly.
Can I trust that Forrest 1.0 will build my 0.6 projects *without* having to
modify configuration files too or do already know
David Crossley wrote:
Why would this suddenly be needed for gump? It was okay
without this until recently. I am wondering if it was
a symptom of some other recent change in forrest.
I think that this is related to remove the ant-proxy build.
David Crossley wrote:
> Ron Blaschke wrote:
>> David Crossley wrote:
>> > Ron Blaschke wrote:
>> Sorry, guess I am too deep into the code, not spelling things out.
>> Pod supports entities as E, akin to &entity; in XML. But
>> instead of just passing them on (E -> ΓΌ), I thought it
>> would be good
