Migrating from XCode to WOLips
Version 26.1 by David Avendasora on 2007/07/02 14:29
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 ?
- First, install Eclipse (3.2.x series)
- After installating Eclipse, start it and follow the instructions from this wiki.
- WOLips is installed ? You can start migrating.
- You can do a manual configuration, or you can use the "fleeto" script from Chuck Hill over at Global Village.
- If you are using Chuck's script, please note that it does the following :
- Checks to see if you actually created a project with a Wonder layout in Eclipse (the script looks for a .project file)
- Checks to see if the current folder (the original XCode project) has a .xcodeproj file
- Does a find of all .java files in the XCode project folder and copies them over to the "Sources" folder of the Eclipse project
- Copies all .wo and .api files found in the root folder of the XCode folder into the "Components" folder of the Eclipse project
- 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
- 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
- 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
- You didn't use Chuck's script ?
- 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).
- If you are using Chuck's script, please note that it does the following :
- 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.
- 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.