I have a workspace for every branch I'm working on. So for example I have a
prod workspace that has everything checked out from the branch that is in production.
Then I have the trunk workspace which checks out everything from trunk in our subversion repository. I usually work on that when adding new features and working on the next release of our applications.
And then I have an mpvwonder workspace. This corresponds to our subversion branch created from trunk. And I'm working on converting all our projects to Wonder. This will be merged into trunk eventually.
But basically, each of these workspaces (prod, trunk, mpvwonder) has all of our projects: frameworks, web apps and something we call agents (they are like webapps but without a user interface and they perform back end tasks such as generating reports periodically to name just one of many many tasks they perform).
I'm currently using WO 5.4.3 only. But eventually I plan on playing with a newer version when it comes out and for that I'll just follow David's excellent tutorial:
I also have Wonder source imported into each Eclipse workspace so that I can work with Wonder's source and for enhanced debugging.
In subversion I use the svn:externals property to check out the right version of Wonder that we are doing QA against. You can read about svn:externals in the svn-book. Google for it if you are not familiar with it.
:-)
On Jun 26, 2009, at 4:09 PM, Your Friend The Atom wrote:
How do you organize your eclipse workspace?
Do you have a workspace for each client?
Or for each project (app and frameworks in one)?
Or are all your legacy apps which use WO5.3 in one workspace
and does that folder on disk contain the WO5.3 framework just like any other third-party framework?
Are your WO5.3 frameworks in /Developer or somewhere else in /Library?
My goal is to have an environment (Leopard) where the default installation mostly remains untouched and the legacy apps do not interfere with 5.4 development.
Thanks.
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
This email sent to email@hidden