Skip to Content
Last modified by Denis Frolov on 2011/05/25 13:12
From version 23.1
edited by Pascal Robert
on 2007/12/08 21:44
Change comment: There is no comment for this version
To version 28.1
edited by Pascal Robert
on 2007/07/20 21:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,14 +1,12 @@
1 1  As you know, if you plan to continue using WebObjects since Apple deprecated EOModeler, WebObjects Builder and RuleModeler.  So, what's the steps to migrate ?
2 2  
3 -First, you need to install the WebObjects frameworks. On Leopard (Mac OS X 10.5), the frameworks are available in the [[Xcode 3.0>>http://developer.apple.com/tools/download/]] package. On Tiger (Mac OS X 10.4), the frameworks are available in the [[Xcode 2.5>>http://developer.apple.com/tools/download/]].
3 +* First, install [[Eclipse>>http://www.eclipse.org]] (3.2.x series)
4 4  
5 -Second part, you need to install [[Eclipse>>http://www.eclipse.org/downloads/download.php?file=//eclipse/downloads/drops/R-3.3.1.1-200710231652/eclipse-SDK-3.3.1.1-macosx-carbon.tar.gz]] (3.3.11 series).
5 +* After installating Eclipse, start it and follow the [[instructions>>Install WOLips with Eclipse Update Manager]] from this wiki.
6 6  
7 -After installating Eclipse, start it and follow the [[instructions>>Install WOLips with Eclipse Update Manager]] from this wiki.
7 +* WOLips is installed ?  You can start migrating.
8 8  
9 -Everything is is installed ? You can start migrating.
10 -
11 -* You have three choices for migrations for projects.  You can do a [[manual migration>>Import an Xcode project into WOLips]], you can use a [[Java tool>>http://community.os.ca/code/webobjects/XCodeMigration-1.0.tgz]] written by [[Pascal Robert>>mailto:probert@os.ca]] or you can use the "[[fleeto>>http://www.global-village.net/migrate.to.eclipse/home]]" script from Chuck Hill over at Global Village.
9 +* You have three choices for migrations for projects.  You can do a manual configuration, you can use a [[Java tool>>http://community.os.ca/code/webobjects/XCodeMigration-1.0.tgz]] written by [[Pascal Robert>>http://www.os.ca/english/pages/equipe/probert.html]] or you can use the "[[fleeto>>http://www.global-village.net/migrate.to.eclipse/home]]" script from Chuck Hill over at Global Village.
12 12  ** If you are using Pascal's tool, please note that it does the following :
13 13  *** It use a XML configuration file, and you can convert multiple projects at the same time
14 14  *** It parse the original Xcode project by creating a readable plist with /Developer/Tools/pbprojectdump
... ... @@ -34,7 +34,8 @@
34 34  *** 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
35 35  *** 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
36 36  ** 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
37 -** You didn't use Chuck's script ?  Check out this [[page>>Import an Xcode project into WOLips]].
35 +** You didn't use Chuck's script ?
36 +*** 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).
38 38  
39 39  * 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.
40 40  ** 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.