Changes for page XcodeMigration

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,103 +1,43 @@
1		-{{toc}}{{/toc}}
	1	+= Introduction  =
2	2
3		-= Introduction =
	3	+XcodeMigration is a tool written by [[Pascal Robert>>~~probert:Home]]to help you migrate multiple WebObjects projects from Xcode to Eclipse/WOLips.  If you have complex or many projects to convert, this is the tool to use.  The tool is written in Java and is a Eclipse project, so you will need to import the project into Eclipse first (you need a functionnal WOLips installation to be able to import the tool). 
4	4
5		-XcodeMigration is a tool written by [[Pascal Robert>>~~probert]]to help you migrate multiple WebObjects projects from Xcode to Eclipse/WOLips.  If you have complex or many projects to convert, this is the tool to use.  The tool is written in Java and is a Eclipse project, so you will need to import the project into Eclipse first (you need a functionnal WOLips installation to be able to import the tool). 
6		-
7		-{{info title="Short video showing XCode project conversion"}}
8		-
9		-* [Converting XCode Projects to Eclipse Dev Tools|http://www.wocommunity.org/podcasts/Converting_Xcode_projects.mov]
10		-
11		-{{/info}}
12		-
13		-{{note}}
14		-XcodeMigration is using the tool _pbprojectdump_ which is no longer present in the Xcode 3 bundle. You need to install Xcode 2.5 to get access to _pbprojectdump_ (you can it over another machine too).
15		-
16		-{{/note}}
17		-
18	18	= How to use it =
19	19
20		-If you want to convert your Java classes from MacRoman to UTF-8, make sure your Eclipse workspace is in UTF-8 (the default is MacRoman).
	7	+* If you want to convert your Java classes from MacRoman to UTF-8, make sure your Eclipse workspace is in UTF-8 (the default is MacRoman).
	8	+* Make sure that you are in the WOLips perspective
	9	+* Download the tool (you don't need to expand the .zip file)
	10	+* Import the XcodeMigration tool into Eclipse, by selecting File > Import > Existings projects into workspace.  Next.  select archive
	11	+* Create two templates, one application, the other framework
	12	+* should see 3 projects
	13	+* open config.xml and change <applicationTemplatePath> and <frameworkTemplatePath>
	14	+* for each project that you want to import, you need the a <project> node.&nbsp; <path> is the file system path to the Xcode project, <name> is the project name, minus .xcodeproj
	15	+* open the Run dialog
	16	+* double-click on Java Application
	17	+* click on the arguments tab and enter this value as a program arguments&nbsp;
21	21
22		-{{panel align=center}}
	19	+{{code}}
23	23
24		-!Image 1.png!
25		-{panel}
26		-
27		-Make sure that you are in the WOLips perspective.
28		-
29		-!Image 6.png!
30		-
31		-!Image 7.png!
32		-
33		-[Download the tool|^XcodeMigration.zip] (you don't need to expand the .zip file)
34		-
35		-Import the XcodeMigration tool into Eclipse, by selecting _File_ \-> _Import_.&nbsp;&nbsp;&nbsp;&nbsp;
36		-
37		-!Image 2.png!
38		-
39		-Select _Existings Projects into Workspace_ and click _Next_.
40		-
41		-!Image 3.png!
42		-
43		-Select the location of the ZIP file with the tool and click _Finish_.
44		-
45		-!Image 4.png!
46		-
47		-The tool needs two projects templates, one of them is a application template, the other a framework template.&nbsp; So you need to create a _WebObjects Application_ and a _WebObjects Framework_.
48		-
49		-!Image 8.png!
50		-
51		-!Image 9.png!
52		-
53		-You should see the tool and the two templates in the _WO Package Explorer_.
54		-
55		-!Image 10.png!
56		-
57		-Open _config.xml_ and change the value of the _<applicationTemplatePath>_ and _<frameworkTemplatePath>_ nodes so that the path points to the templates you created below.
58		-
59		-!Image 22.png!
60		-
61		-For each project that you want to import, you need the a _<project>_ node.&nbsp; _<path>_ is the file system path to the Xcode project, _<name>_ is the project name, minus .xcodeproj
62		-
63		-Right-click on the _XCodeMigration.java_ class and select _Run As_ \-> _Open Run dialog..._
64		-
65		-!Image 12.png!
66		-
67		-Double-click on _Java Application_.
68		-
69		-!Image 13.png!
70		-
71		-Click on the _Arguments_ tab and enter this value as a _Program arguments_.
72		-{code}
73	73	${project_loc}/config.xml
74		-{code}
75		-!Image 21.png!
76	76
77		-Click _Apply_ and click _Run_.
	23	+{{/code}}
78	78
79		-When it's running, you should see a output like this:
	25	+* click apply and run
	26	+* when it's running, you should get a output like this
	27	+Starting the importation process...
	28	+Converting MyProjectName...
	29	+All done&nbsp; Next step: you have to manually import (File > Import > Existing projects into Workspace) the projects into Eclipse
	30	+* to import the converted projects, open File > Import > Existings projects into workspace.&nbsp; Next. select root directory
	31	+* your converted projects will appear in the package explorer
	32	+* fix all frameworks dependencies and you're done
80	80
81		-!Image 16.png!
	34	+= FAQ =
82	82
83		-To import the converted projects, open _File_ \-> _Import_ \-> _Existings projects into workspace_.&nbsp; Click _Next_. Select _Select Root Directory_ and browse to _/tmp/migrations_.&nbsp; You should see the list of projects that you converted.
	36	+**Q.**&nbsp; I can't a //Could not find working dir for project// error when I launch my converted application.
	37	+**A.**&nbsp; Make sure that, in //config.xml//, //<applicationTemplatePath>// is set to a WO application instead of a WO framework.
84	84
85		-!Image 17.png!
	39	+**Q.**&nbsp; Some of my resources are missing or in the wrong folder.
	40	+**A.**&nbsp; The tool detect files that should be marked as Resources by file extension or name. If a file is not a Java class or one of the file type in the Resources list, the file will be move to the WebServerResources folder instead. You just have to move the files to the Resources folder when needed. If you have file types who should be detected as resources, you can add the needed code in the copyFiles method.
86	86
87		-Your converted projects will appear in the _WO Package Explorer_.
88		-
89		-!Image 18.png!
90		-
91		-Fix all frameworks dependencies and any other build errors.&nbsp; It's done.
92		-
93		-h1. FAQ
94		-
95		-*Q.*&nbsp; I can't a _Could not find working dir for project_ error when I launch my converted application.
96		-*A.*&nbsp; Make sure that, in _config.xml_, _<applicationTemplatePath>_ is set to a WO application instead of a WO framework.
97		-
98		-*Q.*&nbsp; Some of my resources are missing or in the wrong folder.
99		-*A.*&nbsp; The tool detect files that should be marked as _Resources_ by file extension or name. If a file is not a Java class or one of the file type in the _Resources_ list, the file will be move to the _WebServerResources_ folder instead. You just have to move the files to the Resources folder when needed. If you have file types who should be detected as resources, you can add the needed code in the _copyFiles_ method.
100		-
101		-*Q.*&nbsp; My application is localized and the content in the components are displaying the wrong caracters.
102		-*A.*&nbsp; If you set the _<convertToUTF8>_ node to true, your Java classes will be converted from MacRoman to UTF-8, but the tool will NOT modify the .woo file so that they use UTF-8. Either you stay in MacRoman and change the value of _<convertToUTF8>_ to _false_, or you will have to modify your components so that they use UTF-8
103		-{{/panel align=center}}
	42	+**Q.**&nbsp; My application is localized and the content in the components are displaying the wrong caracters.
	43	+**A.**&nbsp; If you set the <convertToUTF8> node to true, your Java classes will be converted from MacRoman to UTF-8, but the tool will NOT modify the .woo file so that they use UTF-8. Either you stay in MacRoman and change the value of <convertToUTF8> to false, or you will have to modify your components so that they use UTF-8.