![]() The development branch may now be used for the next round of development work. A Git tag should be created for the released version.gradlew verifyRelease to ensure that the artifacts and site have been published (optional but recommended). Manually confirm the publication of the new artifact on the Bintray web site (or the publication will expire) - this step may no longer be needed, but verify anyway.This step may take some time (on the order of a minute or two depending on server response times).sonotypePass - the Sonotype password (from API key).sonotypeUser - the Sonotype username (from API key).You will need to provide (or have configured in your HOME/.gradle/gradle.properties file):. ![]() gradlew release which will check the documented project version against the project version, publish the artifact and the documentation web site. Once the pull request has been merged into master, checkout the master branch and: Create a Pull Request from development to master and accept it or have it reviewed.gradlew updateVersion -Pfrom=OLD_VERSION to update the documented version. Ensure that the project version (in adle) has been updated to the desired version.When ready to release a new version of the project, perform the following steps starting in the development branch: This task will push the site contents into the gh-pages branch of the project, assuming you have permissions to push content into the repo. The documentation is provided by a unified documentation web site, which can be generated using: Test, Coverage & Quality reports - misc build and quality reports.JavaDocs - unified API documentation (throughout the codebase).User Guide - getting started, examples and detailed usage information ( src/docs/asciidoc directory). ![]()
0 Comments
Leave a Reply. |