Drop the hibernate3-maven-plugin in favor of providing direct support for database schema drop+create
Description
The NewsReader portlet implements a 'db-init' Maven goal that drops & re-creates the database schema. This capability is integrated into the uP4 Maven build via uportal-portlets-overlay.
The current implementation is based on the hibernate3-maven-plugin. This solution is problematic because (1) it's not well integrated into the rest of the app's features (so it's always been very brittle), and (2) it doesn't port well to the Gradle-based build in uP5.
We need to replace it with something we provide directly that is a first-class part of the Spring app.
Major
The NewsReader portlet implements a 'db-init' Maven goal that drops & re-creates the database schema. This capability is integrated into the uP4 Maven build via uportal-portlets-overlay.
The current implementation is based on the hibernate3-maven-plugin. This solution is problematic because (1) it's not well integrated into the rest of the app's features (so it's always been very brittle), and (2) it doesn't port well to the Gradle-based build in uP5.
We need to replace it with something we provide directly that is a first-class part of the Spring app.