Emend POM.XML to specify net.sourceforge.schemaspy.Main as the main JAR class #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… is called from external frameworks for multiple schemas
…e property from plugin configuration
…pe.org/browse/OSSRH-1477); specify net.sourceforge.schemaspy.Main as the main class in the JAR file in order to process multiple schemas successfully
|
This pull request relates to Issue #1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, using the plugin fails with multiple schemas for 2 reasons:-
the generated command-lines reference the wrong JAR file, simply being the first JAR file in the classpath
the generated command-lines do not specify the class to invoke and the generated JAR file does not specify net.sourceforge.schemaspy.Main as the main JAR class and so is not invoked.
This change corrects the second problem: it is upstream compatible - BUT
The groupId has been changed to reflect the change described in https://issues.sonatype.org/browse/OSSRH-1477