Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
MIME-Version: 1.0
In-Reply-To: <528B20E8.3080001@gmail.com>
References: 
 <CAMopvkPjmf7hgGY4Eai031nQCfSempYt=+Z8E2zFwcVGQS83eg@mail.gmail.com>
 <528B20E8.3080001@gmail.com>
From: Lukasz Lenart <lukaszlenart@apache.org>
Date: Tue, 19 Nov 2013 10:03:24 +0100
Message-ID: 
 <CAMopvkOrQU803PT3mV9CFjOVZr65DyPNvMY8z7Fbkmen-g9NBw@mail.gmail.com>
Subject: Re: Registering aliases from within a plugin
To: Struts Developers List <dev@struts.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2013/11/19 Rene Gielen <rene.gielen@gmail.com>:
> what is the rationale behind refactoring out velocity support to a
> plugin? For which Struts version are you targeting this proposal?

Velocity support is optional (in theory), you can enable it by adding
Velocity dependencies to classpath. But because of VelocityManager
included in BeanSelectionProvider it's a required dependency. So you
must include Velocity (and all dependent libs as well) even if you
don't use it. I have figured that out when I wanted to upgrade to
latest Velocity version (1.7 or 2.0).

That's why I want to move Velocity support to a plugin.

Regarding 'for which version' - no idea. Right now I'm preparing a
field for all those changes, code is very coupled in many places. Thus
will also allow in the future move other Core functionalities to
plugins.


Regards
--=20
=C5=81ukasz
+ 48 606 323 122 http://www.lenart.org.pl/

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