+1. This is absolutely the right way to go.
--
Martin Cooper
----- Original Message -----
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 14, 2001 6:20 PM
Subject: [VOTE] Changing Struts 1.1 to depend on Commons Packages
> As I cc'd to this list, the 1.0 versions of the beanutils, collections,
> and digester packages have been released under the Commons project. Now
> that these are official 1.0 releases, I propose to modify the Struts 1.1
> environment to depend on these packages, instead of the internal Struts
> versions (which have generally been deprecated).
>
> This will involve the following steps:
>
> * Modify the build environment to depend on these three packages
>
> * Modify internal Struts classes that rely on these packages to use
> the commons packages instead (normally just a change to the "import"
> statement).
>
> * Remove the internal versions of these classes.
>
> * Include these three packages in the Struts distribution (including
> inside the WAR files for each of the Struts web apps.
>
> * Modifying the appropriate documentation to mention the fact that these
> JARs, along with "struts.jar", must be included in the /WEB-INF/lib
> directory of Struts-based web applications.
>
> Making these changes will allow Struts itself to remain focused on the
> framework and custom tag libraries, while also benefitting from
> improvements in these three packages made by other projects that utilize
> them. (In the future, we'll probably do the same thing with the generic
> connection pool).
>
> Is everybody OK with doing this?
>
> Craig
>
>
>
