Quantcast

Fwd: Re: [ANNOUNCE] Velocity Engine 2.0 RC5 test build available

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Fwd: Re: [ANNOUNCE] Velocity Engine 2.0 RC5 test build available

Claude Brisson-2
I think it is an Eclipse caching issue. Is restarting Eclipse the same
as emptying its cache? It may have a persistent cache.

I found two references to "ResourceLoader2" that have been forgotten in
comments, but they are totally harmless and don't make a new RC
necessary, IMO. The deprecated tag clearly comes from a previous RC.


   Claude

-------- Forwarded Message --------
Subject: Re: [ANNOUNCE] Velocity Engine 2.0 RC5 test build available
Date: Wed, 4 Jan 2017 11:59:36 +0000
From: Greg Huber <[hidden email]>
To: Claude Brisson <[hidden email]>



It seems to be in the text hover (eclipse) I checked the source but
could not find the reference.  There was a ref in
ResourceLoader.resourceExists but not the below :

*Deprecated.*/- use|ResourceLoader2|/

This is abstract class the all text resource loaders should extend.

Version:
    $Id: ResourceLoader.java 1753137 2016-07-17 23:33:09Z cbrisson $
Author:
    Jason van Zyl <mailto:[hidden email]>
    Geir Magnusson Jr. <mailto:[hidden email]>

I restarted eclipse also which did not fix it.  Maybe its in the .jar?

It was not marked @depreciated so I reverted back to ResourceLoader
which works great for me.

Cheers Greg


On 4 January 2017 at 11:21, Claude Brisson <[hidden email]
<mailto:[hidden email]>> wrote:

    Up to RC4, ResourceLoader was deprecated and ResourceLoader2 was the
    replacement. ResourceLoader was just transmitting calls to
    ResourceLoader2.

    But since then, we got rid of the dependency towards
    commons-collections, hence breaking the former ResourceLoader API.
    So the B.C. stub was dropped.

    Where do you see this message? Did you issue a make clean before
    recompiling?

       Claude


    On 04/01/2017 10:13, Greg Huber wrote:

        For this rc5 is says

        org.apache.velocity.runtime.re
        <http://org.apache.velocity.runtime.re>source.loader.ResourceLoader2;

        does not exist and ResourceLoader says its depreciated?

        Cheers Greg

        On 3 January 2017 at 23:43, Claude Brisson <[hidden email]
        <mailto:[hidden email]>> wrote:

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

            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
            <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/
            <https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0/>

            Maven 2 staging repository:

               *
            https://repository.apache.org/content/repositories/orgapache
            <https://repository.apache.org/content/repositories/orgapache>
            velocity-1015/

            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


            Regards,

                Claude





Loading...