Hi Nathan,
I am currently trying to manage a Ingres-DB with liquibase and I run into the same problem. Seeing that there is an interrupt in communication in this thread, I just picking it :-).
I implemented a minimalistic class liquibase.database.ext.IngresDatabase and put it on the classpath:
Running "java -jar liquibase.jar --classpath=./bin:iijdbc_92.jar
--driver=com.ingres.jdbc.IngresDriver
--url="jdbc:ingres://__myconnection__" --username=__myuser__
--password=__mypassword__ --changeLogFile=first.xml --logLevel=debug
update"
- java -jar liquibase.jar --classpath=./bin:./iijdbc_92.jar
--driver=com.ingres.jdbc.IngresDriver
--url="jdbc:ingres://__myconnection__" --username=__myuser__
--password=__mypassword__ --changeLogFile=first.xml --logLevel=debug
update
- DEBUG 2/23/12 12:20 PM:liquibase: Unable to load/access Apache Derby driver class org.apache.derby.tools.sysinfo to check version: org.apache.derby.tools.sysinfo
WARNING 2/23/12 12:20 PM:liquibase: Unknown database: INGRES
Liquibase Update Failed: Unknown Reason
SEVERE 2/23/12 12:20 PM:liquibase: Unknown Reason
java.lang.NullPointerException
at liquibase.database.AbstractDatabase.rollback(AbstractDatabase.java:981)
at liquibase.integration.commandline.Main.doMigration(Main.java:835)
at liquibase.integration.commandline.Main.main(Main.java:133)
Why is derby involved at all? - I don't see a reference.
It seems that the class (located in bin/liquibase/database/ext) is not loaded. At least, I get the same error message when I execute the same without ./bin on the classpath.
Regards,
Simon