Andreas Hartmann wrote:
Joern Nettingsmeier wrote:
do i really have to dig into java code in order to profit
from this feature?
That depends on your publication. If you use the default publication with
some layout changes, you won't need a custom Instantiator. If you add your
own config files which have to be copied for templates, you will have to
write an Instantiator.
ok, that is reassuring :-D
Another option would be a ConfigurableInstantiator, which would read a
list of to-be-copied files / directories from some config file.
You could file an enhancement bug if you consider this useful.
first i'll play with it a little to understand the issue better.
another q: i have already played with the "new publication" usecase in
1.4 and it allows me to select another publication as a starting point.
is this already a (dynamic) template, i.e. will changes in the original
publication propagate to the new one, or is it just being copied once
during creation?
It is an instance of the template, i.e. changes will be propagated
immediately (or, more correctly expressed, the instance will access
the files from the template, which means that changes are reflected
immediately).
great. so just to make the "new publication" usecase uses the mechanism
explained in
http://lenya.apache.org/1_4/reference/publication-templating/index.html#Setting+Up+a+Publication+To+Support+Templating
? if so, can someone add a note to this document? it was not obvious to
me. (i'll put it in the wiki as well as soon as i can reach it again.)
regards,
jörn
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
