Re: source control best practice with wonder
Re: source control best practice with wonder
- Subject: Re: source control best practice with wonder
- From: Chuck Hill <email@hidden>
- Date: Mon, 17 Mar 2008 09:37:22 -0700
On Mar 17, 2008, at 8:38 AM, Simon McLean wrote:
Hi All -
What does everyone else do with the woproject files when it comes to
source control ?
For years, I just swore at them.
We've got some projects where all the woproject files are under
source control, and others have only some of them.
I can't remember the specifics as to why we excluded some files in
the past, but i seem to remember there being problems with different
machines having different set ups (for example different frameworks
installed) which meant certain files we're flagged as having been
changed every time you updated or committed.
Anyway, just wondering what everyone else does ?
The best practice is probably to migrate your project structure to the
Fluffy Bunny Layout (I really should make a Wiki page for that) and
have your source control ignore woproject/.
The second-best (as in not quite as good) practice is to have your
source control ignore woproject/ant.frameworks.* and woproject/
ant.classpaths.* and change your build to use the bundles attribute of
FrameworkSet: http://wiki.objectstyle.org/confluence/display/WOL/WOProject-FrameworkSet
The third-best is to just swear at them. Worked for me for years. :-)
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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