Skip to content

Commit

Permalink
Prepare version 0.15.1
Browse files Browse the repository at this point in the history
  • Loading branch information
gabrielittner committed May 2, 2021
1 parent 8a33630 commit c7d7370
Show file tree
Hide file tree
Showing 3 changed files with 20 additions and 12 deletions.
20 changes: 14 additions & 6 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,24 +3,32 @@
Version 0.16.0 *(In development)*
---------------------------------

Version 0.15.1 *(2021-05-02)*
---------------------------------

- The `closeAndReleaseRepository` task was mistakenly expecting the wrong Gradle properties. The README and changelog also mentioned the wrong properties. The correct ones are `mavenCentralUsername` and `mavenCentralPassword` or for environment variables: `ORG_GRADLE_PROJECT_mavenCentralUsername` and `ORG_GRADLE_PROJECT_mavenCentralPassword`.
- Fix `signing` not being configurable until `afterEvaluate`
- Use empty string as in memory signing password when no password is specified
- Fix `statingProfile` in `nexusOptions` not being optional which causes an error when running `closeAndReleaseRepository`


Version 0.15.0 *(2021-04-24)*
---------------------------------

- **BREAKING**: Removed support for deprecated `RELEASE_REPOSITORY_URL`, `SNAPSHOT_REPOSITORY_URL`, `SONATYPE_NEXUS_USERNAME`, `SONATYPE_NEXUS_PASSWORD` environment variables and properties.
For safety reasons the project will fail when finding these. Use `mavenCentralRepositoryUsername` and `mavenCentralRepositoryPassword` Gradle properties or
`ORG_GRADLE_PROJECT_mavenCentralRepositoryUsername` and `ORG_GRADLE_PROJECT_mavenCentralRepositoryPassword` environment variables instead.
- **BREAKING**: Removed support for deprecated `RELEASE_REPOSITORY_URL`, `SNAPSHOT_REPOSITORY_URL`, `SONATYPE_NEXUS_USERNAME`, `SONATYPE_NEXUS_PASSWORD` environment variables and properties.
For safety reasons the project will fail when finding these. Use `mavenCentralUsername` and `mavenCentralPassword` Gradle properties or
`ORG_GRADLE_PROJECT_mavenCentralUsername` and `ORG_GRADLE_PROJECT_mavenCentralPassword` environment variables instead.
- **BREAKING**: Removed deprecated `targets` API. See README for alternative ways of adding targets.
- Behavior change: The dokka plugin is not applied by default anymore for Kotlin projects. When it is applied we will still use the dokka tasks to create the javadoc jar.
- Support for `s01.oss.sonatype.org` by setting `sonatypeHost = "S01"`.
- Introduce `com.vanniktech.maven.publish.base` plugin. This plugin contains all the functionality of the main plugin, but does not configure anything automatically.
Instead, it offers a public API, which is also used by the main plugin to do so yourself. This allows for more flexibility and to publish different project types.
- Introduce `com.vanniktech.maven.publish.base` plugin. This plugin contains all the functionality of the main plugin, but does not configure anything automatically.
Instead, it offers a public API, which is also used by the main plugin to do so yourself. This allows for more flexibility and to publish different project types.
The API is not final yet, but we're happy to receive feedback.

Version 0.14.2 *(2021-02-14)*
---------------------------------

- fix artifact id in Kotlin Multiplatform projects being incorrect
- fix artifact id in Kotlin Multiplatform projects being incorrect
- fix `closeAndReleaseRepository` requiring callers to pass `--repository`

Version 0.14.1 *(2021-02-11)*
Expand Down
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ buildscript {
mavenCentral()
}
dependencies {
classpath 'com.vanniktech:gradle-maven-publish-plugin:0.15.0'
classpath 'com.vanniktech:gradle-maven-publish-plugin:0.15.1'
}
}
Expand Down Expand Up @@ -168,7 +168,7 @@ It assumes there's only one staging repository active when closeAndReleaseReposi

# Base plugin

Starting with version 0.15.0 there is a base plugin. This new plugin has the same capabilities as the main
Starting with version 0.15.0 there is a base plugin. This new plugin has the same capabilities as the main
plugin but does not configure anything automatically. In the current stage the APIs are still marked with `@Incubating`
so they might change.

Expand All @@ -181,14 +181,14 @@ allprojects {
plugins.withId("com.vanniktech.maven.publish.base") {
GROUP = "com.example.project"
VERSION = "1.0.3-SNAPSHOT"
mavenPublishing {
publishToMavenCentral("DEFAULT")
// Will only apply to non snapshot builds.
// Uses credentials as described above, supports both regular and in memory signing.
signAllPublications()
pom {
name = "My Library"
description = "A description of what my library does."
Expand Down
2 changes: 1 addition & 1 deletion gradle.properties
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
GROUP=com.vanniktech
VERSION_NAME=0.16.0-SNAPSHOT
VERSION_NAME=0.15.1

POM_ARTIFACT_ID=gradle-maven-publish-plugin
POM_NAME=Gradle Maven Publish Plugin
Expand Down

0 comments on commit c7d7370

Please sign in to comment.