Skip to Content

Changes for page XcodeMigration

Last modified by William Sandner on 2011/10/19 21:07
From version 52.1
edited by William Sandner
on 2011/10/19 21:07
Change comment: There is no comment for this version
To version 42.1
edited by Pascal Robert
on 2010/01/04 06:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.wsandner
1 +XWiki.probert
Content
... ... @@ -11,142 +11,93 @@
11 11  {{/info}}
12 12  
13 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 copy it from another machine too).  \\
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 15  
16 -Alternatively, inside the Xcode tools 2.5 disk image, pbprojectdump can be found at Packages/Packages/DeveloperTools.pkg/Contents/Archive.pax.gz:/Tools/pbprojectdump
17 -
18 18  {{/note}}
19 19  
20 20  = How to use it =
21 21  
22 -Get the project from the [[GitHub repository>>https://github.com/pascalrobert/XCodeMigration]].
23 -
24 24  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).
25 25  
26 -{{panel}}
22 +{{panel align=center}}
27 27  
28 -!Image 1.png|align=center!
24 +!Image 1.png!
25 +{panel}
29 29  
30 -{{/panel}}
31 -
32 32  Make sure that you are in the WOLips perspective.
33 33  
34 -{{panel}}
29 +!Image 6.png!
35 35  
36 -!Image 6.png|align=center!
37 -!Image 7.png|align=center!
31 +!Image 7.png!
38 38  
39 -{{/panel}}
33 +[Download the tool|^XcodeMigration.zip] (you don't need to expand the .zip file)
40 40  
41 -Import the XcodeMigration tool into Eclipse, by selecting //File// > //Import//.
35 +Import the XcodeMigration tool into Eclipse, by selecting _File_ \-> _Import_.    
42 42  
43 -{{panel}}
37 +!Image 2.png!
44 44  
45 -!Image 2.png|align=center!
39 +Select _Existings Projects into Workspace_ and click _Next_.
46 46  
47 -{{/panel}}
41 +!Image 3.png!
48 48  
49 -Select //Existings Projects into Workspace// and click //Next//.
43 +Select the location of the ZIP file with the tool and click _Finish_.
50 50  
51 -{{panel}}
45 +!Image 4.png!
52 52  
53 -!Image 3.png|align=center!
47 +The tool needs two projects templates, one of them is a application template, the other a framework template.  So you need to create a _WebObjects Application_ and a _WebObjects Framework_.
54 54  
55 -{{/panel}}
49 +!Image 8.png!
56 56  
57 -Select the location of the ZIP file with the tool and click //Finish//.
51 +!Image 9.png!
58 58  
59 -The tool needs two projects templates, one of them is a application template, the other a framework template.  So you need to create a //WebObjects Application// and a //WebObjects Framework//.
53 +You should see the tool and the two templates in the _WO Package Explorer_.
60 60  
61 -{{panel}}
55 +!Image 10.png!
62 62  
63 -!Image 8.png|align=center!
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.
64 64  
65 -{{/panel}}
59 +!Image 22.png!
66 66  
67 -{{panel}}
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
68 68  
69 -!Image 9.png|align=center!
63 +Right-click on the _XCodeMigration.java_ class and select _Run As_ \-> _Open Run dialog..._
70 70  
71 -{{/panel}}
65 +!Image 12.png!
72 72  
73 -You should see the tool and the two templates in the //WO Package Explorer//.
67 +Double-click on _Java Application_.
74 74  
75 -{{panel}}
69 +!Image 13.png!
76 76  
77 -!Image 10.png|align=center!
78 -
79 -{{/panel}}
80 -
81 -Open //config.xml// and change the value of the //<applicationTemplatePath>// and //<frameworkTemplatePath>// nodes so that the path points to the templates you created below.
82 -
83 -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
84 -
85 -Right-click on the //XCodeMigration.java// class and select //Run As// > //Open Run dialog...//
86 -
87 -{{panel}}
88 -
89 -!Image 12.png|align=center!
90 -
91 -{{/panel}}
92 -
93 -Double-click on //Java Application//.
94 -
95 -{{panel}}
96 -
97 -!Image 13.png|align=center!
98 -
99 -{{/panel}}
100 -
101 -Click on the //Arguments// tab and enter this value as a //Program arguments//.
102 -
103 -{{code}}
104 -
71 +Click on the _Arguments_ tab and enter this value as a _Program arguments_.
72 +{code}
105 105  ${project_loc}/config.xml
74 +{code}
75 +!Image 21.png!
106 106  
107 -{{/code}}
77 +Click _Apply_ and click _Run_.
108 108  
109 -{{panel}}
110 -
111 -!Image 21.png|align=center!
112 -
113 -{{/panel}}
114 -
115 -Click //Apply// and click //Run//.
116 -
117 117  When it's running, you should see a output like this:
118 118  
119 -{{panel}}
81 +!Image 16.png!
120 120  
121 -!Image 16.png|align=center!
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.
122 122  
123 -{{/panel}}
85 +!Image 17.png!
124 124  
125 -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.
87 +Your converted projects will appear in the _WO Package Explorer_.
126 126  
127 -{{panel}}
89 +!Image 18.png!
128 128  
129 -!Image 17.png|align=center!
130 -
131 -{{/panel}}
132 -
133 -Your converted projects will appear in the //WO Package Explorer//.
134 -
135 -{{panel}}
136 -
137 -!Image 18.png|align=center!
138 -
139 -{{/panel}}
140 -
141 141  Fix all frameworks dependencies and any other build errors.&nbsp; It's done.
142 142  
143 -= FAQ =
93 +h1. FAQ
144 144  
145 -**Q.**&nbsp; I can't a //Could not find working dir for project// error when I launch my converted application.
146 -**A.**&nbsp; Make sure that, in //config.xml//, //<applicationTemplatePath>// is set to a WO application instead of a WO framework.
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.
147 147  
148 -**Q.**&nbsp; Some of my resources are missing or in the wrong folder.
149 -**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.
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.
150 150  
151 -**Q.**&nbsp; My application is localized and the content in the components are displaying the wrong caracters.
152 -**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.
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}}