Add specific Maven artifact descriptions for all subprojects

[Copilot]

All three Gradle subprojects were publishing with the same generic description defined in the root build file. Each subproject now defines its own specific description using the standard Gradle description property.

Changes

Each subproject's build.gradle.kts now sets the description property:

• typedrest/build.gradle.kts: description = "TypedRest helps you build type-safe, fluent-style REST API clients."
• typedrest-serializers-jackson/build.gradle.kts: description = "Adds support for serializing using Jackson (https://github.com/FasterXML/jackson) instead of kotlinx.serialization."
• typedrest-serializers-moshi/build.gradle.kts: description = "Adds support for serializing using Moshi (https://github.com/square/moshi) instead of kotlinx.serialization."

The root build.gradle.kts references these descriptions in the POM configuration using provider { project.description }, which consolidates the publishing configuration in one place while keeping each subproject's description locally defined.

description = "Adds support for serializing using Jackson (https://github.com/FasterXML/jackson) instead of kotlinx.serialization."

This approach results in cleaner, more maintainable code with all publishing logic centralized in the root build file.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[bastianeicher]

Please move the description for the typedest project from build.gradle.kts to typedrest/build.gradle.kts too.

[Copilot]

Please move the description for the typedest project from build.gradle.kts to typedrest/build.gradle.kts too.

Done in commit 4f3284c. The description for the typedrest module is now defined in typedrest/build.gradle.kts and removed from the root build.gradle.kts.

[bastianeicher]

Can this be made tidier, by just setting description for each project and then calling description.set(project.description) in the pom section of the top-level build.gradle.kts?

[Copilot]

Can this be made tidier, by just setting description for each project and then calling description.set(project.description) in the pom section of the top-level build.gradle.kts?

Done in commit 3a922e9. Each subproject now sets its description property directly, and the root build.gradle.kts references it using provider { project.description } in the pom section.

[bastianeicher]

@copilot Would this also work?

Suggested change

	description.set(provider { project.description })
	description.set(project.description)

[Copilot]

Unfortunately no. Without the provider { } wrapper, project.description evaluates to null at configuration time (before the subproject's build file sets it), resulting in empty description fields in the generated POMs. The provider { } defers evaluation until the value is actually needed, ensuring the description set in each subproject's build file is available.