I am all for it, but isn't Velocity dependent on commons-collections?
(Velocity would be the last one standing, with SQLTemplate depending
on it, I don't see how we can get rid of it).
Andrus
On Apr 15, 2008, at 1:41 AM, Malcolm Edgar wrote:
> Hi Guys,
>
> On a related issue is there an intention to break the dependency on
> commons-collections. This is the JAR we have most issue with on
> application
> servers. Its something we can deal with by patching the app servers
> shared
> libraries, but when you are building "shrink wrap" style
> applications its a
> difficult thing for your customers to deal with.
>
> regards Malcolm Edgar
>
> On Mon, Apr 14, 2008 at 11:30 PM, Andrus Adamchik <andru..bjectstyle.org
> >
> wrote:
>
>>
>> On Apr 14, 2008, at 4:19 PM, Aristedes Maniatis wrote:
>>
>> Is it worth us putting *all* the dependencies into a repository
>> somewhere
>>> (Objectstyle or Apache?) or directly into svn so that we don't get
>>> stung
>>> again by library versions we depend on being removed from maven
>>> repositories
>>> or not being updated when we want them?
>>>
>>
>> I wouldn't bother to put *all* deps (things like commons-
>> collections or
>> commons-lang generally exist on the shared repo, posted on time,
>> and not
>> removed), but Hessian is a special case. Yeah, let's put it on
>> ObjectStyle.
>> I'll do that tonight.
>>
>> Andrus
>>
>>
This archive was generated by hypermail 2.0.0 : Mon Apr 14 2008 - 18:44:47 EDT