You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Claude Brisson <cl...@renegat.net> on 2017/04/14 10:41:45 UTC

[ANNOUNCE] Velocity Engine 2.0 RC8 test build available

A new test build of Velocity Engine 2.0 is available (RC8).

No determination as to the quality ('alpha,' 'beta,' or 'GA') of 
Velocity Engine 2.0 has been made, and at this time it is simply a "test 
build". We welcome any comments you may have, and will take all feedback 
into account if a quality vote is called for this build.

Release notes:

* 
https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0/release-notes.html

Distribution:

  * https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0/

Maven 2 staging repository:

  * 
https://repository.apache.org/content/repositories/orgapachevelocity-1019/

A vote regarding the quality of this test build will be initiated within 
the next couple of days.

Release Candidates changelog:

   RC1: initial candidate
   RC2: bugfixes
   RC3: review SLF4J Logger names (instead of a single logger named 
"Velocity", have a hierarchy of loggers with a base of 
'org.apache.velocity')
   RC4: minor fixes
   RC5:
    * the default encoding is now UTF-8 (and not the platform default)
    * commons-collections is not any more a compilation dependency
    * commons-lang3 dependency is not any more shaded
    * the configuration API doesn't reference ExtProperties
    * the events API has been optimized and reviewed: all events do 
receive the current Context
    * there has been a few optimizations in ASTStringLiteral rendering
   RC6: mostly code cleaning and build process optimization ; assembly 
module has been dropped
   RC7: still a lot of core cleanups and reviews, plus:
    * new strategy for reference boolean evaluation
    * allow expressions inside [ ] : $foo[$bar + 1]
   RC8: vararg methods bugfix

Regards,

   Claude


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


Re: [ANNOUNCE] Velocity Engine 2.0 RC8 test build available

Posted by Greg Huber <gr...@gmail.com>.
Works great for me +1.

Cheers Greg

On 14 April 2017 at 11:41, Claude Brisson <cl...@renegat.net> wrote:

> A new test build of Velocity Engine 2.0 is available (RC8).
>
> No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity
> Engine 2.0 has been made, and at this time it is simply a "test build". We
> welcome any comments you may have, and will take all feedback into account
> if a quality vote is called for this build.
>
> Release notes:
>
> * https://dist.apache.org/repos/dist/dev/velocity/velocity-eng
> ine/2.0/release-notes.html
>
> Distribution:
>
>  * https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0/
>
> Maven 2 staging repository:
>
>  * https://repository.apache.org/content/repositories/orgapache
> velocity-1019/
>
> A vote regarding the quality of this test build will be initiated within
> the next couple of days.
>
> Release Candidates changelog:
>
>   RC1: initial candidate
>   RC2: bugfixes
>   RC3: review SLF4J Logger names (instead of a single logger named
> "Velocity", have a hierarchy of loggers with a base of
> 'org.apache.velocity')
>   RC4: minor fixes
>   RC5:
>    * the default encoding is now UTF-8 (and not the platform default)
>    * commons-collections is not any more a compilation dependency
>    * commons-lang3 dependency is not any more shaded
>    * the configuration API doesn't reference ExtProperties
>    * the events API has been optimized and reviewed: all events do receive
> the current Context
>    * there has been a few optimizations in ASTStringLiteral rendering
>   RC6: mostly code cleaning and build process optimization ; assembly
> module has been dropped
>   RC7: still a lot of core cleanups and reviews, plus:
>    * new strategy for reference boolean evaluation
>    * allow expressions inside [ ] : $foo[$bar + 1]
>   RC8: vararg methods bugfix
>
> Regards,
>
>   Claude
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>

Re: [ANNOUNCE] Velocity Engine 2.0 RC8 test build available

Posted by Greg Huber <gr...@gmail.com>.
Great thanks.  The generated source looks correct.

Cheers Greg

On 27 April 2017 at 14:44, Claude Brisson <cl...@renegat.net> wrote:

> Glad to hear it's a feature, not a bug...
>
> Almost all methods. org.apache.velocity.util.StringUtils now only
> contains several variants of the formatFileString() method, which should
> not be used by Texe.
>
> On 27/04/2017 14:40, Greg Huber wrote:
>
>> Claude,
>>
>> I think I have managed to resolve it.  Most of the methods in
>> org.apache.velocity.util.StringUtils have been removed. Which texen
>> relies
>> on for parsing the vm files via the context.
>>
>> I updated the texen.properties variable to use the commons StringUtils
>> instead.
>>
>> ie
>>
>> #context.objects.strings=org.apache.velocity.util.StringUtils
>> context.objects.strings=org.apache.commons.lang3.StringUtils
>>
>> So far it looks OK.  Were all of the string methods replaced by the
>> commons
>> version?
>>
>> Cheers Greg
>>
>>
>> On 27 April 2017 at 13:29, Claude Brisson <cl...@renegat.net> wrote:
>>
>> Thanks.
>>>
>>> The old release candidate builds are available from the development
>>> distribution svn history.
>>>
>>> You can get the revision for a specific RC with:
>>>
>>>      svn log https://dist.apache.org/repos/
>>> dist/dev/velocity/velocity-eng
>>> ine/2.0
>>>
>>> and then, you would typically download a specific RC with:
>>>
>>>      svn export https://dist.apache.org/repos/
>>> dist/dev/velocity/velocity-engine/2.0/velocity-engine-core-2.0.jar@19088
>>>
>>> here, for instance, 19088 corresponds to the RC7.
>>>
>>>
>>> On 27/04/2017 12:31, Greg Huber wrote:
>>>
>>> Well, I found a version dated 16th November 2016, which does work so its
>>>> not my setup.
>>>>
>>>> Will try and debug the ant process for any errors.
>>>>
>>>> On 14 April 2017 at 11:41, Claude Brisson <cl...@renegat.net> wrote:
>>>>
>>>> A new test build of Velocity Engine 2.0 is available (RC8).
>>>>
>>>>> No determination as to the quality ('alpha,' 'beta,' or 'GA') of
>>>>> Velocity
>>>>> Engine 2.0 has been made, and at this time it is simply a "test build".
>>>>> We
>>>>> welcome any comments you may have, and will take all feedback into
>>>>> account
>>>>> if a quality vote is called for this build.
>>>>>
>>>>> Release notes:
>>>>>
>>>>> * https://dist.apache.org/repos/dist/dev/velocity/velocity-eng
>>>>> ine/2.0/release-notes.html
>>>>>
>>>>> Distribution:
>>>>>
>>>>>    * https://dist.apache.org/repos/dist/dev/velocity/velocity-eng
>>>>> ine/2.0/
>>>>>
>>>>> Maven 2 staging repository:
>>>>>
>>>>>    * https://repository.apache.org/content/repositories/orgapache
>>>>> velocity-1019/
>>>>>
>>>>> A vote regarding the quality of this test build will be initiated
>>>>> within
>>>>> the next couple of days.
>>>>>
>>>>> Release Candidates changelog:
>>>>>
>>>>>     RC1: initial candidate
>>>>>     RC2: bugfixes
>>>>>     RC3: review SLF4J Logger names (instead of a single logger named
>>>>> "Velocity", have a hierarchy of loggers with a base of
>>>>> 'org.apache.velocity')
>>>>>     RC4: minor fixes
>>>>>     RC5:
>>>>>      * the default encoding is now UTF-8 (and not the platform default)
>>>>>      * commons-collections is not any more a compilation dependency
>>>>>      * commons-lang3 dependency is not any more shaded
>>>>>      * the configuration API doesn't reference ExtProperties
>>>>>      * the events API has been optimized and reviewed: all events do
>>>>> receive
>>>>> the current Context
>>>>>      * there has been a few optimizations in ASTStringLiteral rendering
>>>>>     RC6: mostly code cleaning and build process optimization ; assembly
>>>>> module has been dropped
>>>>>     RC7: still a lot of core cleanups and reviews, plus:
>>>>>      * new strategy for reference boolean evaluation
>>>>>      * allow expressions inside [ ] : $foo[$bar + 1]
>>>>>     RC8: vararg methods bugfix
>>>>>
>>>>> Regards,
>>>>>
>>>>>     Claude
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>>
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>

Re: [ANNOUNCE] Velocity Engine 2.0 RC8 test build available

Posted by Claude Brisson <cl...@renegat.net>.
Glad to hear it's a feature, not a bug...

Almost all methods. org.apache.velocity.util.StringUtils now only 
contains several variants of the formatFileString() method, which should 
not be used by Texe.

On 27/04/2017 14:40, Greg Huber wrote:
> Claude,
>
> I think I have managed to resolve it.  Most of the methods in
> org.apache.velocity.util.StringUtils have been removed. Which texen relies
> on for parsing the vm files via the context.
>
> I updated the texen.properties variable to use the commons StringUtils
> instead.
>
> ie
>
> #context.objects.strings=org.apache.velocity.util.StringUtils
> context.objects.strings=org.apache.commons.lang3.StringUtils
>
> So far it looks OK.  Were all of the string methods replaced by the commons
> version?
>
> Cheers Greg
>
>
> On 27 April 2017 at 13:29, Claude Brisson <cl...@renegat.net> wrote:
>
>> Thanks.
>>
>> The old release candidate builds are available from the development
>> distribution svn history.
>>
>> You can get the revision for a specific RC with:
>>
>>      svn log https://dist.apache.org/repos/dist/dev/velocity/velocity-eng
>> ine/2.0
>>
>> and then, you would typically download a specific RC with:
>>
>>      svn export https://dist.apache.org/repos/
>> dist/dev/velocity/velocity-engine/2.0/velocity-engine-core-2.0.jar@19088
>>
>> here, for instance, 19088 corresponds to the RC7.
>>
>>
>> On 27/04/2017 12:31, Greg Huber wrote:
>>
>>> Well, I found a version dated 16th November 2016, which does work so its
>>> not my setup.
>>>
>>> Will try and debug the ant process for any errors.
>>>
>>> On 14 April 2017 at 11:41, Claude Brisson <cl...@renegat.net> wrote:
>>>
>>> A new test build of Velocity Engine 2.0 is available (RC8).
>>>> No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity
>>>> Engine 2.0 has been made, and at this time it is simply a "test build".
>>>> We
>>>> welcome any comments you may have, and will take all feedback into
>>>> account
>>>> if a quality vote is called for this build.
>>>>
>>>> Release notes:
>>>>
>>>> * https://dist.apache.org/repos/dist/dev/velocity/velocity-eng
>>>> ine/2.0/release-notes.html
>>>>
>>>> Distribution:
>>>>
>>>>    * https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0/
>>>>
>>>> Maven 2 staging repository:
>>>>
>>>>    * https://repository.apache.org/content/repositories/orgapache
>>>> velocity-1019/
>>>>
>>>> A vote regarding the quality of this test build will be initiated within
>>>> the next couple of days.
>>>>
>>>> Release Candidates changelog:
>>>>
>>>>     RC1: initial candidate
>>>>     RC2: bugfixes
>>>>     RC3: review SLF4J Logger names (instead of a single logger named
>>>> "Velocity", have a hierarchy of loggers with a base of
>>>> 'org.apache.velocity')
>>>>     RC4: minor fixes
>>>>     RC5:
>>>>      * the default encoding is now UTF-8 (and not the platform default)
>>>>      * commons-collections is not any more a compilation dependency
>>>>      * commons-lang3 dependency is not any more shaded
>>>>      * the configuration API doesn't reference ExtProperties
>>>>      * the events API has been optimized and reviewed: all events do
>>>> receive
>>>> the current Context
>>>>      * there has been a few optimizations in ASTStringLiteral rendering
>>>>     RC6: mostly code cleaning and build process optimization ; assembly
>>>> module has been dropped
>>>>     RC7: still a lot of core cleanups and reviews, plus:
>>>>      * new strategy for reference boolean evaluation
>>>>      * allow expressions inside [ ] : $foo[$bar + 1]
>>>>     RC8: vararg methods bugfix
>>>>
>>>> Regards,
>>>>
>>>>     Claude
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


Re: [ANNOUNCE] Velocity Engine 2.0 RC8 test build available

Posted by Greg Huber <gr...@gmail.com>.
Claude,

I think I have managed to resolve it.  Most of the methods in
org.apache.velocity.util.StringUtils have been removed. Which texen relies
on for parsing the vm files via the context.

I updated the texen.properties variable to use the commons StringUtils
instead.

ie

#context.objects.strings=org.apache.velocity.util.StringUtils
context.objects.strings=org.apache.commons.lang3.StringUtils

So far it looks OK.  Were all of the string methods replaced by the commons
version?

Cheers Greg


On 27 April 2017 at 13:29, Claude Brisson <cl...@renegat.net> wrote:

> Thanks.
>
> The old release candidate builds are available from the development
> distribution svn history.
>
> You can get the revision for a specific RC with:
>
>     svn log https://dist.apache.org/repos/dist/dev/velocity/velocity-eng
> ine/2.0
>
> and then, you would typically download a specific RC with:
>
>     svn export https://dist.apache.org/repos/
> dist/dev/velocity/velocity-engine/2.0/velocity-engine-core-2.0.jar@19088
>
> here, for instance, 19088 corresponds to the RC7.
>
>
> On 27/04/2017 12:31, Greg Huber wrote:
>
>> Well, I found a version dated 16th November 2016, which does work so its
>> not my setup.
>>
>> Will try and debug the ant process for any errors.
>>
>> On 14 April 2017 at 11:41, Claude Brisson <cl...@renegat.net> wrote:
>>
>> A new test build of Velocity Engine 2.0 is available (RC8).
>>>
>>> No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity
>>> Engine 2.0 has been made, and at this time it is simply a "test build".
>>> We
>>> welcome any comments you may have, and will take all feedback into
>>> account
>>> if a quality vote is called for this build.
>>>
>>> Release notes:
>>>
>>> * https://dist.apache.org/repos/dist/dev/velocity/velocity-eng
>>> ine/2.0/release-notes.html
>>>
>>> Distribution:
>>>
>>>   * https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0/
>>>
>>> Maven 2 staging repository:
>>>
>>>   * https://repository.apache.org/content/repositories/orgapache
>>> velocity-1019/
>>>
>>> A vote regarding the quality of this test build will be initiated within
>>> the next couple of days.
>>>
>>> Release Candidates changelog:
>>>
>>>    RC1: initial candidate
>>>    RC2: bugfixes
>>>    RC3: review SLF4J Logger names (instead of a single logger named
>>> "Velocity", have a hierarchy of loggers with a base of
>>> 'org.apache.velocity')
>>>    RC4: minor fixes
>>>    RC5:
>>>     * the default encoding is now UTF-8 (and not the platform default)
>>>     * commons-collections is not any more a compilation dependency
>>>     * commons-lang3 dependency is not any more shaded
>>>     * the configuration API doesn't reference ExtProperties
>>>     * the events API has been optimized and reviewed: all events do
>>> receive
>>> the current Context
>>>     * there has been a few optimizations in ASTStringLiteral rendering
>>>    RC6: mostly code cleaning and build process optimization ; assembly
>>> module has been dropped
>>>    RC7: still a lot of core cleanups and reviews, plus:
>>>     * new strategy for reference boolean evaluation
>>>     * allow expressions inside [ ] : $foo[$bar + 1]
>>>    RC8: vararg methods bugfix
>>>
>>> Regards,
>>>
>>>    Claude
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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: [ANNOUNCE] Velocity Engine 2.0 RC8 test build available

Posted by Claude Brisson <cl...@renegat.net>.
Thanks.

The old release candidate builds are available from the development 
distribution svn history.

You can get the revision for a specific RC with:

     svn log 
https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0

and then, you would typically download a specific RC with:

     svn export 
https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0/velocity-engine-core-2.0.jar@19088

here, for instance, 19088 corresponds to the RC7.


On 27/04/2017 12:31, Greg Huber wrote:
> Well, I found a version dated 16th November 2016, which does work so its
> not my setup.
>
> Will try and debug the ant process for any errors.
>
> On 14 April 2017 at 11:41, Claude Brisson <cl...@renegat.net> wrote:
>
>> A new test build of Velocity Engine 2.0 is available (RC8).
>>
>> No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity
>> Engine 2.0 has been made, and at this time it is simply a "test build". We
>> welcome any comments you may have, and will take all feedback into account
>> if a quality vote is called for this build.
>>
>> Release notes:
>>
>> * https://dist.apache.org/repos/dist/dev/velocity/velocity-eng
>> ine/2.0/release-notes.html
>>
>> Distribution:
>>
>>   * https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0/
>>
>> Maven 2 staging repository:
>>
>>   * https://repository.apache.org/content/repositories/orgapache
>> velocity-1019/
>>
>> A vote regarding the quality of this test build will be initiated within
>> the next couple of days.
>>
>> Release Candidates changelog:
>>
>>    RC1: initial candidate
>>    RC2: bugfixes
>>    RC3: review SLF4J Logger names (instead of a single logger named
>> "Velocity", have a hierarchy of loggers with a base of
>> 'org.apache.velocity')
>>    RC4: minor fixes
>>    RC5:
>>     * the default encoding is now UTF-8 (and not the platform default)
>>     * commons-collections is not any more a compilation dependency
>>     * commons-lang3 dependency is not any more shaded
>>     * the configuration API doesn't reference ExtProperties
>>     * the events API has been optimized and reviewed: all events do receive
>> the current Context
>>     * there has been a few optimizations in ASTStringLiteral rendering
>>    RC6: mostly code cleaning and build process optimization ; assembly
>> module has been dropped
>>    RC7: still a lot of core cleanups and reviews, plus:
>>     * new strategy for reference boolean evaluation
>>     * allow expressions inside [ ] : $foo[$bar + 1]
>>    RC8: vararg methods bugfix
>>
>> Regards,
>>
>>    Claude
>>
>>
>> ---------------------------------------------------------------------
>> 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: [ANNOUNCE] Velocity Engine 2.0 RC8 test build available

Posted by Greg Huber <gr...@gmail.com>.
Well, I found a version dated 16th November 2016, which does work so its
not my setup.

Will try and debug the ant process for any errors.

On 14 April 2017 at 11:41, Claude Brisson <cl...@renegat.net> wrote:

> A new test build of Velocity Engine 2.0 is available (RC8).
>
> No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity
> Engine 2.0 has been made, and at this time it is simply a "test build". We
> welcome any comments you may have, and will take all feedback into account
> if a quality vote is called for this build.
>
> Release notes:
>
> * https://dist.apache.org/repos/dist/dev/velocity/velocity-eng
> ine/2.0/release-notes.html
>
> Distribution:
>
>  * https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0/
>
> Maven 2 staging repository:
>
>  * https://repository.apache.org/content/repositories/orgapache
> velocity-1019/
>
> A vote regarding the quality of this test build will be initiated within
> the next couple of days.
>
> Release Candidates changelog:
>
>   RC1: initial candidate
>   RC2: bugfixes
>   RC3: review SLF4J Logger names (instead of a single logger named
> "Velocity", have a hierarchy of loggers with a base of
> 'org.apache.velocity')
>   RC4: minor fixes
>   RC5:
>    * the default encoding is now UTF-8 (and not the platform default)
>    * commons-collections is not any more a compilation dependency
>    * commons-lang3 dependency is not any more shaded
>    * the configuration API doesn't reference ExtProperties
>    * the events API has been optimized and reviewed: all events do receive
> the current Context
>    * there has been a few optimizations in ASTStringLiteral rendering
>   RC6: mostly code cleaning and build process optimization ; assembly
> module has been dropped
>   RC7: still a lot of core cleanups and reviews, plus:
>    * new strategy for reference boolean evaluation
>    * allow expressions inside [ ] : $foo[$bar + 1]
>   RC8: vararg methods bugfix
>
> Regards,
>
>   Claude
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>

Re: [ANNOUNCE] Velocity Engine 2.0 RC8 test build available

Posted by Greg Huber <gr...@gmail.com>.
I have noticed now that my bespoke taxen generator does not produce any
output.  Also there are no errors generated.

Is it possible to back to previous snapshots (rc1) to see if the problem
exists?

There seems to be only the lasted release in the repo.

https://repository.apache.org/content/repositories/orgapachevelocity-xxxx/

Cheers Greg

On 14 April 2017 at 11:41, Claude Brisson <cl...@renegat.net> wrote:

> A new test build of Velocity Engine 2.0 is available (RC8).
>
> No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity
> Engine 2.0 has been made, and at this time it is simply a "test build". We
> welcome any comments you may have, and will take all feedback into account
> if a quality vote is called for this build.
>
> Release notes:
>
> * https://dist.apache.org/repos/dist/dev/velocity/velocity-eng
> ine/2.0/release-notes.html
>
> Distribution:
>
>  * https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0/
>
> Maven 2 staging repository:
>
>  * https://repository.apache.org/content/repositories/orgapache
> velocity-1019/
>
> A vote regarding the quality of this test build will be initiated within
> the next couple of days.
>
> Release Candidates changelog:
>
>   RC1: initial candidate
>   RC2: bugfixes
>   RC3: review SLF4J Logger names (instead of a single logger named
> "Velocity", have a hierarchy of loggers with a base of
> 'org.apache.velocity')
>   RC4: minor fixes
>   RC5:
>    * the default encoding is now UTF-8 (and not the platform default)
>    * commons-collections is not any more a compilation dependency
>    * commons-lang3 dependency is not any more shaded
>    * the configuration API doesn't reference ExtProperties
>    * the events API has been optimized and reviewed: all events do receive
> the current Context
>    * there has been a few optimizations in ASTStringLiteral rendering
>   RC6: mostly code cleaning and build process optimization ; assembly
> module has been dropped
>   RC7: still a lot of core cleanups and reviews, plus:
>    * new strategy for reference boolean evaluation
>    * allow expressions inside [ ] : $foo[$bar + 1]
>   RC8: vararg methods bugfix
>
> Regards,
>
>   Claude
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>