Re: Folder structure with Eclipse
Re: Folder structure with Eclipse
- Subject: Re: Folder structure with Eclipse
- From: "RedBugz Software" <email@hidden>
- Date: Sun, 27 Aug 2006 21:41:35 -0600
On 8/27/06, Wolfram Stebel <email@hidden> wrote:
Hi all,
My WO project has grown in the last years and it is not structured to well,
with packages etc.
I'm coming from a Xcode project with lots of nested folders for
WebComponents as well as for java files.
Now i want a clear folder structure in Eclipse too.
What is a clever "refactoring" for improving the project structure.
It is also not very clear, how to put EOGenerator files in their own folder
in the creation cycle (to keep the project folder content small).
I used to have a folders "EO's" and "Generated EO's" where i never needed to
look into the "Generated..." folder for obvious reasons :-)
Is there a how to on the web or will someone talk about his solution?
You may want to look at some of the larger open source projects to see
how they manage it. Project Wonder has a simple consistent structure,
but doesn't subgroup their components very much. GVC.SiteMaker has an
interesting document on using Eclipse/WOLips with their project, as
their setup is quite involved. They use lots of subprojects to group
their components and classes.
The largest projects I deal with are older legacy projects created and
maintained in ProjectBuilder/Xcode that use lots of subprojects to
group components and source into modules. I've converted those to
WOLips and continue to use the subproject structure. It's more
complicated and tedious to set up in WOLips, but once it's done you
don't need to worry about it much.
Newer projects haven't grown in size large enough for me to really
start worrying about project structure too much. I do create folders
at the root of the project for different kinds of resources, much like
Wonder does. You can even duplicate your Xcode virtual folder
structure in WOLips, but Eclipse follows your file system pretty
carefully, so all of your Xcode groups will need to become actual
filesystem folders in Eclipse.
I have some projects that I inherited that build generated stuff into
separate folders as well. Eclipse lets you have many source folders
per project, so it can be done, though is a bit tricky the first time
to understand, but then it's straightforward. I only do a little
EOGenerator stuff, and it just builds directly into my normal source
folder.
I use Java packages for pretty much everything new, but I haven't
converted our old projects, where most stuff is still in the default
package. This can get messy in WOLips as all of your source and
component classes are in one big default package folder. It's fairly
easy to convert the classes themselves to use packages using Eclipse's
refactoring support. You can create a package folder and just drag and
drop the classes from with the Eclipse Package Explorer or Navigator,
and it will automatically convert the classes to that package. Getting
WebObjects to recognize that your classes are in packages can be
trickier, but again, once it's done it's done, and straightforward
after that.
When I get some time, I'll try to post an example on the wiki.
Logan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden