暂无描述

Oliver Gierke c134ef35d9 #203 - Prepare for next development iteration. 6 年之前
doc 77c5b1abda #5 - Added Buildsystem Maven to documentation. 10 年之前
etc 22d0c2dfa1 #25 - Overhauled domain code. 10 年之前
src 5e60772a94 #203 - Prepare release 6.4.2. 6 年之前
.gitignore c4db49c33a #32 - Added changelog to website. 10 年之前
.travis.yml 768b85b1ed #183 - Added setup for Travis CI. 7 年之前
LICENSE ccc8e807d9 #169 - Added license file to project root. 7 年之前
Salespoint.sonargraph 5450ed1889 #150 - Updated Sonargraph architecture description. 8 年之前
lombok.config 9cd370f13f #9 - Introduced simplified Quantity abstraction. 9 年之前
pom.xml c134ef35d9 #203 - Prepare for next development iteration. 6 年之前
readme.adoc 6a8fe8c5f5 #188 - Updated details of the release procedure. 7 年之前

readme.adoc

# Salespoint Framework

image:https://travis-ci.org/st-tu-dresden/salespoint.svg?branch=6.4.x["Build Status", link="https://travis-ci.org/st-tu-dresden/salespoint"]

## Prerequisites

- Java 8
- Git
- Maven 3.x

## Building the project

.Building the project
[source, bash]
----
$ git clone https://github.com/st-tu-dresden/salespoint
$ cd salespoint
$ mvn clean install
----

## Documentation

The reference documentation is written in Asciidoc and built using Asciidoctor. The main documentation source file is located in `src/main/asciidoc`.

To build the reference documentation simply run `mvn generate-resources` on the command line. This generates the following HTML files:

* the Salespoint website in `target/generated-docs/index.html`.
* the Salespoint reference in `target/generated-docs/salespoint-reference.html`.

## Deployment

To deploy artifacts to the salespoint repository, simply run `mvn clean deploy`. This requires your `settings.xml` (located in `~/.m2`) to contain a server defintion with the credentials to access the Salespoint server via SFTP:

[source, xml]
----

salespoint



----

To deploy the website and reference documentation, run `mvn site:deploy`.

## Release

. Make sure all tickets are closed, except the release one.
. Tweak `ChangelogCreator` (in `src/test/java`) to point to the milestone to be released. Run the creator. Copy console output into `src/main/asciidoc/site/changelog.adoc`.
. Update `src/main/asciidoc/site/index.adoc` to reflect version about to be released and correct next development version.
. Commit as `#?? - Prepare release $version.`.
. Run `mvn release:prepare -DscmCommentPrefix="$releaseTicketId - "`.
. Edit commits to match commit message format, re-create tag.
. Push changes & tag.
. Check out tag.
. Run `mvn clean deploy site:deploy -Prelease -DskipTests`.