Documentation » History » Revision 21
« Previous |
Revision 21/25
(diff)
| Next »
chin-yeh, 09/23/2011 10:17 AM
- Table of contents
- Documentation
Documentation¶
The main documentation for DP Client.
Programming Guide¶
Deployment Guide¶
List of Components¶
Name | Latest Stable Version | Description |
---|---|---|
dp-stub | 1.2-[version] | The client stub of DP web services |
dp-client | 1.3.3-[version] | The client of DP web services |
dp-test | 1.2.4-SNAPSHOT | A demo application for dp-client |
dp-batch | HEAD tag | dp related batch programs |
- SNAPSHOT - for development environment
- RELEASE - for production environment
The binary of the above components can be found in:
Compile from source files¶
Important Note:
This section is not applicable to dp-batch as its deployment files have to be compiled individually and only upload those which are needed.
All of the projects are built and maintained using Maven 2.
Those projects can be imported into Eclipse IDE but the m2 Maven plugin is needed.
The source files are stored in:
Prerequisite:
- Eclipse IDE (optional)
- Apache Maven 2
- CVS client, e.g TortoiseCVS, Eclipse IDE
- Project or module name, e.g. dp-client
By default, all of the project is configured to include development properties files when packaging the binary file. To include production properties files, activate the prod profile.
Steps:- checkout the project or module using the CVS client
cd
to the checkout folder, e.g. dp-client- Example:
$ cd dp-client
- Example:
- execute the maven goal, clean and package:
- compile for development environment:
- change the artifact version to x.x-SNAPSHOT
$ mvn clean package
- change the artifact version to x.x-SNAPSHOT
- compile for production environment:
- change the artifact version to x.x-RELEASE
$ mvn -P prod clean package
- change the artifact version to x.x-RELEASE
- compile for development environment:
- if success, the binary file can be found in the target folder
Updated by chin-yeh over 13 years ago · 21 revisions