Hi Simo, That was just the type of information that I was looking for. Skipping a logging refactor vastly simplifies the work I was planning on doing.
I won't be able to publish my proof of concept until sometime next week because I have a vacation coming up. Thanks, -Elijah On Thu, Jul 28, 2011 at 12:01 PM, Simone Tripodi <simonetrip...@apache.org> wrote: > Hi Elijah, > it sounds a great interesting contribution, I haven't seen [chain] > development activity lately so I eventually volunteer to apply the > patch. Thanks in advance for your effort, [chain] if one of the > components that need new energy. > > Two recommendations: > > * we are updating components code to more recent JVM specs, please > try to keep 1.5 as target as much as possible. take the [digester] pom > (is the one I know more) as a good sample where starting from > * please don't migrate to slf4j. here at commons we continue using > commons-logging > > Hope that helps and count on me if you need more infos - feel free to > contact me even directly for trivial questions, better anyway > discussing on public MLs. > > A minor note: [collections] will get a new life soon ;) > Have a nice day, all the best! > Simo > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > > > On Thu, Jul 28, 2011 at 7:27 PM, David Karlsen <davidkarl...@gmail.com> wrote: >> +1 >> Den 28. juli 2011 06:42 skrev "Paul Benedict" <pbened...@apache.org> >> følgende: >>> >>> +1. I have done some of this privately (like generics). Having an >>> official version would be so useful. >>> >>> On Wed, Jul 27, 2011 at 10:46 PM, Elijah Zupancic <eli...@zupancic.name> >> wrote: >>> > Hi, >>> > >>> > I've been a active user for a number of years now and a big fan of the >>> > project. I'm a total beginner when it comes to contributing on Apache >>> > projects, so please bear with me. >>> > >>> > The code base for Apache Chain is starting to feel more and more >>> > dated. I would like to see the following changes in the project: >>> > >>> > * Upgrading the source code to 1.6. >>> > * Supporting generics on commands, so that we get something like >>> > Command<MyContext> >>> > * Switching the logging API over to SLF4J, so that we can swap out >>> > logging implementations >>> > * Using the new java.util.concurrency classes to handle thread safety as >> needed. >>> > * Removing deprecated methods. >>> > >>> > I realize that I am suggestion rather drastic API changes that may >>> > break the existing API and that is why I'm suggesting a 2.0. I have a >>> > prototype that I am working on and I do not see it being a lot of work >>> > to accomplish the above tasks. >>> > >>> > Would a 2.0 version of Chain be useful to anyone? Or should I just >>> > fork the project for my own needs and release it independently like >>> > the Commons Collections with Generics? >>> > >>> > I know that I'm assuming a lot and diving in head first here, so thank >>> > you ahead of time for any replies. >>> > >>> > -Elijah Zupancic >>> > >>> > --------------------------------------------------------------------- >>> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> > For additional commands, e-mail: dev-h...@commons.apache.org >>> > >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
