Add Sources and Javadoc Jars for Maven Central

Co-authored-by: Markus Stoy <markus.stoy@lmax.com>

Author: thebeanogamer

.github/workflows/release.yml

@@ -24,7 +24,7 @@ jobs:
       - name: Setup Gradle
         uses: gradle/actions/setup-gradle@v3
       - name: Publish package
-        run: ./gradlew :nanofix-client:jreleaserFullRelease
+        run: ./gradlew publish :nanofix-client:jreleaserFullRelease --stacktrace
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           JRELEASER_MAVENCENTRAL_USERNAME: ${{ secrets.JRELEASER_MAVENCENTRAL_USERNAME }}

build.gradle

@@ -62,14 +62,6 @@ subprojects {
                 'Bundle-Description': fullDescription,
                 'Bundle-DocURL': siteUrl)
     }
-
-    task sourcesJar(type: Jar) {
-        from sourceSets.main.allSource
-    }
-
-    artifacts {
-        archives sourcesJar
-    }
 }
 
 class Version

nanofix-client/build.gradle

@@ -24,6 +24,11 @@ dependencies {
     implementation 'org.slf4j:slf4j-api:1.7.16'
 }
 
+java {
+    withJavadocJar()
+    withSourcesJar()
+}
+
 jreleaser {
     files {
         active = 'ALWAYS'

nanofix-client/src/main/java/com/lmax/nanofix/outgoing/FixMessageBuilder.java

@@ -62,7 +62,7 @@
  * FixMessageBuilder used for constructing messages to be sent.
  * Tags 8 BeginString, 9 MessageLength and 10 CheckSum are automatically appended in the correct order.
  * The message length and checksum can be overridden with the {@link #overrideMessageLength(String)}. and {@link #overrideChecksum(String)} methods.
- * All other fix tags & values are appended to the fix message in the order that they are specified.
+ * All other fix tags and values are appended to the fix message in the order that they are specified.
  * Care must be taken to ensure the order of fields is valid for the version of the FIX protocol being used.
  */
 public class FixMessageBuilder {