Migration Guide

Migrating from older versions of Mirage-SQL

Migrating from Mirage =<1.2.5 to 1.3.0

Mirge-SQL was moved to a new GitHub Organisation https://github.com/mirage-sql , so the artifacts were renamed from:

<dependency>
    <groupId>jp.sf.amateras</groupId>
    <artifactId>mirage</artifactId>
    <version>1.2.5</version>
</dependency>

and

compile 'jp.sf.amateras:mirage:1.2.5'

to:

<dependency>
    <groupId>com.miragesql</groupId>
    <artifactId>miragesql</artifactId>
    <version>1.3.0</version>
</dependency>

and

compile 'com.miragesql:miragesql:1.3.0'

Migrating from Mirage 1.3.0 to 2.0.x

1. Imports

Mirage-SQL sources were refactored to use the new Github Organization package name, so you have to change all you imports from:

import jp.sf.amateras.mirage.*;

to

import com.miragesql.miragesql.*;

2. Logging

Mirage-SQL was refactored to use https://www.slf4j.org/ instead of java.util.logging (JUL) . If your application is using JUL, you could migrate it to SLF4J as described https://www.slf4j.org/migrator.html

Note the logging levels between JUL and SLF4j:

FINEST  -> TRACE
FINER   -> DEBUG
FINE    -> DEBUG
CONFIG  -> INFO
INFO    -> INFO
WARNING -> WARN
SEVERE  -> ERROR

Migrating from Mirage 2.0.x to 2.1.x

Mirage-SQL monolitic JAR was split in several smaller JARs.

Take the following steps to to migrate your application:

• tbd