On 18 Mar 07, at 12:23 AM 18 Mar 07, Brett Porter wrote:
On 18/03/2007, at 11:29 AM, Jason van Zyl wrote:
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.
Right, as far as I'm concerned that's breaking something :)
Yes, but this is 2.0 of the plugin so breaking your documents would
be a new feature :-)
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.
Yeah, I think we did. Or at least there was those jsl reports. I'm
not suggesting we actually go and do it now, but it might have been
a useful migration path at one point :)
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.
Agreed.
I will figure out something there then with that.
Cool, thanks.
The campaign for no-more-alphas seems to be going well. :)
- 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]
