VIVO-1478 mysql driver throws exception

[j2blake]

Thank you for submitting a pull request! Title this pull request with a brief description of what the pull request fixes/improves/changes. Please describe the pull request in detail using the template below.

---

JIRA Issue: https://jira.duraspace.org/browse/VIVO-1478

• Other Relevant Links (Mailing list discussion, related pull requests, etc.)

What does this pull request do?

Upgrading to a newer MySQL driver caused an exception unless serverTimezone was specified in the JDBC URL. This request causes VIVO to specify serverTimeZone=UTC as a default option on the URL. It also uses the most recent version of the MySQL driver.

What's new?

• Changes mysql-connector-java artifact from version 6.0.6 (February, 2017) to version 5.1.46 (April, 2018)

How should this be tested?

• To reproduce the problem,
  • Install VIVO
  • Start VIVO
  • Observe InvalidConnectionAttributeException in the log
  • VIVO presents a fatal error page
• To test the fix,
  1. user provides no options on JDBC URL
     • Merge the fix, repeat installation and start VIVO
     • Log contains no InvalidConnectionAttributeException
     • VIVO operates normally
  2. user provides options on JDBC URL
     • As above, but add an innocuous option to the JDBC URL in runtime.properties
       • e.g., VitroConnection.DataSource.url = jdbc:mysql://localhost/vitrodb?useUnicode=yes
     • Start VIVO
     • Log contains no InvalidConnectionAttributeException
     • VIVO operates normally

Interested parties

@VIVO-project/vivo-committers

[grahamtriggs]

Needs the ampersand at the start to separate the additional parameter.

[j2blake]

(facepalm)
Ouch. Fixed error, updated test procedure.

[gneissone]

Per developer call discussion today, switch to using mysql-connector-java version 5.1.46.

[roflinn]

Approved