Re: [Springframework-developer] Scheduler update #2

[Ivan R. <iv...@we...>]

> I would probably make it a separate project and download within Spring,
> spring-scheduler, dependent on the main codebase.

   Why not in the main project? Having that functionality out of the
   box is very convenient.


> - Volume of code. If there's lots of code, it's a stronger argument for
> putting it outside the main codebase.

   It's actually rather small in size. Compiled classes are around
   30K at the moment.


> - Any dependencies it introduces.

   None (not counting commons-logging).


> - Unit test coverage. As our target is to go above 80% for 1.0 RC1, new code
> must have this kind of level of test coverage, verified via Clover.

   I'll look into that, add tests to the scheduler and come back later.


> - Your commitment to maintaining it, providing forum/list support etc.

   No problem. But I do plan *not* to expand its functionality
   significantly. It exists only to be lightweight, and those who need
   more should look at more capable projects (eg Quartz).

-- 
ModSecurity (http://www.modsecurity.org)
[ Open source IDS for Web applications ]