Nathan Bubna <[EMAIL PROTECTED]> writes:
>On 10/27/05, Henning P. Schmiedehausen <[EMAIL PROTECTED]> wrote:
>> [EMAIL PROTECTED] writes:
>>
>> > jakarta/velocity/tools/trunk/lib/commons-beanutils-1.7.0.jar (with
>> > props)
>>
>> Do you need code from the Bean collections API or would
>> commons-beanutils-core-1.7.0 be sufficient here?
I ran some tests:
| jar | jar.generic | jar.struts | jar.view
----------------+-----+-------------+------------+-----------
beanutils | X | X | X | X
collections | X | | X | X
digester | X | | X | X
lang | X | X | X | X
logging | | | |
validator | X | | X |
oro | | | |
servlet | X | | X | X
sslext | X | | X |
struts | X | | X |
velocity | X | X | X | X
- beanutils-core works fine BTW but the size difference (20k) is
neglectable.
- oro and commons-logging can actually go, they are not needed for
compilation of velocity-tools.
- all velocity tool distributions depend on beanutils, lang and
velocity.
- the "full" jar and the "struts" jar are the same thing.
>i don't believe we directly use their API in our code. the lib is
>present for digester and struts to use.
Nope. Some tools rely on it. In fact, beanutils is one of the two
indispensable dependencies of velocity-tools.
Best regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
4 - 8 - 15 - 16 - 23 - 42
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
