Skip to content

publishing.md

Latest commit

 

History

History
59 lines (39 loc) · 1.3 KB

publishing.md

File metadata and controls

59 lines (39 loc) · 1.3 KB
Raw

Project-local Maven publishing

The 4.0.0 build can publish signed artifacts into a Maven repository inside the project rather than ~/.m2.

The names and coordinates below are the historical NilKit 4.0.0 values. They should be changed consistently when the NilKit API rename is applied to Gradle metadata.

Publish

./gradlew publishProjectLocal

Windows:

gradlew.bat publishProjectLocal

Historical repository path:

maven/me/tamkungz/nilkit/nilkit/4.0.0/

Historical classified artifacts:

nilkit-4.0.0-all.jar
nilkit-4.0.0-mapping-tool.jar

The publication also includes the normal JAR, sources JAR, Javadoc JAR, POM/module metadata, checksums, and OpenPGP signatures.

GPG

The build uses Gradle useGpgCmd() and therefore your normal GnuPG configuration and gpg-agent.

To choose a specific key, prefer your user Gradle configuration:

signing.gnupg.keyName=YOUR_KEY_ID

Do not commit private keys or passphrases to the repository.

Consumer example (historical coordinates)

repositories {
    maven { url = uri('/absolute/path/to/project/maven') }
}

dependencies {
    implementation 'me.tamkungz.nilkit:nilkit:4.0.0'
}

These coordinates should not be copied into new NilKit documentation after the rename is finalized.