Kontent Java Packages
Monorepo with Java Kontent packages.
Packages
Package | Summary | Version |
---|---|---|
Kontent Delivery Java SDK | The Kentico Kontent Delivery Java SDK is a client library used for retrieving content from Kentico Kontent | |
Kontent Generators | This tool generates strongly-typed models based on Content Types in a Kentico Kontent project. | |
Kontent Sample Spring Boot app | Showcase of the Spring boot application displaying data from Kontent. | source |
Kontent Sample Gradle Console app | Simple Java console application showcasing how to load data from Kontent. | source |
Kontent Sample Android app (Java) | Showcase of the Android application written in Java using RxJava for data fetching from Kontent. | source |
Kontent Sample Android app (Kotlin) | Showcase of the Android application written in Kotlin using Kotlin Coroutines for data fetching from Kontent. | source |
Development
If you wish to find out more about the project specification. Check out the Project information.
Prerequisites
Required: Java 8 SDK (Oracle & OpenJDK both tested and supported)
Build and Test
-
Ensure your
JAVA_HOME
environment is set. -
Clone this repository
git clone https://github.com/Kentico/kontent-java-packages
-
Enter the cloned repository and build the project via the provided Gradle wrapper.
To grant execution rights for
gradlew
binary, you could usechmod a+x ./gradlew
which allows execution to everybody.cd kontent-java-packages ./gradlew clean build
The command will build whole solution and run all tests in this monorepo.
๐ก
Next steps
The ideal next step is to test out the Kontent Sample Spring Boot app or load the project in In IDE (IntelliJ IDEA recommended) and run/debug tests in Kontent Delivery Java SDK.
Publishing
To publish a new version, it is required to have write permissions for this repository (to be able to create releases) and access to the Nexus Repository Manager.
-
Verify that everything in the branch is ready to be published and the build and tests are passing.
-
Create new GitHub release - the tag name of the release will be used as a version
-
If you define tag name with "-SNAPSHOT" suffix i.e.
4.4.0-SNAPSHOT
artifact will be published to thehttps://oss.sonatype.org/content/repositories/snapshots/
, so that you could use it when you want to try out the beta version. -
The creation of a release triggers the Publish Github workflow and creates and publishes the artifacts to "Staging" repositories on Nexus repository manager.
-
-
Log in to the Nexus Repository Manager.
-
Select "Staging repositories", verify the repository content (sometimes it takes a couple of minutes until the repository is visible in the Nexus Repository Manager UI).
-
Close the Staging repository
-
Release the Closed repository
-
Increase the patch version and append
-SNAPSHOT
in the bottom of/build.gradle
file (i.e.4.4.1-SNAPSHOT
).
๐ก This is just an abbreviated description of the publishing process. If you want to see the detailed publishing description, checkout the wiki page "Publishing process".