Le 08-05-11 à 15:50, Gennady Kushnir a écrit :
Thank you all for your opinions.
I see all hands are for SVN except built in Eclipse integration.
Count me as one hand down for cvs/svn ... mainly for its tag/
branching model.
Count me as a Git happy user !
Maybe I should have used google, but could you explain me in
general how does versioning work. And how do I work with it.
Specifically in regard to WO development.
Does it archive only java sources? And how about components,
EOmodels and other related resources (which can also have versions)?
Specialy with WO, in a MacOS-X context, where we have 'bundles', cvs/
svn will do poorly, because they will spread CVS and SVN directory
all over your file system. If most developer tools have learn to
deal with those extra directories and doesn't cause any problem
nowadays, it doesn't mean it's a good practice. For example, with
git, you only have one .git directory at the root of your project,
easy to work with, easy to backup. Git doesn't get in your way, it
just help you.
Another condition is that I don't have Internet connection at work
so I can't use online repository and have to merge my "homework"
using flash drive anyway. Does versioning system support this?(and
which
ones do?)
By definition your workflow is distributed, disconnected, in that
regards centralized tools (cvs/svn/...) wont help you, in fact they
will get in your way and bring you more pain.
By comparaison, a distributed tool (git / bzr / hg) will better fit
your workflow, it is design with such workflow in mind and will 'just
work' (ok, you still have to learn how to make it work).
And questions to Miguel:
- where I can find that "very good open source book that documents
everything" ?
Look at google, specificaly tech-talk videos. The one with Linus
T. explaining GIT to google employe is a good one.
Look also for Mercurial and Bazaar video / presentation, they will
explain the distributed model and how it is different to the
centralized model.
- I can't imagine versioning system without IDE integration. how
does it work?
Command line. Most tool (if not all) will have a command-line
interface first.
- If you say it is that good with Mac OS X integration and coming
really soon - maybe I could wait a bit and start my versioning
experience with something really cool?
Do not base your decision based on the quality of the interface, but
based on the quality of the model. If the model fit yours, then it's
a fit for you. I doubt cvs/svn will be a fit for you based on your
distributed / disconnected nature of your workflow.
- jfv
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
