This is being tracked here https://jira.jboss.org/jira/browse/JBAS-6133

Why not just package your own version of quartz jar in your application?

henk53 wrote:

 

 

Well, it's either that or replacing the one JBoss bundles. This has been a workable workaround for me, but it's a workaround nevertheless.

 

Ideally, never replace what JBoss ships. It's always recommended to package your own version of library and use it.

henk53 wrote:

 

Surely, one day JBoss AS really has to upgrade this particularly library? As I understand it, it's used for some internal stuff in JBoss AS too (do EJB3 timers use it perhaps?). It's maybe just a bit out of place that year after year JBoss bundles the same version of Quartz, even though it is known to contain a plethora of bugs.

So even though it would not be the highest priority for many, I do wonder if JBoss AS is ever going to ship a more recent version. The version that's now being shipped is nearly 4 years old. If JBoss AS 6 is not going to update it, then this will probably mean another year, maybe two, for the next upgrade opportunity?

I don't think anyone is against upgrading the version of that library. It just doesn't seem to be on priority - because whatever it is used for in the AS, seems to be working fine with the current version. And as i already mentioned, ideally no user application should rely on the version of the thirdparty library (like quartz) shipped in the AS. Just to reiterate, i am not against upgrading the version - but the best way for user applications to deal with this is, to package their own quartz library in their app.