Currently fails in Travis CI: ERROR: Error during SonarQube Scanner execution org.sonar.java.AnalysisException: You are not using the latest JaCoCo binary format version, please consider upgrading to latest JaCoCo version. at org.sonar.plugins.jacoco.JacocoReportReader.checkCurrentReportFormat(JacocoReportReader.java:87) at org.sonar.plugins.jacoco.JacocoReportReader.<init>(JacocoReportReader.java:49) at org.sonar.plugins.jacoco.UnitTestAnalyzer.readExecutionData(UnitTestAnalyzer.java:122) at org.sonar.plugins.jacoco.UnitTestAnalyzer.analyse(UnitTestAnalyzer.java:95) at org.sonar.plugins.jacoco.JaCoCoSensor.execute(JaCoCoSensor.java:77) at org.sonar.scanner.sensor.SensorWrapper.analyse(SensorWrapper.java:45) at org.sonar.scanner.phases.SensorsExecutor.execute(SensorsExecutor.java:88) at org.sonar.scanner.phases.SensorsExecutor.execute(SensorsExecutor.java:62) at org.sonar.scanner.phases.AbstractPhaseExecutor.execute(AbstractPhaseExecutor.java:74) at org.sonar.scanner.scan.ModuleScanContainer.doAfterStart(ModuleScanContainer.java:164) at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:136) at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:122) at org.sonar.scanner.scan.ProjectScanContainer.scan(ProjectScanContainer.java:319) at org.sonar.scanner.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:314) at org.sonar.scanner.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:312) at org.sonar.scanner.scan.ProjectScanContainer.doAfterStart(ProjectScanContainer.java:288) at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:136) at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:122) at org.sonar.scanner.task.ScanTask.execute(ScanTask.java:48) at org.sonar.scanner.task.TaskContainer.doAfterStart(TaskContainer.java:82) at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:136) at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:122) at org.sonar.scanner.bootstrap.GlobalContainer.executeTask(GlobalContainer.java:131) at org.sonar.batch.bootstrapper.Batch.doExecuteTask(Batch.java:116) at org.sonar.batch.bootstrapper.Batch.executeTask(Batch.java:111) at org.sonarsource.scanner.api.internal.batch.BatchIsolatedLauncher.execute(BatchIsolatedLauncher.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.sonarsource.scanner.api.internal.IsolatedLauncherProxy.invoke(IsolatedLauncherProxy.java:60) at com.sun.proxy.$Proxy0.execute(Unknown Source) at org.sonarsource.scanner.api.EmbeddedScanner.doExecute(EmbeddedScanner.java:233) at org.sonarsource.scanner.api.EmbeddedScanner.runAnalysis(EmbeddedScanner.java:151) at org.sonarsource.scanner.cli.Main.runAnalysis(Main.java:123) at org.sonarsource.scanner.cli.Main.execute(Main.java:77) at org.sonarsource.scanner.cli.Main.main(Main.java:61)

https://nvd.nist.gov/vuln/detail/CVE-2018-9159

__LiquigraphLock is left in place whenever migration / changset fails.

Here's an excerpt from the log: ``` Cannot remove __LiquigraphLock during cleanup.

java.sql.SQLException: org.neo4j.driver.v1.exceptions.ClientException: Cannot run more statements in this transaction, because previous statements in the transaction has failed and the transaction has been rolled back. Please start a new transaction to run another statement. at org.neo4j.jdbc.bolt.BoltNeo4jPreparedStatement.executeInternal(BoltNeo4jPreparedStatement.java:105) ~[neo4j-jdbc-driver-3.3.1.jar!/:na] at org.neo4j.jdbc.bolt.BoltNeo4jPreparedStatement.execute(BoltNeo4jPreparedStatement.java:77) ~[neo4j-jdbc-driver-3.3.1.jar!/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0181] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0181] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0181] at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0181] at org.neo4j.jdbc.utils.Neo4jInvocationHandler.invoke(Neo4jInvocationHandler.java:54) ~[neo4j-jdbc-driver-3.3.1.jar!/:na] at com.sun.proxy.$Proxy223.execute(Unknown Source) ~[na:na] at org.liquigraph.core.io.lock.LiquigraphLock.releaseLock(LiquigraphLock.java:123) [liquigraph-core-3.0.2.jar!/:na] at org.liquigraph.core.io.lock.LiquigraphLock.release(LiquigraphLock.java:54) [liquigraph-core-3.0.2.jar!/:na] at org.liquigraph.core.io.lock.LockableConnection.close(LockableConnection.java:103) [liquigraph-core-3.0.2.jar!/:na] at org.liquigraph.core.api.MigrationRunner.runMigrations(MigrationRunner.java:81) [liquigraph-core-3.0.2.jar!/:na] at org.liquigraph.core.api.Liquigraph.runMigrations(Liquigraph.java:63) [liquigraph-core-3.0.2.jar!/:na] at org.liquigraph.spring.SpringLiquigraph.afterPropertiesSet(SpringLiquigraph.java:52) [liquigraph-spring-boot-starter-3.0.2.jar!/:na] at ```

To reproduce this, create changeset that fails (for example, create an invalid query).

This was observed in a Spring Boot application, using org.liquigraph:liquigraph-spring-boot-starter:3.0.2.

Following a discussion here, I think it could be a good idea to implement a task to remove the entire Liquigraph history and constraints/indices if something goes wrong.

This task is quite destructive, so it should probably be guarded with a confirmation ask (and a --force flag for automation).

It's probably worth it to port this task to the 2.x branch as well.