You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Dan Damian <da...@star-group.ro> on 2007/04/20 10:49:13 UTC
I WANT TO UNSUSCRIBE
-----Original Message-----
From: Apache Wiki [mailto:wikidiffs@apache.org]
Sent: 20 aprilie 2007 11:21
To: velocity-cvs@jakarta.apache.org
Subject: [Velocity Wiki] Trivial Update of "Velocity15ReleaseNotes" by
ChristophReck
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Velocity Wiki"
for change notification.
The following page has been changed by ChristophReck:
http://wiki.apache.org/velocity/Velocity15ReleaseNotes
------------------------------------------------------------------------
------
* In order to run "ant test" with ant 1.6.x, you will need to copy
the junit.jar into <ANT_HOME>/lib. Otherwise, please upgrade to ant 1.7
(which accesses the junit jar from within the Velocity classpath).
* Macros cannot be defined in one file and included with #parse in
another. See MacroIssues for more information.
* If you call VelocityEngine.evaluate() (or use the RenderTool) from
within a macro and a #foreach loop, you will not be able to access the
loop variable. See [https://issues.apache.org/jira/browse/VELOCITY-504
Velocity-285].
- * If your references used shorthand notation (e.g. "$foo") and were
followed immediately by a "(" character, they may have slipped through a
whole in the parser which was closed in Velocity 1.5, causing them to
throw parse exceptions. See
[http://issues.apache.org/jira/browse/VELOCITY-528 Velocity-528]. Using
formal notation (e.g. "${foo}") will resolve this.
+ * If your references used shorthand notation (e.g. "$foo") and were
followed immediately by a "(" character, they may have slipped through a
hole in the parser which was closed in Velocity 1.5, causing them to
throw parse exceptions. See
[http://issues.apache.org/jira/browse/VELOCITY-528 Velocity-528]. Using
formal notation (e.g. "${foo}") will resolve this.
* There remain various subtle escaping bugs
=== Other Notes ===
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: I WANT TO UNSUSCRIBE
Posted by Will Glass-Husain <wg...@gmail.com>.
Did you figure this t? Send an empty email to
dev-unsubscribe@velocity.apache.org and cvs-unsubscribe@velocity.apache.org.
Try both.
WILL
On 4/20/07, Dan Damian <da...@star-group.ro> wrote:
>
>
>
> -----Original Message-----
> From: Apache Wiki [mailto:wikidiffs@apache.org]
> Sent: 20 aprilie 2007 11:21
> To: velocity-cvs@jakarta.apache.org
> Subject: [Velocity Wiki] Trivial Update of "Velocity15ReleaseNotes" by
> ChristophReck
>
> Dear Wiki user,
>
> You have subscribed to a wiki page or wiki category on "Velocity Wiki"
> for change notification.
>
> The following page has been changed by ChristophReck:
> http://wiki.apache.org/velocity/Velocity15ReleaseNotes
>
> ------------------------------------------------------------------------
> ------
> * In order to run "ant test" with ant 1.6.x, you will need to copy
> the junit.jar into <ANT_HOME>/lib. Otherwise, please upgrade to ant 1.7
> (which accesses the junit jar from within the Velocity classpath).
> * Macros cannot be defined in one file and included with #parse in
> another. See MacroIssues for more information.
> * If you call VelocityEngine.evaluate() (or use the RenderTool) from
> within a macro and a #foreach loop, you will not be able to access the
> loop variable. See [https://issues.apache.org/jira/browse/VELOCITY-504
> Velocity-285].
> - * If your references used shorthand notation (e.g. "$foo") and were
> followed immediately by a "(" character, they may have slipped through a
> whole in the parser which was closed in Velocity 1.5, causing them to
> throw parse exceptions. See
> [http://issues.apache.org/jira/browse/VELOCITY-528 Velocity-528]. Using
> formal notation (e.g. "${foo}") will resolve this.
> + * If your references used shorthand notation (e.g. "$foo") and were
> followed immediately by a "(" character, they may have slipped through a
> hole in the parser which was closed in Velocity 1.5, causing them to
> throw parse exceptions. See
> [http://issues.apache.org/jira/browse/VELOCITY-528 Velocity-528]. Using
> formal notation (e.g. "${foo}") will resolve this.
> * There remain various subtle escaping bugs
>
> === Other Notes ===
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com