On Fri, Dec 12, 2008 at 9:55 AM, Claude Brisson <[email protected]> wrote:
> Apparently, there's only one binary jar published in
> http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/velocity/velocity-tools/2.0-beta3/
> (i.e. no way to find velocity-tools-view-2.0-beta3.jar and
> velocity-tools-generic-2.0-beta3.jar).

I'm open to solutions...  i'm just not maven-savvy enough to feel
confident of the best way to do this.

> It's maybe not a so big deal since velocity-tools contains anything. We
> could consider that the ones wishing to use dedicated jars can build
> them themselves. After all, deploying only one jar is much more easier.

Or download them themselves.  They shouldn't have to build them.

> And the beta3 is not in the maven-1 repository.

Should we still be putting stuff in the maven-1 repo?  I'm not aware
of having done anything to put beta2 or even Engine 1.6 into the
maven-1 repo.  Perhaps some Maven maven has been doing this?

>
>  Claude
>
> On mar, 2008-12-02 at 22:01 -0800, Nathan Bubna wrote:
>> The Velocity developers are pleased to make the third (and probably
>> final) beta release of
>> VelocityTools 2.0 available for download.
>>
>> Downloads are available here:
>>  http://velocity.apache.org/download.cgi
>>
>> This should be useable as a drop in replacement for Tools 1.4 or Tools
>> 2.0-beta2, with a few minor exceptions. The 2.x series of
>> VelocityTools also requires both Velocity 1.5+ and JDK 1.5+.
>>
>> Since the last beta release, there have been a number of small fixes,
>> additional features (like caching for VelocityViewTag), and especially
>> improvements in the extensibility of VelocityView.
>>
>> The Velocity developers are very interested in all feedback regarding
>> Tools 2.0, especially regarding backwards compatibility with apps
>> designed for Tools 1.4 or earlier. We aim to enable a smooth,
>> incremental transition for developers and their applications.
>>
>> ---------------------------------------------------------------------
>> 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]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to