Changes for page XcodeMigration
Last modified by William Sandner on 2011/10/19 21:07
From version 27.1
edited by Pascal Robert
on 2007/12/08 23:06
on 2007/12/08 23:06
Change comment:
There is no comment for this version
To version 28.1
edited by Pascal Robert
on 2007/12/08 23:18
on 2007/12/08 23:18
Change comment:
http://wiki.objectstyle.org/confluence/download/resources/com.atlassian.confluence.extra.tinymceplugin:tinymceeditor/tinymcesource/plugins/confluence/images/confimahttp://wiki.objectstyle.org/confluence/download/resources/com.atlassian.confluence.extra.tinymceplugin:tinymceeditor/tinymcesource/plugins/confluence/images/confimage.gifge.gifhttp://wikhttp://wiki.objectstyle.org/confluence/download/resources/com.atlassian.confluence.extra.tinymceplugin:tinymceeditor/tinymcesource/plugins/confluence/images/confimage.gifi.objectstyle.org/confluence/download/resources/com.atlassian.confluence.extra.tinymceplugin:tinymceeditor/tinymcesource/plugins/confluence/images/confimage.gif
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,19 +1,36 @@ 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). 3 +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 5 5 = How to use it = 6 6 7 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 +[[image:Image 1.png]] 8 8 * Make sure that you are in the WOLips perspective 10 +[[image:Image 6.png]] 11 + 12 +[[image:Image 7.png]] 13 + 9 9 * Download the tool (you don't need to expand the .zip file) 10 10 * Import the XcodeMigration tool into Eclipse, by selecting File > Import > Existings projects into workspace. Next. select archive 16 +[[image:Image 2.png]] 17 + 18 +[[image:Image 3.png]] 19 + 11 11 * Create two templates, one application, the other framework 21 +[[image:Image 8.png]] 22 + 23 +[[image:Image 9.png]] 24 + 12 12 * should see 3 projects 26 +[[image:Image 10.png]] 13 13 * open config.xml and change <applicationTemplatePath> and <frameworkTemplatePath> 28 +[[image:Image 11.png]] 14 14 * for each project that you want to import, you need the a <project> node. <path> is the file system path to the Xcode project, <name> is the project name, minus .xcodeproj 15 15 * open the Run dialog 31 +[[image:Image 12.png]] 16 16 * double-click on Java Application 33 +[[image:Image 13.png]] 17 17 * click on the arguments tab and enter this value as a program arguments 18 18 19 19 {{code}} ... ... @@ -22,13 +22,15 @@ 22 22 23 23 {{/code}} 24 24 42 +[[image:Image 21.png]] 43 + 25 25 * click apply and run 26 26 * when it's running, you should get a output like this 27 -Starting the importation process... 28 -Converting MyProjectName... 29 -All done Next step: you have to manually import (File > Import > Existing projects into Workspace) the projects into Eclipse 46 +[[image:Image 16.png]] 30 30 * to import the converted projects, open File > Import > Existings projects into workspace. Next. select root directory 48 +[[image:Image 17.png]] 31 31 * your converted projects will appear in the package explorer 50 +[[image:Image 18.png]] 32 32 * fix all frameworks dependencies and you're done 33 33 34 34 = FAQ = ... ... @@ -37,7 +37,7 @@ 37 37 **A.** Make sure that, in //config.xml//, //<applicationTemplatePath>// is set to a WO application instead of a WO framework. 38 38 39 39 **Q.** Some of my resources are missing or in the wrong folder. 40 -**A.** 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. 59 +**A.** 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.** My application is localized and the content in the components are displaying the wrong caracters. 43 -**A.** 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. 62 +**A.** 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.