git & java - 未名空间MITBBS历史存档

国际科技财经博客移民网络热点娱乐民生时事公众号

Redian新闻

>未名空间

>Java - 爪哇娇娃

git & java

git & java# Java - 爪哇娇娃

c*t2009-03-04 08:03

1 楼

Does git work well for Java (consider refactoring etc)? Anyone has
experiences / tips?

m*t2009-03-04 08:03

2 楼

Works great for me. Renamed classes/packages are correctly
detected and history preserved. The trick is that right after the
refactoring, hold off whatever other changes you want to make,
and check in the rename change alone.
I have not been using the eclipse plugin, but it seems to be
in some pretty good shape by now.
Oh did I mention git rocks? ;-)

【在 c*****t 的大作中提到】

: Does git work well for Java (consider refactoring etc)? Anyone has
: experiences / tips?

b*y2009-03-04 08:03

3 楼

hmm, seems like a good one, made by top programmer for good programmers ;-)
I guess linus got this one right.
but, for me, I use subversion and done a good job for me both my work and my
hobby 剑知小站 project.

m*t2009-03-04 08:03

4 楼

Not everyone needs or has to use git, but I do feel that in general
distributed VCS
is the way to go. It gives developers much more flexibility.

my

【在 b******y 的大作中提到】

: hmm, seems like a good one, made by top programmer for good programmers ;-)
: I guess linus got this one right.
: but, for me, I use subversion and done a good job for me both my work and my
: hobby 剑知小站 project.

c*t2009-03-04 08:03

5 楼

I was just worried about two things
1. management of version # itself. i.e. there could be too many versions
that one lost track of which is which.
2. what if one forget to immediately commit the changes after refactoring
of directories / files. Particularly for people switching back-n-forth
between SVN / Git.

【在 m******t 的大作中提到】

: Not everyone needs or has to use git, but I do feel that in general
: distributed VCS
: is the way to go. It gives developers much more flexibility.
:
: my

m*t2009-03-04 08:03

6 楼

If by "versions" you mean the sha1 names, you don't have to keep track
of those. Git supports tags just as well.
If they forget to commit right after, but remember it before they actually
commit anything, they can commit the renaming only, and then the rest of
the changes, because git supports selectively committing only some lines
in a file.
If they forget about it all the way, and only remember it after, say, 14
commits later, but have not published them yet (like pushed or being pulled)
they

【在 c*****t 的大作中提到】

: I was just worried about two things
: 1. management of version # itself. i.e. there could be too many versions
: that one lost track of which is which.
: 2. what if one forget to immediately commit the changes after refactoring
: of directories / files. Particularly for people switching back-n-forth
: between SVN / Git.