-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
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
Externalize providers for PostgreSQL and Oracle to separate jars #20
Comments
I propose to do this when every feature (create template, delete template, create database instance, delete database instance) will work. |
You can externalize providers without making OSGI modules. Just create some Maven submodules and add dependencies. In that way you will have good separation from start and it will be easier to refactor in future. |
Yesterday I made an example PostgreSQL plugin. I pushed it in a branch but I think not to GitHub 🤣. I repush it today. |
Code for database providers (that uses native jdbc to create databases) should be externalized to separate jars. That's because those jars should became OSGi plugins in future.
Mind you that Cascades own persistence (Hibernate+PostgreSQL) shouldn't be moved. It's two separate things.
The text was updated successfully, but these errors were encountered: