Skip to Content
Last modified by Denis Frolov on 2011/05/25 13:12
From version 25.1
edited by Pascal Robert
on 2007/06/14 18:33
Change comment: There is no comment for this version
To version 27.1
edited by David Avendasora
on 2007/07/02 14:29
Change comment: Grammar changes only.

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.probert
1 +XWiki.avendasora
Content
... ... @@ -7,16 +7,16 @@
7 7  * WOLips is installed ?  You can start migrating.
8 8  
9 9  * You can do a manual configuration, or you can use the "[[fleeto>>http://www.global-village.net/migrate.to.eclipse/home]]" script from Chuck Hill over at Global Village.
10 -** If you are using Chuck's script, please note that it do the following :
11 -*** Check if you actually created a project, with a Wonder layout, in Eclipse (the script look for a .project file)
12 -*** Check if the current folder (the original XCode project) has a .xcodeproj file
13 -*** Do a find of all .java files in the XCode project folder and copy them over to the "Sources" folder of the Eclipse project
14 -*** Copy all .wo and .api files found in the root folder of the XCode folder into the "Components" folder of the Eclipse project
15 -*** Copy all .eomodeld, .plist, .txt, .html, .xml and the Properties files found in the root folder of the XCode folder into the "Resources" folder of the Eclipse project
16 -*** Copy all .gif, .jpeg, .js, .css,  and .map files found in the root folder of the XCode folder into the "WebServerResources" folder of the Eclipse project
17 -** So if you have files (for examples, your .wo files where in a WOComponents folder), you either have to modify the script or move the files by hand
10 +** If you are using Chuck's script, please note that it does the following :
11 +*** Checks to see if you actually created a project with a Wonder layout in Eclipse (the script looks for a .project file)
12 +*** Checks to see if the current folder (the original XCode project) has a .xcodeproj file
13 +*** Does a find of all .java files in the XCode project folder and copies them over to the "Sources" folder of the Eclipse project
14 +*** Copies all .wo and .api files found in the root folder of the XCode folder into the "Components" folder of the Eclipse project
15 +*** Copies all .eomodeld, .plist, .txt, .html, .xml and the Properties files found in the root folder of the XCode folder into the "Resources" folder of the Eclipse project
16 +*** Copies all .gif, .jpeg, .js, .css and .map files found in the root folder of the XCode folder into the "WebServerResources" folder of the Eclipse project
17 +** So if you have files (for examples, your .wo files were in a WOComponents folder), you either have to modify the script or move the files by hand
18 18  ** You didn't use Chuck's script ?
19 -*** Copy the files as the script does.  Don't forget that if your code is inside packages, you have to create the complete folder structure in the Eclipse project (in fact, you do it at the file system level) and move your code to the correct folder (example : if your package name is "org.objectstyle.migration", you have to create this folder structure, "org/objectstyle/migration", in the "Sources" folder and move the source files there).
19 +*** Copy the files as the script does. Don't forget that if your code is inside packages, you have to create the complete folder structure in the Eclipse project (in fact, you do it at the file system level) and move your code to the correct folder (example : if your package name is "org.objectstyle.migration", you have to create this folder structure, "org/objectstyle/migration", in the "Sources" folder and move the source files there).
20 20  
21 -* Go back to Eclipse, right-click and hit "Refresh".  You should see your files in the various folders, and Eclipse will automatically build your project.  After that, you just need to check for any errors and warnings and fix them.
22 -** In our case, we had old EOModels that where using NSdoubleNumber instead of NSNumber.  BUT Entity Modeler won't show those errors inside Eclipse, instead you will see blank stuff.  You see the actual errors in Console.app instead, so be sure to check that log if you have any strange errors.
21 +* Go back to Eclipse, right-click and hit "Refresh". You should see your files in the various folders, and Eclipse will automatically build your project. After that, you just need to check for any errors and warnings and fix them.
22 +** In our case, we had old EOModels that where using NSdoubleNumber instead of NSNumber. BUT Entity Modeler won't show those errors inside Eclipse, instead you will see blank stuff. You see the actual errors in Console.app instead, so be sure to check that log if you have any strange errors.