[Building Sakai] Quartz upgrade in trunk to 1.8.6 which changes groupId.

[Matthew Buckett]

There's an upgrade to quartz in trunk at the moment which moves us up to 1.8.6:

https://jira.sakaiproject.org/browse/SAK-20384

This involves a change in the groupId of the maven artifact.

-                <groupId>org.opensymphony.quartz</groupId>
+                <groupId>org.quartz-scheduler</groupId>

The artifactId remains the same. The APIs are very similar and I
haven't seen any problems running against the new API so far. If you
have a contrib tool that uses the quartz jar you should update when
building against trunk. If you have different profiles for 2.9/2.10
then you should move quartz to dependencies in the profiles and switch
the groupId.

There are database changes that are now in the 2.10 conversion scripts:

https://source.sakaiproject.org/svn//reference/trunk/docs/conversion/sakai_2_10_0_mysql_conversion.sql
https://source.sakaiproject.org/svn//reference/trunk/docs/conversion/sakai_2_10_0_oracle_conversion.sql

We could move to 2.1 but there is more work in doing this as the API changes:

http://quartz-scheduler.org/documentation/quartz-2.1.x/migration-guide

-- 
  Matthew Buckett, VLE Developer, IT Services, University of Oxford