Hi Ludovic, On 9/18/07, Ludovic Maitre <[EMAIL PROTECTED]> wrote: > Hi Steve, all > > As an old contributor which still follow the mailing list, i would like > to explain why i doesn't contribute nor use anymore Lokahi. It's because > at work we use (and i have contributed to develop) another system to > deploy j2ee webapps, a homegrown ant-remote solution with xml based > descriptors to describe the platforms/farms and the > products/applications to install [perhaps this is similar to what > smartfrog want to achieve or at least describe?]. Initially, i was > planning to use Lokahi to maintain the apache and tomcat servers, but > finally i do it with a combination of ant remote (to deploy binary and > config files) and a homegrown Java xml rpc API which call webmin rpc, > because i feel that i can control more things with this system.
Good to hear you solved your problem - even though Lokahi wasn't the turnkey solution for you. What extra control does you solution allow? I'd love to hear :) > > Toback, Steve a écrit : > > This brings some questions to mind - namely what is causing this project > > to not gather continued attention. > > > > What's preventing adoption or continued improvement? (other than me > > lack of personal time to work on this, this summer) > > > > > I have contributed some code some time ago to support MySQL i would say > that i haven't been able to keep up with the code changes in order to > maintain this port. Also the mysql code has been put on a side svn > branch and IIRC there is ongoing work in trunk to have a ORM framework, > so basically my contributions will be useless after this work will be > done. I would have continued to contribute or at least improve my code > if it would have been useful but this has not been the case and i > believe (but haven't checked) that the refactoring with the ORM > framework has not been finished --> i'm reluctant to work again on the > project until the devs which had began to contribute this code have > finished it. The refactoring for ORM (jackrabbit) was started in a completely separate branch (sandbox if you will) - knowing full well that I would break quite a few things, and take a long time doing so... The intent was to prove that it worked - and honestly I had thought I would have a lot more time to work on it. The mysql patches you contributed (Thank you) were put into a separate branch with the intention of merging them back to trunk quickly and after proving that it all still worked - shipping a release that worked on mysql & oracle. AFAIK there are only a few small issues remaining with the MySQL branch. I believe one of the things that needed to be still ported was the job scheduling thread. But without running it through a full set of tests - I am not sure. Steve
