The EE Project toolset (GO)

1. Support for refactoring, TDD, Debug Java EE application and flying error hint IDE

A. Refactoring: Even if the team uses the most only rename,move,extract method and so on a limited number of the most basic functions, but the structure of the Java EE led to the whole body of things too much, refactoring will help you to wipe things clean, forming a dependency, has not been used to rely on the compiler.

B.TDD:TDD is not equal to Unit Test. TDD lets you not rely on the presentation layer, do not manually input data, clear the data, do not restart the development of Tomcat.
Our team is still not in the pursuit of testing coverage, So,unttest is only a means of development, not testing.

C.debug Java EE application:
Web developers generally use System.out or log4j to display debugging information, but for the programmer who used to desktop programming, directly into the debug mode, one-step tracking program execution path, want to see which variable to see which variable, is the right thing.
Just before the IDE couldn't support it.

D.flying error Hint:
Java IDE's standard configuration, error prompt immediately, do not wait for compile time. Unfortunately, this is not standard in the IDE for other languages.

The team is now using Idea 4.5. You need to go to some plugins before you open eclipse.

2. Version management tool and text diff/merge tool
This year, who dares not use the version management tool to cooperate with the person to develop? Some.
A good programer, in addition to having good udpate/commit habits, will not use the text difference comparison/Merger tool is another level of observation standards.
In addition, version management tools can be combined with idea (because refactoring is useful).

With CVS, green-fur turtles and winmerge. Subversion and other days to eat full of support when the change.

3. Project planning, task allocation, requirements change management, bug management tools
Project planning, task allocation, progress tracking, requirements change management, bug management is almost all the work of PM.
There used to be a lot of software separate to manage these problems, the same problem often to copy paste several software.
But if your team's project plan is XP plan style instead of MS Project---
Congratulations, a jira can do all the work.

4. Team IM tools and shared folders with interference-free
The previous generation is the word will be called email, but we prefer QQ group of instant and Mass.
At the same time, QQ version 2005-"Only show the message number of messages when the message is" the non-intrusive function is very important.
The team that sits together, it's enough to build a shared folder on the file server.

Other tools include paper, pens, large enough whiteboard, ready-to-use conference rooms, and a wiki of knowledge base.

What's missing? Because there are not enough unittest use cases, the well-equipped continuous integration tool does not actually work. The Code Auto-generation tool is not yet the most hand-built.

---restore content ends---

Java EE Project toolset (GO)