Ideas for maven, Gradle, SVN, Spring 3.0 fragment, git

1. Maven

Maven can build projects and use pom to Configure master projects and other projects that need to be referenced. The new feature Web fragmentcan also be combined with spring3.0.

From the reality, especially for the management is not in place, the overall quality of the programmer is not so high development team, the use of this method may not be able to play its advantages and efficacy, but will become a constraint on the way forward.

2. Gradle

for Gradle I was quite fond and admired. But the cult can not be blind, like Maven has a central warehouse and support a variety of warehouse methods.

also in terms of development team management and daily development efficiency, comfort and convenience, I recommend using the gradle maven Central Warehouse to dismantle the traditional jar The way Baoqian in the Lib folder is reasonable and does not cost much. The cost here is human cost, management cost, learning cost and so on.

3. Spring 3.0 Fragment

a few of the features of Spring3.0 really make people ecstatic. And the Web fragment to the Java Object-oriented modular development is to blow, immediately let people clairvoyant.

Some people say that in fact, Java object-oriented is not a concept of modular development, but the Java Underlying class library is not a modular development of the idea.

If you don't have to build a project with Gradle,maven,fragment , It's also a must. Because we used to be thousands of miles away, straight to the head of the killing tools Eclipse 's Deployment Assembly in one degree can achieve the main project reference to other projects, It is called and developed with the idea of modularization.

but with gradle, we can get rid of our long-standing bad at a very small cost:There are too many jars in Lib . Many of them are irritable, even log4j, but there are different versions. Accidentally remembered a song, "God, help me."

with fragment, we can be more completely modular, not only to split the Java code to achieve the background service layer components of the low-coupling, the front page can also be implemented component.

4. SVN

from the first time with SVN to the present, even the project has been transferred to git . I still think that svn is a good tool. Despite the enumeration of Git 's many things, it is useless to belittle svn . such as git can achieve branch management, fast rollback and so on advantages.

many of the development teams that turn to git say the most, probably because git can implement versions of iterative control, branch management, and is particularly powerful. In fact, I would like to say thatsvn can also achieve similar functions in the case of team management. Maybe it's a little too big for work, and maybe a lot more expensive than git to write. But that doesn't obscure the fact that svn is a good tool.

that's the point, why I'm now moving the project to git. In fact the reason is very simple, I have not used git, I want to try something new, and git 's split management, version of the natural advantages of iteration is also my urgent need.

5. Git

Git 's branch management, version iterations are already familiar to the public. The benefits will not be mentioned again, I give git hit the score. The rest of the point is afraid of his pride. Ha ha.

You can visit the website of Liao Xuefeng to learn about Git.

Ideas for maven, Gradle, SVN, Spring 3.0 fragment, git