On Thu, Jun 16, 2011 at 5:27 AM, Martin Grigorov <[email protected]> wrote: > With all this said I think it is better to leave it as it is now. I.e. > not moving it anywhere. > It doesn't cause us troubles. It just stays where it is. > I still believe it is not used (wildly) with the only one answer "We > plan to use it someday"... >
I haven't chimed in because my vote doesn't really count, but we do actually use this feature to implement a pretty big part of our application at work. It would make upgrading to the next version(s) that much more difficult if it were moved. If I had to cast an "official" vote, then I'd be -0.9. :) My objections would be the fact that we use it and I wouldn't want to see support for it go away and that moving the code would put it outside the "protection" of the ASF and its stringent project/code management policies. Do people really build the entire library of tests when working on a specific feature? I usually set up a specific test to run over and over again while I'm working on a specific piece of code. Of course, before I check stuff in, I'd run the full test suite to make sure I haven't broken anything. Besides, you can mark the velocity tests as a long-running tests and specifically ignore those during your development cycle (not during CI builds of course).
