@@ -4,28 +4,44 @@ This is the common SDK for the Eppo JVM SDKs. It provides a set of classes and i
4
4
interact with the Eppo API. You should probably not use this library directly and instead use the [ Android] ( https://github.com/Eppo-exp/android-sdk )
5
5
or [ JVM] ( https://github.com/Eppo-exp/java-server-sdk ) SDKs.
6
6
7
- # Usage
7
+ ## Usage
8
8
9
- ## build.gradle:
9
+ ### build.gradle:
10
10
11
11
``` groovy
12
12
dependencies {
13
13
implementation 'cloud.eppo:sdk-common-jvm:1.0.0'
14
14
}
15
15
```
16
16
17
- # Releasing a new version
17
+ ## Releasing a new version
18
18
19
- Bump the project version in ` build.gradle `
20
- To release a new version of the SDK, you need to create a new tag in the repository. The tag should be named ` vX.Y.Z ` ,
21
- where ` X.Y.Z ` is the version number of the release. For example, if you are releasing version 1.2.3, the tag should be
22
- named ` v1.2.3 ` .
19
+ For publishing a release locally, follow the steps below.
20
+
21
+ ### Prerequisites
22
+
23
+ 1 . [ Generate a user token] ( https://central.sonatype.org/publish/generate-token/ ) on ` s01.oss.sonatype.org ` ;
24
+ 2 . [ Configure a GPG key] ( https://central.sonatype.org/publish/requirements/gpg/ ) for signing the artifact. Don't forget to upload it to the key server;
25
+ 3 . Make sure you have the following vars in your ` ~/.gradle/gradle.properties ` file:
26
+ 1 . ` ossrhUsername ` - User token username for Sonatype generated in step 1
27
+ 2 . ` ossrhPassword ` - User token password for Sonatype generated in step 1
28
+ 3 . ` signing.keyId ` - GPG key ID generated in step 2
29
+ 4 . ` signing.password ` - GPG key password generated in step 2
30
+ 5 . ` signing.secretKeyRingFile ` - Path to GPG key file generated in step 2
31
+
32
+ Once you have the prerequisites, follow the steps below to release a new version:
33
+
34
+ 1 . Bump the project version in ` build.gradle `
35
+ 2 . Run ` ./gradlew publish `
36
+ 3 . Follow the steps in [ this page] ( https://central.sonatype.org/publish/release/#credentials ) to promote your release
37
+
38
+ ## Using Snapshots
23
39
24
- # Using Snapshots
25
40
If you would like to live on the bleeding edge, you can try running against a snapshot build. Keep in mind that snapshots
26
41
represent the most recent changes on master and may contain bugs.
42
+ Snapshots are published automatically after each push to ` main ` branch.
27
43
28
- ## build.gradle:
44
+ ### build.gradle:
29
45
30
46
``` groovy
31
47
repositories {
0 commit comments