>
>(c) include force in 0.20, default it to "false", but
>have a message in the release notes warning about the
>change.
>
>Technically, even if most users forgot to read the
>warning in (c) they would still be OK, as they would
>be happy if no time was spent with unnecessary
>regnerations. Howeve
From: Glen Mazza <[EMAIL PROTECTED]>
(a) Don't include force patch at all -- only have this
option for 1.0. Argument for this: Haven't had too
many requests for it, we can continue as-is until 1.0.
Since no one else has answered I hope you dont object to me posting an
opinion.
I would tend t
Team,
I'm looking at the "force" parameter-- Sean's recent
patch for the Ant Task. This parameter, when set to
"false", will stop xslfo files from being processed if
there hasn't been a timestamp change on the xslfo file
compared to the output file. force="true" means always
generate.
A default
