Re: [Springframework-developer] Scheduler update #2

[Rod J. <rod...@in...>]

Ivan,

Thanks for the update.

> Will the scheduler be accepted as a part of Spring?

We should probably take a vote on this.

I would probably make it a separate project and download within Spring,
spring-scheduler, dependent on the main codebase. Other crucial things are:

- Code review.
- Volume of code. If there's lots of code, it's a stronger argument for
putting it outside the main codebase.
- Any dependencies it introduces.
- 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.
- Your commitment to maintaining it, providing forum/list support etc.

> I am all for having pluggable scheduler, so people can choose the one
> they like. Is anyone willing to contribute a Quartz wrapper? Now would
> be a very good time to get the abstraction interfaces right.
+1

I think abstraction interfaces are very important, and consistent with
Spring's approach in general.

Providing a default scheduler implementation as standard might flow from
that.

Regards,
Rod