Skip to Content
Last modified by Denis Frolov on 2011/05/25 13:12
From version 18.1
edited by Pascal Robert
on 2007/12/08 23:36
Change comment: There is no comment for this version
To version 24.1
edited by Pascal Robert
on 2007/06/14 18:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,9 +1,22 @@
1 -As you know, if you plan to continue using WebObjects since Apple [[deprecated>>http://lists.apple.com/archives/webobjects-dev/2006/Aug/msg01144.html]] EOModeler, WebObjects Builder and RuleModeler.  In fact, the tools are [[NOT available at all>>http://www.wocommunity.org/webobjects_faq.html#xcode3]] on Mac OS X 10.5.  So, what's the steps to migrate ?
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/]].  After the frameworks are installed, 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]] and [[WOLips>>Install WOLips with Eclipse Update Manager]].
3 +* First, install [[Eclipse>>http://www.eclipse.org]] (3.2.x series)
4 4  
5 -Everything is is installed ? You can start migrating.  You have three choices for migrations for projects. 
5 +* After installating Eclipse, start it and follow the [[instructions>>Install WOLips with Eclipse Update Manager]] from this wiki.
6 6  
7 -* You only have a couple of frameworks and applications, and those projects are not very complex?  You can do a [[manual migration>>Import an Xcode project into WOLips]].
8 -* You have a couple of projects and you didn't put your components and classes in sub folders ?  Try the "[[fleeto>>http://www.global-village.net/migrate.to.eclipse/home]]" script from [[Chuck Hill>>~~chill]].
9 -* You have complex and/or many projects ?  Use the [[XcodeMigration]] tool from [[Pascal Robert>>~~probert]].
7 +* WOLips is installed ?  You can start migrating.
8 +
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
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).
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.