Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[] [Bug 249745] Eclipse Repository Best Practices  
Product/Component: Community / Architecture Council

--- Comment #5 from Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>  2008-10-06 13:27:07 -0400 ---
(In reply to comment #4)
> It's interesting to see so much opinion against SVN.  I've used SVN daily for
> many years and quite like it. 

SVN is not bad. It has many benefits over CVS. I think it's just sometimes that
UHHH-NOOO effected when you refactored a bit, renamed a package, moved some
classes around and bummm, your working copy is broken. Commits don't work with
some cryptic message like "folder already exists/added" or "please cleanup". Of
course, a cleanup doesn't help. 

You manually have to backup your WC, check out a fresh one, and apply your
changes again. Suddenly you lost half of your day. That even happened to me in
a 1.5 WC so the problem still exists.

The admin problem is a general one. I guess that every other SCM will not
support manipulation in the repository through direct file system operations in
a way that CVS allows it. There are good reasons not to allow that. Nobody
modifies MySQL or Oracle table rows directly by editing the bits on the file

Do we have any stats across the board on how often a repository had to be
cleaned by admins? Is it once a week, a month or three times a day? Typically,
what files are affected? EPL Java source or 3rd party libs? If only libs, an
option could be to have those in a SCM which is easier to keep clean, i.e. CVS
(Orbit comes in mind).

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Back to the top