Windows Java Agile Development Environment Setup Steps tutorial

Programming development environment is very important to build, the first step is to build the environment, with the environment to carry out the work. In this article we look at the steps to build a Java Agile development environment under Windows.

The whole software project divides into four environment development local environment, development environment, test environment, IDC environment. Unlike traditional C + + development, the model is the first to develop the local environment. This is why, because most developers are still more familiar with Windows development. For Mac and Linux directly using software and development of the Chinese developers are still very few, this framework is made out of this situation. The following is an architectural diagram of the environment:

From the Environment:

　　First, the development of local environment, the development of integrated server structures. Front-End developers, background developers.

The most used front-end development is Photoshop and Dreamweaver. Most of the PSD will not be developed in collaboration until the entire file is passed over. HTML cutting may be more than one person to develop together. This time requires a centralized FTP server, SVN server. The SVN server is used to save the version code base for saving history-modified versions and developers collaborating. FTP server is suitable for timely modification of the upload to the preview server to preview. See here Some people may ask, I directly merge SVN and FTP not? In fact, there is such a problem, if the direct submission SVN, background developers will see from SVN. Originally the front-end integration of the development of a preview, the results of the impact of the background prone to version confusion.

Background development How to build the environment? Use Eclipse to build a development environment in your local environment and start debugging class, JSP through the Tomcat plug-in or jetty. I've seen a lot of companies that have been published to the integration environment and debugged by playing war packages. Integration environment everyone to integrate easily cause version confusion. Even if you do not publish to the integration environment, it is a waste of time to restart the war package locally even if you modify a small class file. It is best to use Tomcat's thermal deployment to modify small functions directly. That's what we're doing now, using MAVEN to manage jar bundle dependencies, ant local Packaging, copy packages, and rapid development with Eclipse's Tomcat plug-in hot deployment. Wait until all the features have been developed. Publish the branch version to the development environment for integration testing.

The software involved in the development environment are: Nexus, MAVEN, Tomcat server, MySQL, FTP, Jenkins, SVN, Jira, Fisheye, Eclipse, Dreamweaver, Photoshop, Nginx.

The role of the software:

Nexus is managed as a centralized warehouse because each project is difficult to manage if it has a stack of jar packs. Plus svn upload, branch, merge cost network bandwidth, space. If there is a place where these wasted jars are managed centrally, it would be nice to have all the projects together.

MAVEN is the software lifecycle, dependency management, and with a centralized management jar package, you need something to connect the jar storage and engineering.

The Tomcat server is a local development use and a centralized test server.

MySQL does not need each development machine to install a, put in a development environment can be.

FTP is used as a front-end development upload file.

Jenkins is continuous integration, development and front-end all the code, how to integrate the integration test, there is always a person to put all the files together? This software is the role of integrating, compiling, packaging, and publishing all files into a tomcat server. The following figure:

SVN code versioning, we all know synergy.

Jira is used for management of requirements, bugs, and so on.

Fisheye is used for code statistics, auditing, and so on.

Eclipse, Dreamweaver, Photoshop, needless to say.

Nginx is mainly used for virtual host and static resource management. Because we may be developing multiple Web sites at the same time, Nginx can be forwarded to different Web servers based on different domain names.

　　Second, the test server. Development, testing.

After the development of the integrated test environment, this can be transferred to the test. With continuous integration, test the deployment environment to start testing. The test environment also relies on software such as centralized warehouses, MAVEN, and continuous integration. That is, the integrated test environment, the development of integrated environment, the development of the local environment are a set of jar package, is not very cool. If the test does not pass, it is necessary to revert to the development, development, and then turn test. How to ensure the quality of development and testing of quality, and everyone's collaboration, this process involves software engineering and performance appraisal, and later. The test passes some tests, and the test is passed and released to the extranet. This time need to provide a publishing list, procedures, database operations scripts to the operation of the audit, after the approval can be released.

How to publish to extranet IDC? Operation Dimension can be operated according to publish List, development and front end together wait to stay up late. No efficiency! Here is an incremental release of the way, by publishing a list, our publishers will automatically detect the release of the file and the release of the Machine, published to the corresponding server. If the publication fails, you can roll back the file, which is essentially a one-click operation. The future will also be the server restart, log output, such as integration.

　　Third, IDC server.

External network of the real server, backstage and front desk. You can access to the Web server. Business personnel are viewed after release. The whole process is done. Everyone in each version of the development is over, can be very good synergy, development, testing, release.