jpdigital / hibernate5-ddl-maven-plugin Goto Github PK

View Code? Open in Web Editor NEW

22.0 22.0 16.0 1.92 MB

Maven plugin for creating SQL DDL files for applications which use Hibernate as JPA provider

License: GNU General Public License v3.0

Java 91.98% Groovy 8.02%

hibernate5-ddl-maven-plugin's People

Contributors

Stargazers

Watchers

Forkers

tavish zzsoszz codes-lab bade7n jwgmeligmeyling pado83 kamilchyc codefabrim fabqua mohsenr7596 fabio-bonfante arbormetrix ryansmith4 rosjle artipop deyang-li

hibernate5-ddl-maven-plugin's Issues

Add drop-create support

Hi all,

I could not find the support for drop first statements.
I use them for idempotency.

Thank you a lot

scale, precision or @Size for numeric types (ORACLE DIALECTS)

I can't make @column properties for defining numbers length to work.
I tried both scale, precision or even length but it doesn't seems to work.
Also @SiZe annotation from javax.validation does not apply.
Im using only JPA annotations.

for exampe:

@Id
    @SequenceGenerator(name = "ROSURVEY_GEN",allocationSize = 1,sequenceName = "ROSURVEY_SEQ")
    @GeneratedValue(generator = "ROSURVEY_GEN",strategy = GenerationType.SEQUENCE)
    @Column(name = "IDSURVEY",scale = 18, nullable = false)
    @Size(max = 18)
    protected Long id;

does produces:

create table TABLE( IDSURVEY number(19,0) not null, .....

Tested with both ORACLE10G, ORACLE12C

Add @Size support

Hi all,

First thank you a lot since you were the only plugin to be at the same straightforward to configure and working flawlessly.

But I found out that the @SiZe attribute was not taken into account in the generation thus generating the default 255 varchar size.

Thank you for your help

Issue with two differentes persistence units inside the persistence.xml

I have two persistence units in my persistence.xml, each one with a different set of classes.

They were both configured with exclude-unlisted-classes=true in order to avoid hibernate to auto discover the entities, thus guaranteeing that each persistence unit have its own separate entities correctly recognized.

The plugin ignores this confugiration and generate one single DDL mixing both persistence unit classes.

Add org.hibernate.dialect.MySQL57Dialect

Please add the org.hibernate.dialect.MySQL57Dialect dialect.

persistence.xml is required but doc claims its optional

this is what i get when there is no persistance.xml
note inconsistency of log vs. error.

...
[INFO] persistence.xml available, locking for properties...
[ERROR] Failed to open persistence.xml. Not processing properties.
java.io.FileNotFoundException: D:\DEV\CODE\trunk\src\main\resources\META-INF\persistence.xml (The system cannot find the path specified)
        at java.io.FileInputStream.open0(Native Method)```

Add org.hibernate.dialect.Oracle12cDialect

Please add the org.hibernate.dialect.Oracle12cDialect dialect.

Pass persistence properties as plugin properties

I use spring boot and there is no persistence.xml file. So instead of getting the properties from this file, which I had to artificially create, could we just pass these properties directly in the plugin?

Plugin availability

When this plugin will be available in Maven?

threeten not present error

When I run mvn install with this plugin

Execution default of goal de.jpdigital:hibernate54-ddl-maven-plugin:2.3.0:gen-ddl failed: Type org.threeten.bp.LocalTime not present

TypeDef Annotations in package-info.java are ignored

Hibernate allows the definition of user defined types. To use them the annotation @Type is used, either with the fully qualified name of the type class or a short name. This short name can be defined using the @TypeDef in the package-info.java of the package containing the user type. The plugin ignores the package-info.java file at the moment.

@SequenceGenerator allocationSize not considered when generating DDL

I am simply using the plugin as:

<plugin>
    <groupId>de.jpdigital</groupId>
    <artifactId>hibernate54-ddl-maven-plugin</artifactId>
    <version>2.3.0</version>
    <configuration>
        <dialects>
            <param>POSTGRESQL9</param>
        </dialects>
        <packages>
            <param>com.corp.proj.pack.data.entity</param>
        </packages>
        <outputFileNamePrefix>create_</outputFileNamePrefix>
    </configuration>
    <executions>
        <execution>
            <goals>
                <goal>gen-ddl</goal>
            </goals>
            <phase>process-classes</phase>
        </execution>
    </executions>
</plugin>

and I am having the entity defined as:

@MappedSuperclass
public abstract class AbstractEntity implements Serializable
{
    @Id
    @SequenceGenerator(name = "my_id_gen", sequenceName = "my_id_sequence", initialValue = 200, allocationSize = 100)
    @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "my_id_gen")
    @Column(name = "id", updatable = false, nullable = false)
    private long id;
}

but the DDL generated by the plugin does not take the allocationSize into account and generate the following DDL:

create sequence my_id_sequence start 1 increment 1;

which causes an exception at runtime:

org.hibernate.MappingException: The increment size of the [my_id_sequence] sequence is set to [100] in the entity mapping while the associated database sequence increment size is [1].

Is this a bug in the plugin that is does not consider the allocationSize or am I missing any configuration to get this generated correctly?

[Feature Request] Use custom name strategy

Any way to use custom name strategy with plugin?

persistence.xml is not optional as documented

When persistence.xml is not found, the following error occurs:
java.io.FileNotFoundException: src\main\resources\META-INF\persistence.xml (The system cannot find the file specified)

The documentation says: If the file is not present it is ignored.

Update and support hibernate V 5.3 And Java 9

Please update To support hibernate 53 and java 9 and later
in java 9 this error occurred
javax.xml.bind not found exception

im solve this to add dependency to plugin

javax.xml.bind
jaxb-api
2.3.0

com.sun.xml.bind
jaxb-core
2.3.0.1

com.sun.xml.bind
jaxb-impl
2.3.0.1

javax.activation
javax.activation-api
1.2.0

please keep alive project

Add org.hibernate.dialect.DerbyTenSevenDialect

Please add the org.hibernate.dialect.DerbyTenSevenDialect dialect.

Plugin fails if we have a custom dialect but not a dialect

The plugin fails if we had the a custom dialect but we don't had the dialect parameter.
A NPE is thrown

omitDialectFromFileName does not work if customDialect is used

If we have a customDialect being used it's not possible to omit the Dialect from the name file. We keep having it added to the file name

How to configure plugin for use with model classes under src/test/java ?

I have a need to use this plugin only during tests. I have some model classes (under src/test/java) that are only used for testing, and want to generate DDL on them prior to running the tests so that some unit tests can test some automated query generation stuff.

It's not clear that this is possible with this plugin; or, if it is possible, it's not documented anywhere.

I tried configuring <phase>process-test-classes</phase> but that didn't work - nothing was generated because apparently the plugin is still looking under src/main/java for source files.

I see that it's possible and documented to generate DDL for tests based on src/main/java classes, but I don't want my test model classes to be in the main JAR; they are only used for testing.

Thanks.

@Converter annotated classes are ignored

@converter annotated classes with autoapply = true are ignored, this affect sql for fields with converter that changes sql type. For example enums are mapped by default as int but my converter maps it to String.

I suppose that you have to change EntityFinder class to discover also @converter annotated classes and pass them to Hibernate.

I tried to annotate my converter with @entity (it is wrong, I know...), your plugin discovered it, and the sql was correct.

HikariCPConnectionProvider

HikariCPConnectionProvider let the build fail

persistence.xml:

error:

[ERROR] HikariPool-1 - dataSource or dataSourceClassName or jdbcUrl is required.

Failed to execute goal de.jpdigital:hibernate5-ddl-maven-plugin:1.0.1-hibernate-5.2.4.Final:gen-ddl (default-cli) on project auti-server: Execution default-cli of goal de.jpdigital:hibernate5-ddl-maven-plugin:1.0.1-hibernate-5.2.4.Final:gen-ddl failed: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]: java.lang.IllegalArgumentException: dataSource or dataSourceClassName or jdbcUrl is required.

Add support for Hibernate ORM 5.6

Hibernate 5.6 has been released (see https://in.relation.to/2021/10/13/hibernate-orm-560-final/). There should be a variant of the plugin depending on Hibernate 5.6.

Java9 required after 2.3.0+

I've noticed that "The plugin requires Java 8 or newer" while actually Java 9 is required. This is (at least) due to the usage of ClassLoader #getDefinedPackages() in EntityFinder.

My hopes are that you'll find a Java 8 substitute, but otherwise I guess just update the readme? =).

A shared @SequenceGenerator not found when referenced from other entities

On hibernate50-ddl-maven-plugin version 2.1.0-beta.1

We are using @SequenceGenerator and @GeneratedValue annotations like this:

@SequenceGenerator(name = "key_gen", sequenceName = "key_sequence")
public class SomeEntity {
    @Id
    @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "key_gen")
    private long key;

This works fine when the @SequenceGenerator is defined in the same entity class. However, when trying to reference the same generator by name from other entities when generating schemas using the plugin, the generator is not found. Perhaps the code is interpreted in such order that the @SequenceGenerator annotation has not been encountered yet when the plugin already tries to interpret the first @GeneratedValue annotation referencing it?

As a workaround we are currently defining a different generator for each entity that uses a generated primary key. We would like to share the same generator between multiple entities because it's simpler.

Plugin takes artifact from local repo instead of target/classes and generates empty script.

I have a single Maven module project.
If I run mvn install then generated resources are packaged and installed to local repo.
The second run of mvn install takes *.jar file from Local Repo and can see that postgresql9.sql presents and thus generates empty script in target/generated-resources.

gen-ddl fails after upgrade to 2.4.0

After upgrading hibernate54-ddl-maven-plugin (and hibernate55-ddl-maven-plugin) from 2.3.0 to 2.40 I get the following error when running the gen-ddl goal.

[INFO] Reactor Summary for tailormap 5.9.10-SNAPSHOT:
[INFO] 
[INFO] tailormap .......................................... SUCCESS [  0.253 s]
[INFO] viewer-config-persistence .......................... FAILURE [  1.264 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  2.049 s (Wall Clock)
[INFO] Finished at: 2021-10-19T09:56:31+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal de.jpdigital:hibernate54-ddl-maven-plugin:2.4.0:gen-ddl (schema-export-main) on project viewer-config-persistence: Execution schema-export-main of goal de.jpdigital:hibernate54-ddl-maven-plugin:2.4.0:gen-ddl failed: Scanner SubTypesScanner was not configured -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal de.jpdigital:hibernate54-ddl-maven-plugin:2.4.0:gen-ddl (schema-export-main) on project viewer-config-persistence: Execution schema-export-main of goal de.jpdigital:hibernate54-ddl-maven-plugin:2.4.0:gen-ddl failed: Scanner SubTypesScanner was not configured
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
    at java.util.concurrent.FutureTask.run (FutureTask.java:264)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)
    at java.util.concurrent.FutureTask.run (FutureTask.java:264)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)
    at java.lang.Thread.run (Thread.java:829)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution schema-export-main of goal de.jpdigital:hibernate54-ddl-maven-plugin:2.4.0:gen-ddl failed: Scanner SubTypesScanner was not configured
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:148)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
    at java.util.concurrent.FutureTask.run (FutureTask.java:264)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)
    at java.util.concurrent.FutureTask.run (FutureTask.java:264)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)
    at java.lang.Thread.run (Thread.java:829)
Caused by: org.reflections.ReflectionsException: Scanner SubTypesScanner was not configured
    at org.reflections.Store.get (Store.java:39)
    at org.reflections.Store.getAllIncluding (Store.java:75)
    at org.reflections.Reflections.getAllAnnotated (Reflections.java:469)
    at org.reflections.Reflections.getTypesAnnotatedWith (Reflections.java:430)
    at org.reflections.Reflections.getTypesAnnotatedWith (Reflections.java:416)
    at de.jpdigital.maven.plugins.hibernate5ddl.EntityFinder.findEntities (EntityFinder.java:264)
    at de.jpdigital.maven.plugins.hibernate5ddl.GenerateDdlMojo.execute (GenerateDdlMojo.java:192)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
    at java.util.concurrent.FutureTask.run (FutureTask.java:264)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)
    at java.util.concurrent.FutureTask.run (FutureTask.java:264)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)
    at java.lang.Thread.run (Thread.java:829)
[ERROR] 
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :viewer-config-persistence

apparently this originates in ronmamo/reflections#273 which was reported fixed with version 0.10. I tried forcing this newer version (both 0.10.0 as well as 0.10.1) as a plugin dependency, however there are API incompatibilities so it ends up in a runtime error. Downgrading to something before 0.9.12 (

hibernate5-ddl-maven-plugin/pom.xml

Line 140 in 7fc0466

) also fails in API incompatibilities.

Any chance you can release a version with a fix version of org.reflections:reflections?

reproducer is available in B3Partners/tailormap#2905

`useEnvers` not available as configuration anymore

On the documentation site (http://jpdigital.github.io/hibernate5-ddl-maven-plugin/usage.html) following configuration is proposed to enable envers:

<configuration>
  <dialects>
    <param>postgresql9</param>
  </dialects>
  <useEnvers>true</useEnvers>
  <packages>
    <param>org.example.entities</param>
  </packages>
</configuration>

But looking at GenerateDdlMojo there is no useEnvers parameter. How can i enable schema generation with envers?

DDL generation fails when cache region factory cannot be found on class path

When my persistence.xml contains the following caching configuration:

      <property name="hibernate.cache.use_second_level_cache" value="true" />
      <property name="hibernate.cache.use_query_cache" value="true" />
      <property name="hibernate.cache.infinispan.statistics" value="true"/>
      <property name="hibernate.cache.region.factory_class" value="org.hibernate.cache.infinispan.InfinispanRegionFactory"/>
      <property name="hibernate.transaction.factory_class" value="org.hibernate.transaction.JTATransactionFactory"/>
      <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
      <property name="hibernate.cache.infinispan.cfg" value="infinispan-config.xml"/>

The DDL generation fails with:

[ERROR] Failed to execute goal de.jpdigital:hibernate52-ddl-maven-plugin:2.0.4:gen-ddl (default-cli) on project domain: Execution default-cli of goal de.jpdigital:hibernate52-ddl-maven-plugin:2.0.4:gen-ddl failed: Unable to create requested service [org.hibernate.cache.spi.RegionFactory]: Unable to resolve name [org.hibernate.cache.infinispan.InfinispanRegionFactory] as strategy [org.hibernate.cache.spi.RegionFactory] -> [Help 1]

It was quite easy to workaround as I could temporarily disable caching for DDL generation, plus that it is possible to specify the persistence.xml configuration file that should be used. Nevertheless it got me wondering, perhaps the plugin should construct the persistence.xml on its own using the provided package?

Allow configurable output file

Currently in core the SQL file generation is based off of the dialect chosen:

return Paths.get(String.format(
            "%s/%s.sql", dirPath, dialect.name().toLowerCase(Locale.ENGLISH)));

It would be nice to have this configurable via a property. Something like:

@Parameter(required = false)
private String outputFileName;

If not provided then you'd use the dialect name as is and continue to support multiple dialect generations but the presence of the property would allow for single-dialect cases where we want to generate a specific file (for example Spring folk would use this to generate a data.sql file on the classpath).

Thoughts?

"cascade" property of @OneToMany and @ManyToOne is not reflected in SQL

Maybe this is more like a question than a bug. But I realized that the "cascade" property of @OneToMany and @manytoone is not reflected in the SQL statements.

I'm using Apache Derby 10.13 and currently I'm using the DB2 dialect as the hibernate5-ddl-maven-plugin doesn't support Derby natively yet (see issue #6). I have specified CascadeType.ALL in both cases and would have expected - as the standard ON DELETE and ON UPDATE action is NO ACTIONS (see CONSTRAINTS clause - Referential actions) - would be ON UPDATE CASCADE ON DELETE CASCADE.

Maybe my expectation is just wrong. Or maybe the current situation only exists because there is no native Derby support in the plugin.

Support for Jakarta EE

Please consider supporting Jakarta EE Persistence with the new namespace for entities jakarta.persistence.Entity, because at the moment only entities of the old namespace javax.persistence.Entity are supported.

How can I specify *.hbm.xml mapping files?

I'm working in a project with an (unfortunate) mix of JPA annotations, Hibernate annotations, and hbm.xml mapping files. It's a Spring Boot application and we specify the locations of the mapping files (in directory/src/main/resources/hibernate/) via the spring.jpa.mapping-resources config property. Hibernate generates the DB schema for all the annotated entities and mapping files at runtime.
But when I run the hibernate54-ddl:gen-ddl maven goal, it only includes SQL for the annotated entity classes, ignoring the mapping files. Does the plugin support xml mapping files, and if so, how can I tell it where to find them?

Getting UnmarshalException

When I try to generate the schema, I get:

Caused by: javax.xml.bind.UnmarshalException: unexpected element (uri:"http://www.hibernate.org/xsd/orm/hbm", local:"hibernate-mapping"). Expected elements are <{}hibernate-mapping>
    at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.handleEvent (UnmarshallingContext.java:741)
    at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError (Loader.java:262)
    at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError (Loader.java:257)
    at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportUnexpectedChildElement (Loader.java:124)
    at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext$DefaultRootLoader.childElement (UnmarshallingContext.java:1149)
    at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext._startElement (UnmarshallingContext.java:574)
    at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.startElement (UnmarshallingContext.java:556)
    at com.sun.xml.bind.v2.runtime.unmarshaller.InterningXmlVisitor.startElement (InterningXmlVisitor.java:75)
    at com.sun.xml.bind.v2.runtime.unmarshaller.StAXEventConnector.handleStartElement (StAXEventConnector.java:261)
    at com.sun.xml.bind.v2.runtime.unmarshaller.StAXEventConnector.bridge (StAXEventConnector.java:130)
    at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0 (UnmarshallerImpl.java:460)
    at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal (UnmarshallerImpl.java:435)
    at org.hibernate.boot.jaxb.internal.AbstractBinder.jaxb (AbstractBinder.java:171)
    at org.hibernate.boot.jaxb.internal.MappingBinder.doBind (MappingBinder.java:61)
    at org.hibernate.boot.jaxb.internal.AbstractBinder.doBind (AbstractBinder.java:102)
    at org.hibernate.boot.jaxb.internal.AbstractBinder.bind (AbstractBinder.java:57)
    at org.hibernate.envers.boot.internal.AdditionalJaxbMappingProducerImpl$1.addDocument (AdditionalJaxbMappingProducerImpl.java:92)
    at org.hibernate.envers.configuration.internal.EntitiesConfigurator.configure (EntitiesConfigurator.java:111)
    at org.hibernate.envers.boot.internal.EnversServiceImpl.doInitialize (EnversServiceImpl.java:154)
    at org.hibernate.envers.boot.internal.EnversServiceImpl.initialize (EnversServiceImpl.java:118)
    at org.hibernate.envers.boot.internal.AdditionalJaxbMappingProducerImpl.produceAdditionalMappings (AdditionalJaxbMappingProducerImpl.java:99)
    at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete (MetadataBuildingProcess.java:288)
    at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.build (MetadataBuildingProcess.java:83)
    at org.hibernate.boot.internal.MetadataBuilderImpl.build (MetadataBuilderImpl.java:418)
    at org.hibernate.boot.internal.MetadataBuilderImpl.build (MetadataBuilderImpl.java:87)
    at org.hibernate.boot.MetadataSources.buildMetadata (MetadataSources.java:179)
    at de.jpdigital.maven.plugins.hibernate5ddl.DdlGeneratorHibernate52.generateDdl (DdlGeneratorHibernate52.java:95)
    at de.jpdigital.maven.plugins.hibernate5ddl.DdlGeneratorHibernate52.generateDdl (DdlGeneratorHibernate52.java:132)
    at de.jpdigital.maven.plugins.hibernate5ddl.GenerateDdlMojo.execute (GenerateDdlMojo.java:168)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:134)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:564)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)

but I do not have XML files with that namespace anywhere. Did anyone ever get into this problem?