readme.adoc 2.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354
  1. = Salespoint Framework
  2. image:https://github.com/st-tu-dresden/salespoint/actions/workflows/deploy.yaml/badge.svg["Build and deploy Maven artifacts", link="https://github.com/st-tu-dresden/salespoint/actions/workflows/deploy.yaml"]
  3. == Prerequisites
  4. - OpenJDK 17
  5. - Git
  6. == Building the project
  7. .Building the project
  8. [source, bash]
  9. ----
  10. $ git clone https://github.com/st-tu-dresden/salespoint
  11. $ cd salespoint
  12. $ ./mvnw clean install
  13. ----
  14. == Documentation
  15. The reference documentation is written in Asciidoc and built using Asciidoctor. The main documentation source file is located in `src/main/asciidoc`.
  16. To build the reference documentation simply run `./mvnw -Pdocs package` on the command line. This generates the following HTML files:
  17. * the Salespoint website in `target/generated-docs/index.html`.
  18. * the Salespoint reference in `target/generated-docs/salespoint-reference.html`.
  19. == Deployment
  20. To deploy artifacts to the salespoint repository, simply run `./mvnw clean deploy`. This requires your `settings.xml` (located in `~/.m2` ) to contain a server definition with the credentials to access the Salespoint server via SFTP:
  21. [source, xml]
  22. ----
  23. <server>
  24. <id>salespoint</id>
  25. <username>…</username>
  26. <password>…</password>
  27. </server>
  28. ----
  29. To deploy the website and reference documentation, run `./mvnw -Pdocs site:deploy`.
  30. == Release
  31. 1. Make sure all tickets are closed, except the release one.
  32. 2. 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`.
  33. 3. Update version information `index.adoc` (in `src/main/asciidoc/site`).
  34. 4. Commit as `GH-??? - Prepare release $version.`. If this was on a maintainance branch, also cherry-pick this commit to `main` and resolve any conflicts.
  35. 5. Run `./mvnw release:prepare`.
  36. 6. Edit commits to match commit message format, re-create tag.
  37. 7. Push changes & tag.
  38. 8. Check out tag and run `./mvnw clean deploy -Prelease -DskipTests`.
  39. 9. Check out tag and run `./mvnw clean package site:deploy -Pdocs,release`.