Open mrpotes opened 12 years ago
This is really a bug that has been fixed in core maven - it can be fixed for your plugin by uplifting the maven-reporting-impl version to 2.2.
So to workaround this issue, you can do:
<plugin>
<groupId>com.wakaleo.schemaspy</groupId>
<artifactId>maven-schemaspy-plugin</artifactId>
...
<dependencies>
<dependency>
<groupId>org.apache.maven.reporting</groupId>
<artifactId>maven-reporting-impl</artifactId>
<version>2.2</version>
</dependency>
</dependencies>
</plugin>
Oh, this saved my day! Thanks!
I'm using the plugin to generate a report on a derby database, and the tables page has been overwritten by a generated by maven report type page. I think this is because when there's no schema, the table information is generated to schemaspy/index.html, but that is also where the AbstractMavenReport generates its output, because of the following in SchemaSpyReport: