We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split the project in several maven modules (and jars). It would allow an easier reuse of the different parts of Mirage SQL, and also easier to extend.
E.g. there's stuff not needed at runtime, or not by everybody, but still gets deployed since it's there in the same JAR:
and other parts that would be reusable outside of Mirage like:
The text was updated successfully, but these errors were encountered:
+1 Maybe this would make it easier to provide implementations for other languages too.
Sorry, something went wrong.
+1
This would be easier if the build would be migrated to Gradle.
For now the project was split in:
miragesql-2.1.0.jar
miragesql-test-2.1.0.jar
miragesql-integration-2.1.0.jar
aadrian
No branches or pull requests
Split the project in several maven modules (and jars).
It would allow an easier reuse of the different parts of Mirage SQL, and also easier to extend.
E.g. there's stuff not needed at runtime, or not by everybody, but still gets deployed since it's there in the same JAR:
and other parts that would be reusable outside of Mirage like:
The text was updated successfully, but these errors were encountered: