On Jan 28, 2008, at 7:54 PM, Jacob Kjome wrote:
I think it would be better to avoid adding a dependency to pick up
the CronExpression since that would likely force the Policy off
into a yet another companion since we would not want to force
everyone who uses extras to pick up quartz.
Why would this be an issue? For those wanting to use
CronExpressionTriggeringPolicy, they would simply put the dependency
in the classpath. For those that don't use
CronExpressionTriggeringPolicy, there would be no runtime
dependency, only a compile time dependency. If we were talking
about Log4j-core, then it would be a different story. But I don't
see why log4j-extras has to be shielded from external dependencies?
Jake
I likely overstated that. If I were doing it myself, I'd want to make
sure that CronExpression added sufficient value to justify the extra
dependency and that the dependency was ASL licensed (which was
indicated) and that the project is sufficiently live etc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
