[forge-issues] [JBoss JIRA] (FORGEPLUGINS-54) Plugin to Database Migration Framework

[George Gastaldi (JIRA)]

     [ https://issues.jboss.org/browse/FORGEPLUGINS-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Gastaldi updated FORGEPLUGINS-54:
----------------------------------------

    Description: 
Recommend idea for adding a database change plugin. The Grails plugin for database changes (http://grails.org/plugin/database-migration) may be good for inspiration, however the Forge version may not necessarily have the tightly coupled support as the Grails/Groovy domain models have, but something that supports JPA would be fabulous.
Although a generic plugin for Liquibase or other database change management support could be useful, it would be left 'up to the developer' on how to use it which seems counter-intuitive to a more RAD-style development environment, per the specific of JPA-based data access (potentially OGM-based JPA as well).
Usecase is for solving how to deploy database structure changes in an automated fashion to ensure the database schema does not go out of sync with the application.

A Plugin like spring-roo-addon-flyway (http://code.google.com/p/spring-roo-addon-flyway/).

Could be other Database Migration API that works better on Jboss ecosystem (I dont know if that is one).

  was:
A Plugin like spring-roo-addon-flyway (http://code.google.com/p/spring-roo-addon-flyway/).
Culd be other Database Migration API that works better on Jboss ecosystem (I dont know if that is one).


    
> Plugin to Database Migration Framework
> --------------------------------------
>
>                 Key: FORGEPLUGINS-54
>                 URL: https://issues.jboss.org/browse/FORGEPLUGINS-54
>             Project: Forge Plugins
>          Issue Type: Feature Request
>            Reporter: Mauro Silva
>
> Recommend idea for adding a database change plugin. The Grails plugin for database changes (http://grails.org/plugin/database-migration) may be good for inspiration, however the Forge version may not necessarily have the tightly coupled support as the Grails/Groovy domain models have, but something that supports JPA would be fabulous.
> Although a generic plugin for Liquibase or other database change management support could be useful, it would be left 'up to the developer' on how to use it which seems counter-intuitive to a more RAD-style development environment, per the specific of JPA-based data access (potentially OGM-based JPA as well).
> Usecase is for solving how to deploy database structure changes in an automated fashion to ensure the database schema does not go out of sync with the application.
> A Plugin like spring-roo-addon-flyway (http://code.google.com/p/spring-roo-addon-flyway/).
> Could be other Database Migration API that works better on Jboss ecosystem (I dont know if that is one).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira