Skip to content

Commit

Permalink
configure publishing for the release variant
Browse files Browse the repository at this point in the history
The publishing plugin didn't have any publications set up. The `./gradlew publish` and `./gradlew publishToMavenLocal` tasks would execute and pass, but they were essentially no-ops. Now, they'll actually create artifacts.
  • Loading branch information
RBusarow authored and rjrjr committed Apr 30, 2024
1 parent 8913bb0 commit 3ac8119
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion build.gradle.kts
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@
* See the License for the specific language governing permissions and
* limitations under the License.
*/
import com.vanniktech.maven.publish.AndroidSingleVariantLibrary
import com.vanniktech.maven.publish.MavenPublishBaseExtension
import com.vanniktech.maven.publish.SonatypeHost
import kotlinx.validation.ApiValidationExtension
Expand Down Expand Up @@ -58,7 +59,7 @@ extensions.configure<ApiValidationExtension> {
"compose-tests",
"compose-unsupported-tests",
"sample",
"sample-compose"
"sample-compose",
)
}

Expand All @@ -78,6 +79,10 @@ subprojects {
publishToMavenCentral(SonatypeHost.S01)
signAllPublications()
pomFromGradleProperties()

configure(
AndroidSingleVariantLibrary(variant = "release", sourcesJar = true, publishJavadocJar = true),
)
}
}

Expand Down

0 comments on commit 3ac8119

Please sign in to comment.