publish the internal package change first

Update the docs and simplify the local build enable using a property to disable signing vs commenting it out.

Author: jsonbailey

lib/sdk/server/contract-tests/service/src/main/java/sdktest/TestService.java

@@ -35,7 +35,7 @@ public class TestService {
     "filtering",
     "migrations",
     "event-sampling",
-    "inline-context-all",
+    "inline-context",
     "anonymous-redaction",
     "evaluation-hooks",
     "client-prereq-events"

lib/shared/common/CONTRIBUTING.md

@@ -37,9 +37,9 @@ If you wish to clean your working directory between builds, you can clean it by
 ./gradlew clean
 ```
 
-If you wish to use your generated SDK artifact by another Maven/Gradle project such as [java-server-sdk](https://github.com/launchdarkly/java-server-sdk), you will likely want to publish the artifact to your local Maven repository so that your other project can access it.
+If you wish to use your generated SDK artifact by another Maven/Gradle project such as [java-server-sdk](https://github.com/launchdarkly/java-server-sdk), you will likely want to publish the artifact to your local Maven repository so that your other project can access it. You can append `-SNAPSHOT` to the version in [gradle.properties](gradle.properties) and update any dependancies to test the snapshot version.
 ```
-./gradlew publishToMavenLocal
+./gradlew publishToMavenLocal -PskipSigning=true
 ```
 
 ### Testing

lib/shared/common/build.gradle.kts

@@ -88,5 +88,6 @@ nexusPublishing {
 }
 
 signing {
+    setRequired({ findProperty("skipSigning") != "true" })
     sign(publishing.publications["mavenJava"])
 }

lib/shared/internal/CONTRIBUTING.md

@@ -45,9 +45,9 @@ If you wish to clean your working directory between builds, you can clean it by
 ./gradlew clean
 ```
 
-If you wish to use your generated SDK artifact by another Maven/Gradle project such as [java-server-sdk](https://github.com/launchdarkly/java-server-sdk), you will likely want to publish the artifact to your local Maven repository so that your other project can access it.
+If you wish to use your generated SDK artifact by another Maven/Gradle project such as [java-server-sdk](https://github.com/launchdarkly/java-server-sdk), you will likely want to publish the artifact to your local Maven repository so that your other project can access it. You can append `-SNAPSHOT` to the version in [gradle.properties](gradle.properties) and update any dependancies to test the snapshot version.
 ```
-./gradlew publishToMavenLocal
+./gradlew publishToMavenLocal -PskipSigning=true
 ```
 
 ### Testing

lib/shared/internal/build.gradle.kts

@@ -82,5 +82,6 @@ nexusPublishing {
 }
 
 signing {
+    setRequired({ findProperty("skipSigning") != "true" })
     sign(publishing.publications["mavenJava"])
 }