Esup-News Portlet - Migration Guide
Autors : Julien Gribonvald
Important note
This page explain only specific parts useful for migrations from an old version !
Migration
From NewsPortlet 2.0.6 and upper to Esup-News 0.2.X
Updating the database
- select the script of you version for the update in build.properties with property db.filename
# Make your choice on the good script to update your database, please uncomment/comment only db.filename=update_mysql_newsPortlet-2.0.x_to_esup-news-0.2.0.sql #db.filename=update_mysql_2.0.6_to_2.1.0.sql #db.filename=update_mysql_2.1.0_to_2.2.0.sql #db.filename=update_postgresql_newsPortlet-2.0.x_to_esup-news-0.2.0.sql
By default the good script is selected, if you have a MySQL database, else if you have a PostgreSQL database comment the uncommented line and uncomment this line : db.filename=update_postgresql_newsPortlet-2.0.x_to_esup-news-0.2.0.sql.
The PostgreSQL script migration wasn't tested, it's sure there will be one problem, you will need to deactivate constraints checking before to pass the script.
Please contact us if you have problems or to share your tips to solve this problem.
- run ant db-update after configuring databases configuration in build.properties
Replacing NewsPortlet by Esup-News in the portal
- In the channel manager of the portal go on "Modify a currently published channel" and modify the channel of your NewsPortlet. You will have only to modify the property Portlet definition ID to <app.name>.news, where <app.name> is setted in build.properties