I've always found it interesting there is a "commons-beanutils" and
"common-beanutils-core" deliverable. The name doesn't suggest what makes
the first one different. Usually the "core" artifact is foundational
(like tapestry-core or struts-core). If it is an API package, I would
add "api" to the end .. or fold the two together.
Stephen Colebourne wrote:
Henri Yandell wrote:
One area for discussion is the split between the optional Collections
component and the 'Core' beanutils. Do we maintain that, or should we
just fold the code back together?
1.7.0 shipped three versions:
commons-beanutils-1.7.0.jar
commons-beanutils-core-1.7.0.jar
commons-beanutils-collections-1.7.0.jar
where the first is the sum of the second and third.
Personally I think we should just merge them back together. It's not
worth the effort.
The purpose is to avoid forcing users to take dependencies that they
are not interested in, [collections] in this case. As such I think
that the split is a Good Thing.
Stephen
---------------------------------------------------------------------
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]
