Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: domain of
 robertburrelldonkin@blueyonder.co.uk designates 195.188.213.5 as permitted
 sender)
Subject: Re: [functor] Still maintained?
From: robert burrell donkin <robertburrelldonkin@blueyonder.co.uk>
To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
In-Reply-To: <1979070745.20050401143556@semagia.com>
References: <1979070745.20050401143556@semagia.com>
Content-Type: text/plain
Date: Wed, 06 Apr 2005 22:05:09 +0100
Message-Id: <1112821509.5245.22.camel@knossos.elmet>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Fri, 2005-04-01 at 14:35 +0200, Lars Heuer wrote:
> Hi all,
> 
> Is the commons.functor package still under active development?

AFAIK it's hibernating

(it used to be very active and maybe one day it'll be active again.)

> Would it be wise to rely on the functor package for developing domain
> specific functors or would it be better to use mango or something
> else?

the activity (or not) of a component is not a reliable guide. small,
complete components tend to require less and less maintenance (the major
defects being ones introduced early and fixed by backwards
compatibility) and so activity tails off. though it may be tough to get
patches into mature components, there is a much smaller upgrade tax to
pay for those which are not accepted. 

personally speaking, i would look at a different set of criteria
including how good the match is to your needs. how well tested the code
is and what the standard of coding looks like (from the source).

- robert


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org