I am also a [resources] developer and while I wish there were more interest
in supporting it, I just don't see that happening any time soon. Also, I
agree with Niall that the API needs a bit of clean up.
At one point, the existing MessageResources (Struts) were to be deprecated
in favor of commons-resources. I remember seeing it on it on the roadmap
and having a few discussions around it, but I can't find the link for it
right now....which says more about my involvement than I like to admit ;)
So, +1 for fast track.
I suppose if we need it bad enough for a future release, we can always pull
it back out and try again.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring
678.910.8017
----- Original Message -----
From: "Martin Cooper" <[EMAIL PROTECTED]>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Sent: Monday, March 06, 2006 1:01 AM
Subject: Re: [resources][all] Resources status
On 3/5/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
On 3/5/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
> Can we establish the status of [resources].
<snip/>
Does a [resources] developer want to speak up in its favour?
> Or should we fast track it to dormant?
If no other commons developers show interest in working on it then +1
Technically, I'm a Resources developer, but I haven't touched it in a _long_
time. Given that most of my coding these days is in JavaScript and
ActionScript, that's not likely to change any time soon, so +1 for
fast-tracking Resources to dormant.
--
Martin Cooper
Niall
> 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]
