Maven Plugin does not use outputDefaultCatalog property

Hi,
I think I found a problem in the Maven Plugin. It does not seem to use the prameters outputDefaultCatalog or outputDefaultSchema.

If I run the command line tool like this:

java -jar liquibase-core-3.1.1.jar --defaultsFile=db\conf\liquibase-reverse-engineer.properties  --classpath=ojdbc6-11.2.0.2.0.jar --changeLogFile=/target/export_changelog.xml generateChangeLog

Using the following properties file:

driver=oracle.jdbc.driver.OracleDriver
url=jdbc:oracle:thin:@localhost:1521:xe
username=userxy
password=xxx
outputDefaultCatalog=false
outputDefaultSchema=false

I will get a changelog file that hat no “catalogName” XML attribute in the generated XML (this is the behavior I would expect from the outputDefaultCatalog property, btw I think that these properties are not used at all by the CLI tool).
e.g.:
   
       
   

But if I run the generateChangeLog goal of the Maven plugin with the same properties file, every tag has a “catalogName” XML attribute.

   
       
   

Am I doing something wrong here? Is the outputDefaultCatalog property not used to control the generation of the “catalogName” XML attribute? I dont want the catalogName in my changelog to be able to use it for a database with a different schema and catalog for testing.

Here my Maven setup:

               
                   
                        org.liquibase
                        liquibase-maven-plugin
                        3.1.1


                       
                           
                                generateChangeLog execution
                                process-resources
                               
                                    generateChangeLog
                               

                               
                                    true
                                    db/conf/liquibase-reverse-engineer.properties
                                    ${user.name}
                                    ${project.build.directory}/data
                                    ${project.build.directory}/db.changelog-${project.version}.xml
                                    false
                                    false
                               
                           
                       
                   
               
           

Best regards,
Christian

Thanks for the report. I created https://liquibase.jira.com/browse/CORE-1748 to track the issue.


Nathan