custom dialect class not found about liquibase-hibernate

[jgribonvald]

expect this problem the diff generation using hbm2dll is working with liquibase 3.4.0-snapshot and adding this dependency :

                    <dependency>
                        <groupId>xml-apis</groupId>
                        <artifactId>xml-apis</artifactId>
                        <version>1.4.01</version>
                    </dependency>

[nvoxland]

Can you describe the problem you are trying to solve and what your suggestion is a bit better. Maybe with some examples?

[jgribonvald]

I'm using a custom dialect of MySQL which add ROWTYPE=COMPRESSED after
ENGINE INNODB, but running the tool with the class of my custom dialect in
the classpath isn't found (Class not found error as i specify my custom
class dialect). With Hibernate we have only to specify the class and it
works very well.

2014-11-21 21:52 GMT+01:00 Nathan Voxland [email protected]:

Can you describe the problem you are trying to solve and what your
suggestion is a bit better. Maybe with some examples?

—
Reply to this email directly or view it on GitHub
#67 (comment)
.

[nvoxland]

OK. And the problem is that your class or one of it's dependencies is using the xml-apis, but Liquibase doesn't declare it as a dependency. If you add the xml-apis dependency to your pom it works and you would like it added to the main liquibase-hibernate pom?

[jgribonvald]

Not totaly, it works only if i add as dependency in the plugin my custom
class after packaging and installing it as a jar. Also maybe it's the maven
target that should evolve. The xml-api was needed in complement, but can't
remember which error i've got to place it (i think it was due to in
incompability with serveral version of jar like xerces, java...).

If you want to look, i can provide you the link of my project on github.

2014-11-25 17:35 GMT+01:00 Nathan Voxland [email protected]:

OK. And the problem is that your class or one of it's dependencies is
using the xml-apis, but Liquibase doesn't declare it as a dependency. If
you add the xml-apis dependency to your pom it works and you would like it
added to the main liquibase-hibernate pom?

—
Reply to this email directly or view it on GitHub
#67 (comment)
.

[nvoxland]

Yes, if you could send me a link to help reproduce the problem that would be a big help.

[jgribonvald]

Ok so :
https://github.com/GIP-RECIA/esup-publisher-api.git
and go on devs-api branch

So to works i need to run 'mvn install -Dmaven.test.skip=true' before 'mvn
compile liquibase:generateChangeLog'

After i don't know if it will work for you as I don't have same versions
now of liquibase-maven-plugin 3.4.0-SNAPSHOT (core version mainly)
and liquibase-hibernate4 3.5-SNAPSHOT
mhhh here are last commit for theses libs :
liquibase : 51b83c8 Merge pull request #326 from
mattbertolini/bug/ref-connection-props (4 weeks ago)
liquibase-hibernate : 6dd34f6 #58 Max unique constraint length ignored with
this patch : https://github.com/liquibase/liquibase-hibernate/pull/69/files

For note i modified some generated data, but nothing really important.

[tomhughesnice]

Has any progress been made on this issue as im having exactly the same problem.
Using Liquibase maven plugin version 3.4.1 with liquibase hibernate 4 version 3.5

I am using a Postgres database, connecting with hibernate. I have had to create my own Dialect class to handle Postgres's 'JSONB' type.
I have updated the particular line in the maven plugin
<referenceUrl>hibernate:spring:com.fieldmargin.fm.core.domain?dialect=com.fieldmargin.fm.core.config.dialect.JsonPostgreSQLDialect</referenceUrl>
But I always get a class not found exception when trying to load the dialect.

Its strange as I can see in the liquibase debug the classpath is being loaded, and the Dialect class I created is in there. So there must be a bug in the Liquibase class loader for the dialect.

The work around above gets me past this issue. I have to run a Maven install, and make the produced artifact a dependancy of the liquibase plugin. Would be good to get a proper fix though.

[nvoxland]

The next version (3.6) should be reading the dialect correctly from your hibernate configuration file. You shouldn't need to specify the dialect in the connection url. But you can if you need to