Changes for page XcodeMigration

Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.probert
	1	+XWiki.kieran

Content

...	...	@@ -1,21 +1,67 @@
	1	+{{toc}}{{/toc}}
	2	+
1	1	= Introduction  =
2	2
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). 
	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). 
4	4
	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	+
5	5	= How to use it =
6	6
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;
	15	+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).
18	18
	17	+[[image:Image 1.png]]
	18	+
	19	+Make sure that you are in the WOLips perspective.
	20	+
	21	+[[image:Image 6.png]]
	22	+
	23	+[[image:Image 7.png]]
	24	+
	25	+[[Download the tool>>^XcodeMigration.zip]] (you don't need to expand the .zip file)
	26	+
	27	+Import the XcodeMigration tool into Eclipse, by selecting //File// > //Import//.&nbsp;&nbsp;&nbsp;&nbsp;
	28	+
	29	+[[image:Image 2.png]]
	30	+
	31	+Select //Existings Projects into Workspace// and click //Next//.
	32	+
	33	+[[image:Image 3.png]]
	34	+
	35	+Select the location of the ZIP file with the tool and click //Finish//.
	36	+
	37	+[[image:Image 4.png]]
	38	+
	39	+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//.
	40	+
	41	+[[image:Image 8.png]]
	42	+
	43	+[[image:Image 9.png]]
	44	+
	45	+You should see the tool and the two templates in the //WO Package Explorer//.
	46	+
	47	+[[image:Image 10.png]]
	48	+
	49	+Open //config.xml// and change the value of the //<applicationTemplatePath>// and //<frameworkTemplatePath>// nodes so that the path points to the templates you created below.
	50	+
	51	+[[image:Image 22.png]]
	52	+
	53	+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
	54	+
	55	+Right-click on the //XCodeMigration.java// class and select //Run As// > //Open Run dialog...//
	56	+
	57	+[[image:Image 12.png]]
	58	+
	59	+Double-click on //Java Application//.
	60	+
	61	+[[image:Image 13.png]]
	62	+
	63	+Click on the //Arguments// tab and enter this value as a //Program arguments//.
	64	+
19	19	{{code}}
20	20
21	21	${project_loc}/config.xml
...	...	@@ -22,15 +22,24 @@
22	22
23	23	{{/code}}
24	24
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
	71	+[[image:Image 21.png]]
33	33
	73	+Click //Apply// and click //Run//.
	74	+
	75	+When it's running, you should see a output like this:
	76	+
	77	+[[image:Image 16.png]]
	78	+
	79	+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.
	80	+
	81	+[[image:Image 17.png]]
	82	+
	83	+Your converted projects will appear in the //WO Package Explorer//.
	84	+
	85	+[[image:Image 18.png]]
	86	+
	87	+Fix all frameworks dependencies and any other build errors.&nbsp; It's done.
	88	+
34	34	= FAQ =
35	35
36	36	**Q.**&nbsp; I can't a //Could not find working dir for project// error when I launch my converted application.
...	...	@@ -37,7 +37,7 @@
37	37	**A.**&nbsp; Make sure that, in //config.xml//, //<applicationTemplatePath>// is set to a WO application instead of a WO framework.
38	38
39	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.
	95	+**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.
41	41
42	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.
	98	+**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.