message has been deleted

@Yongjun Hong If you need to estimate my availability when moving a meeting, https://calendly.com/onenashev/virtual-coffee is the best estimation

@Yongjun Hong I'm so sorry, but we have to move the meeting on Wednesday again. I have a court hearing and it looks like it will take longer than initially anticipated. Would you be fine with meeting on Thursday or Friday? My plan for reviews and GitHub issues is today

@Yongjun Hong For testing Gradle plugins: • https://docs.gradle.org/current/userguide/testing_gradle_plugins.html , especially https://docs.gradle.org/current/userguide/testing_gradle_plugins.html#implementing_automated_tests • The patch from the screenshare - https://github.com/YongGoose/kotlin-pom-gradle/pull/12/commits/198641e82e341959aecac3b7703295f67cbf513f

@Yongjun Hong just saw the pings on GitHub. Please do not hesitate to ping here. Sadly, I am on too many projects and my GitHub notifications are overflowing at the moment

Hi, Not sure if this is the correct channel to ask but With the OSSRH being sunset I am no longer able to login to oss.sonatype.com where as I can login to the central.sonatype.org . Is this the expected behaviour ? Also I don't see my namespace(group id) with which I use to publish my android artifacts in the central repository . How can I go about fixing this ?

@Yongjun Hong are we meeting today?

@Yongjun Hong do you want to meet today?

@Martin @Gabriel Ittner @Andres Almiray If you're interested to add short summaries/examples to https://cookbook.gradle.org/integrations/maven-central/publishing/ , I think it would be a win at this stage

FWIW JReleaser provides an example that may be used as a starting point https://jreleaser.org/guide/latest/examples/maven/maven-central.html

has renamed the channel from "maven-central-publishing" to "maven-central"

set the channel description: All things Maven Central related: from publishing to mirroring inside corporate networks

Hey folks, Renamed the channel so that we cover all interactions with Maven Central here: from publishing to mirroring.

@Yongjun Hong do you want to meet tomorrow? I am at the conference and the time looks complicated. Thursday or Friday the same time would be better

@Yongjun Hong to follow-up on the debugging session we had today, the approach with generating files in the build directory will not work as Gradle does not record such injected artifacts in Publishing metadata. You will need to finish the test started 2 weeks ago and get it to the stage that test application is actually built and the artifacts are actually signed via the

signing

plugin. https://github.com/YongGoose/kotlin-pom-gradle/pull/33/commits/54c8a1ea2d6b94e581a76fa11e9286518459c122 makes some progress towards that, but there is more work to be done. If it becomes too complicated to develop the sample project in tests, you can just do it as a separate project, and then copy configurations into the test (as well as test signing keys). Please provide me with an update on your progress by Saturday noon UTC. I will follow up on the administrative bits separately. And, please, do not hesitate to ask any questions on Slack.

Hello! I’d like to share a plugin I developed during the GSoC project period. This Gradle plugin helps you manage Maven POM metadata more easily and efficiently. Main features are: 1. Define a POM in the root project and manage it hierarchically. 2. Artifact signature verification. 3. POM validation. The current release is version 0.1.6, and I believe there’s still plenty of room for improvement. • https://plugins.gradle.org/plugin/io.github.yonggoose.kotlin-pom-gradle-artifact-check-project (For Artifact Signing & POM Validation) • https://plugins.gradle.org/plugin/io.github.yonggoose.kotlin-pom-gradle-project (For hierarchical POM configuration) I’d really appreciate it if you could give it a try and share your feedback! The detailed usage instructions are available in the demo video and the README.

@Yongjun Hong According to https://github.com/YongGoose/kotlin-pom-gradle, I am the only person watching the repository. It may sound counter-intuitive to say the least, but new GitHub repository creators do not automatically get added to the watch list of the repo they have just created

@Yongjun Hong I am merging the project page patches, but please keep the comment in mind: https://github.com/gradle/community/pull/239#pullrequestreview-3138151425

@Oleg Nenashev I’ve updated my blog post! Please take another look 🙂

@Yongjun Hong https://github.com/YongGoose/kotlin-pom-gradle still does not have a release tag/changelog for your last announcement. is it expected?

Cover image looks good 😂 https://dev.to/gradle-community/centralized-pom-configuration-management-with-kotlin-pom-gradle-1kap

@Oleg Nenashev I created several PRs related to documentation (README, repo name). Please take a look! • https://github.com/YongGoose/Maven-Central-utility-plugins-for-Gradle/pull/40 • https://github.com/YongGoose/Maven-Central-utility-plugins-for-Gradle/pull/39 • https://github.com/gradle/community/pull/242

Version 0.1.7 has been released! 🚀 In this version, we resolved issues related to the license field and redefined required fields. We also completed the documentation. You can check the updates and download the latest plugin from the link below. • https://plugins.gradle.org/plugin/io.github.yonggoose.maven.central.utility.plugin.check • https://plugins.gradle.org/plugin/io.github.yonggoose.maven.central.utility.plugin.project • https://plugins.gradle.org/plugin/io.github.yonggoose.maven.central.utility.plugin.setting • https://github.com/YongGoose/Maven-Central-utility-plugins-for-Gradle/releases/tag/v0.1.7 P.S. Version 0.1.8 is scheduled to be released on Maven Central.

@Oleg Nenashev I have an urgent appointment tomorrow—would it be okay to move the meeting to Thursday?

Yep, it should be ok

@Yongjun Hong Did you have a chance to promote https://dev.to/gradle-community/centralized-pom-configuration-management-with-kotlin-pom-gradle-1kap on social media? I have not seen posts

I’m planning to proceed after writing a blog about artifact signing & validation!

@Yongjun Hong no meeting today, right?

Yes!

@Yongjun Hong sorry, I got ill :( I assume we do not have a meeting today, but, just in case, I suggest moving it to the next week