Hi Scott,
I would recommend another plan.
1. Get used to Eclipse. Eclipse is completely different IDE. Lern how to
work with. Create a java project and launch it. Create more projects, manage
dependencies and so on.
2. Do the the same stuff from step one with WebObjects projects. Add some
resources and so on. Don't forget to test the deployment.
If all went well proceed with step 3. Don't forget the mailinglist is ready
to help you.
3. Proceed with your plan. Be aware of duplicate class. It's possible that
the same class is in different projects. Eclipse gives you some feedback but
it's very hard to figure out that the duplicates are the issue.
----- Original Message -----
From: "Scott Anderson" <scot..ccendi.com>
To: <woproject-de..bjectstyle.org>
Sent: Wednesday, July 21, 2004 3:54 PM
Subject: Converting from Xcode to eclipse & wolips/woproject
> Hello All,
>
> We have a number of large WebObjects projects currently being developed
> using Xcode on Mac OS X. These projects consist of a number of
> frameworks and some number of applications. We use subversion for
> revision control on these particular projects with a custom client that
> uses the name "CVS" for the admin directory so that WOBuilder and
> EOModeler don't trash the subversion information. Specific questions
> are at the bottom...
>
> We have been breathlessly waiting for Eclipse 3.0 and WOLips to reach
> synergy so that we can fully explore conversion. We are very interested
> in taking advantage of the productivity enhancements this combination
> can provide for large projects.
>
> I've am working on getting a large project that is our pilot into some
> working with this setup. As I'm a newbie to both Eclipse and WOLips, I
> sometimes get confused as to which tool is responsible for the
> functionality that I need to configure.
>
> My current plan is this:
>
> 1. Create a new workspace for this project and create a WOLips
> framework project for each of the frameworks, and an Application
> project for each of the applications.
>
> 2. Copy the java files from the old frameworks and apps into the new
> equivalent's src directories.
>
> 3. Copy the components from the old frameworks and apps into the new
> equivalents directory (keeping the subdirectory Component -- is that ok
> & best practice for this setup?)
>
> 4. Copy the models into their frameworks in a subdirectory named Models
> and somehow setup auto generation of the 2-tier classes again
> (currently done with eogenerator)
>
> Specific Questions
>
> 1. How do you set up a model to be recognized by Eclipse/WOLips for
> auto-generation. We currently use eogenerator but there appears to be a
> woproject task that can do this and converting our templates are not a
> big deal I imagine.
>
Currently discussed in the list.
> 2. There are jar files in some of the frameworks that are normally
> copied by a copy files build phase in Xcode into Resources/Java so that
> the applications pick them up -- what is the best way to do this in the
> Eclipse/WOLips environment.
Add them to the build.xml. The lib tag does the job.
http://www.objectstyle.org/woproject/ant/woframework.html
For instance to include all jars from the lib dir in your project:
<woframework name="MyFramework" destDir="${dist}/Frameworks">
.
.
.
.
<lib dir="lib">
<include name="lib/*.jar"/>
</lib>
</woframework>
>
> 3. Is there a document that covers getting started with WOLips that I'm
> missing?
The help is integrated into the Eclipse help.
>
> 4. ivars don't seem to be showing up in WOBuilder -- I seem to recall
> that this might be a known limitation of this version of WOLips -- is
> that true?
>
http://www.objectstyle.org/woproject/wolips.html
> 5. THANK YOU VERY MUCH to all who make this project possible.
>
> If anyone has tips on moving from an Xcode environment I'd love to hear
> them!
>
> -s
>
>
This archive was generated by hypermail 2.0.0 : Sat Jul 24 2004 - 04:21:54 EDT