Upgrade com.liferay.dynamic.data.mapping.service module to 1.0.0 fails when DDLRecords exist

• Type: Bug
• Status: Closed
• Resolution: No Longer Reproducible
• Affects Version/s: 7.0.0 Beta 4
• Fix Version/s: 7.0.0 Beta 6
• Component/s: Dynamic Data Mapping, Dynamic Data Mapping > Upgrades
• Labels: None
• Fix Priority: 3
• Sprint: Sprint 10: Feb, 01 - Feb, 19

Steps to Reproduce

1. Startup 6.2 GA6 and create a Dynamic Data List Recordset and add a new Record
2. Shutdown 6.2 GA6
3. In a liferay 7 server, create a file called com.liferay.portal.upgrade.internal.configuration.ReleaseManagerConfiguration.cfgin osgi/configs/ folder with the following content

   autoUpgrade=false
   

4. Add the following property to the portal-ext.properties:

   upgrade.processes.6205==${upgrade.processes.master}
   

5. Start an upgrade against the Liferay 6.2 database by using the stand-alone upgrade tool:

   ./run.sh --classpath $TOMCAT_DIR/lib,$TOMCAT_DIR/lib/ext,$TOMCAT_DIR/webapps/ROOT/WEB-INF/lib --liferay_home $LRHOME_DIR
   

6. Once the core upgrades, connect to GoGo console:

   telnet localhost 11311
   

7. Execute the following command:

   upgrade:execute com.liferay.dynamic.data.mapping.service
   

8. You will get the following exception:

   gogo: RuntimeException: com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.exception.PortalException: com.liferay.portal.kernel.xml.DocumentException: Error on line 1 of document  : Content is not allowed in prolog. Nested exception: Content is not allowed in prolog.