Alright, with 1.0.0-M2 released later today, it's time to discuss what to do for the next milestone. My wish is to have all major changes to the API done by M3. Therefore, I suggest focusing on the following three items:
* JSecurity integration - throw out our own security stuff and use JSecurity instead. Work on this has already started * OSGi support - restructure our package structure to better separate our public API from the internal implementation. As part of that, we should also make sure we work in a OSGi environment. This might include exposing services to allow setting up FtpServer in a OSGi runtime. * Generic Ftplet - make the Ftplet interface generic in that it only contains methods similar to that of Servlet.service(), possibly beforeCommand() and afterCommand(). These would then be mapped to the current methods, such as onMkdirStart() via a template class like DefaultFtplet (compare with HttpServlet). The aim is to make Ftplets generic and be able to respond to any command, not just those that we have defined in the interface while making the transition easy for those with existing Ftplets. In addition, fixing bugs and making FtpServer more stable is of course ongoing. Recently we've had a lot of great bug reports so I would like to see these in M3 rather sooner than later. Hopefully we can do the M3 release as soon as possible. After M3, I would like to completely focus on stability and maturity so that the next release can be an RC for 1.0. What do you think? Would to like to include something else in M3? Or exclude some of those proposed above? /niklas
