On 17 Mar 07, at 7:06 PM 17 Mar 07, Brett Porter wrote:
On 18/03/2007, at 9:56 AM, Jason van Zyl wrote:
On 17 Mar 07, at 6:37 PM 17 Mar 07, Brett Porter wrote:
What about anything with a .vm extension?
download.apt.vm gets processed as vm first, then apt. We can do
that in Doxia with zero-configuration.
I really don't want it on by default, because it'll break
existing documents
It won't break any existing documents. If it doesn't parse it just
goes back to processing the raw document.
Wouldn't documents like:
src/site/apt/guides/getting-started/index.apt
have the ${pom.name} expressions (which are meant to be
expressions) populated with the value?
Wouldn't break them, they would render just interpolate the value.
So, yes, you would have to escape that value or use a literal block.
, and I can see situations where we might want to facilitate
different processors.
Sure, I'll ponder this a bit more. I don't want it to cause any
problems, but zero configuration. What kind of other processors
are you thinking about?
Not that I particularly want to do it now, but this could have been
a useful way to support some of the maven1 docs that used jelly.
I'm going to pretend I didn't hear the word Jelly. La la la la, dum
dee do.
Did we really process documents through Jelly? We were really on
crack. But James was on crack first, so it's not all our fault.
Ultimately I think it would be good if people could configure filter
input streams and chain them and then you can really have whatever
you want. Unfortunately velocity doesn't expose stream processing.
Not yet anyway.
But I guess it would allow using other templating solutions if they
are a skillset the team already has.
I'm not sure it's that important, but it seems simple and useful to
make it extensible in that way.
Maybe we could make a configuration and allow the options to be
configured from the site.xml.
Yeah, I think pushing site plugin configuration in general into
there when it's related to rendering is a good idea.
I will figure out something there then with that.
Jason.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
