wakaleo / maven-schemaspy-plugin Goto Github PK

The LICENSE.txt file contains the MIT license text, but the POM file lists the Apache license. Please clarify which is the correct license of the project to avoid confusion.

Hi,

I'm getting a 404 Not Found page when trying to open the referenced site of the plugin:
http://maven.wakaleo.com/mojo/maven-schemaspy-plugin

greetings
Riggs

Hello, when using site:staging maven target the output folder used my maven-schemaspy-plugin remains the default site output, so the menu entry link is broken.
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:

public String getOutputName() {
    return "schemaspy/index";
}

Please publish the project's Maven site somewhere and/or make it accessible by everyone. The link in the project description gives "403 Forbidden".

By the way, you can easily host the Maven site on Github using Gitub pages. This basically means to create an orphan branch named "gh-pages", commit the generated site in that branch and push it to Github. The page then would become available at http://wakaleo.github.io/maven-schemaspy-plugin.

The groupId in the pom.xml (and presumably that requested from Sonatype) was com.wakaleo.schemaspy: it was changed to com.wakaleo
OSSRH Ticket

This might cause deployment problems.

Hello,
I started using your plugin to integrate schemaspy doc to my maven site.
It works great for one schema, but I cannot use it for several schemas at a time.
I navigated in this plugin sources and schemaspy sources to found it out.
The issue is that when -schemas parameter is passed to schemaspy, MultipleSchemaAnalyzer will be called to create a global index html page and generate the doc for each schema, to do so in fact, several command lines with -schema (without "s") are generated and ran but this generation step call Config.getLoadedFromJar() that assumes that schemaspy jar is the only one of the classpath thus doing :
public static String getLoadedFromJar() {
String classpath = System.getProperty("java.class.path");
return new StringTokenizer(classpath, File.pathSeparator).nextToken();
}

But under maven run, this call fetch the classworld.jar of maven,so all commandline generated are invalid.
I come to you hoping you may find a solution inside the plugin itself or can interact with the author of schemaspy about this.
Many Thanks.

We rely on using the "orathin_servicename" db type, which is not yet released and our build environment frowns upon using SNAPSHOT dependencies..

A release would be very much appreciated.

Change the artifact ID from maven-schemaspy-plugin to schemaspy-maven-plugin. During the build of the plugin, an error is displayed which explains the reason:

[ERROR] 

Artifact Ids of the format maven-___-plugin are reserved for 
plugins in the Group Id org.apache.maven.plugins
Please change your artifactId to the format ___-maven-plugin
In the future this error will break the build.