- This topic has 3 replies, 2 voices, and was last updated 10 years, 5 months ago by
.
-
Posts
-
I have a number of projects that I am trying to move from ME 10.7 to ME 2014 and have two problems going.
1) If I try to import the project from my SVN it throws all kinds of stuff when trying to run it in the integrated tomcat. That is another topic I am sure. To bypass this problem I am trying to just copy the whole workspace, which leads to #2.
2) If I copy the workspace and then open it with ME 2014, it does the migration and runs with minor setting changes. But if I edit any BIRT report in the project or create a new one and then try to execute the report in my application it throws an error set that starts like:
org.eclipse.birt.report.engine.api.EngineException: The design file file:/E:/Development/Projects/Java/xx/MyApp/.metadata/.me_tcat7/webapps/MyServ/reports/myReport.rptdesign has error and can not be run.
If I change the report version line from:
<report xmlns=”http://www.eclipse.org/birt/2005/design” version=”3.2.23″ id=”1″>
To version 3.2.22 then the report will run. The application does have BIRT enabled at the project level and I believe it embeds BIRT in the project somewhere.
I am assuming the BIRT in the project is not getting updated by the migration process, so I need to know how I get BIRT updated in the project to match what is installed in ME 2014?
Also, is there any kind of automated process for this to not have to do a manual upgrade with each ME upgrade?
Any help would be greatly appreciated.
mongonv,
Sorry that you are facing issues with MyEclipse.
Regarding running a report (created in MyEclipse 10.7.1) in MyEclipse 2014, I have filed a bug report for the dev team to investigate on this issue.
1) If I try to import the project from my SVN it throws all kinds of stuff when trying to run it in the integrated tomcat. That is another topic I am sure. To bypass this problem I am trying to just copy the whole workspace, which leads to #2.
Can you mention the detailed steps to help us replicate the issue at our end ? Please attach the screenshots of the issue to help us visualise the issue ? Also check the .log file which is located at <workspace dir>/.metadata/.log for any errors of interest. If any, please attach them as well.
Also, is there any kind of automated process for this to not have to do a manual upgrade with each ME upgrade?
Can you please be more clear on what exactly you are looking for ?
Sorry for the inconvenience caused.
On the upgrading of reporting, I have several projects with BIRT enabled as part of the project, but if I try to upgrade the ME and I edit any of the reports where they get saved with the new ME version of BIRT, the application cannot run them because the BIRT in the project does not get upgraded with the new version of ME.
If there was an automated option to update the BIRT of the project when it gets migrated to the new version of ME, it would eliminate having to do some kind of manual upgrade to BIRT, which is the immediate thing I have to do in order to upgrade ME.
In regards to what I really need in response to this post, is the process to upgrade my BIRT from ME 10.7 to ME 2014. This issue is what has prevented me from moving from ME 10.7 to 2013 or 2014, as the migration of ME projects does not upgrade the BIRT in the project.
On item #1, that will take some work to put together the specifics. I tried checking out my project from our SVN snapshot of the current 10.7 project and it threw a lot of errors when I tried to run it, so I just copied the whole workspace and let ME upgrade all the projects in the workspace. Having several dozen applications in ME, when its not an easy upgrade of a project, it means not upgrading ME cause I just don’t have the time to puzzle thru what the upgrade is not doing or has changed that needs reworked.
If you could provide the steps to upgrade BIRT in my projects, that would be the major item I have to have in order to upgrade my ME.
Thanks much
mongonv,
Thanks for the detailed explanation.
The only workaround we have so far is to manually change the project facets version and the BIRT jar files that are present in the lib folder.
Here are the steps that I followed and got the reports running in MyEclipse 2014. (To avoid confusion, the project that is migrated is referred as ‘OldReportProject’) :
1) Open ‘Navigator view’, expand the OldReportProject/.settings folder, open the file org.eclipse.wst.common.project.facet.core.xml and manually set the ‘birt.runtime’ version to 4.3.1. <installed facet=”birt.runtime” version=”4.3.1″/>
2) Take a backup of all the jar files located in OldReportProject/WEB-INF/lib folder. After taking the backup, delete all the jar files from OldReportProject/WEB-INF/lib folder.
3) Create a new report web project named ‘NewReportProject’ in MyEclipse 2014, copy all the content of NewReportProject/WEB-INF/lib folder and paste it in OldReportProject/WEB-INF/lib folder.
4) Go to the Eclipse BIRT site and download the runtime zip. Extract it out to a folder. Find the jar file : org.eclipse.birt.runtime_4.3.1.v20130918-1142.jar and copy paste it to OldReportProject/WEB-INF/lib folder. Click ‘Yes’ to replace the jar file.
5) Make sure the database drivers are added to the project lib folder. (You can copy paste them from the backup taken in step 2). For Example, if you are using ME derby database, you need to copy derby.jar and derbyclient.jar files to lib folder. Also, make sure you have added all the jar files that are needed for your project.
6) Redeploy the OldReportProject to MyEclipse Tomcat 7 (make sure you first remove the project from deployment and then deploy the project again).Let us know how this workaround works for you.
