> Any insights or suggestions I would suggest staying with the maven toolchain, given the JPI plugin is feature stalled and we stopped onboarding plugins using Gradle over Maven more than a year ago. If loss of functionality, stability, and support is no concern, you may use Gradle.
> On 13. Feb 2024, at 10:02, Sandeep Kumar <[email protected]> wrote: > > Hi Team, > > In the p4-plugin, I have made the switch from Maven to Gradle as the build > tool using "gradle-jpi-plugin" > (https://github.com/jenkinsci/gradle-jpi-plugin). > > Before publishing, I want to gather feedback from the community to address > any potential issues that may have been overlooked during this migration. > > The Gradle file for the plugin can be found here: > https://github.com/jenkinsci/p4-plugin/blob/master/build.gradle. Any insights > or suggestions from the community would be highly appreciated. > > Also, Which repository should be prioritized for publishing artifacts: > https://repo.jenkins-ci.org/public/ or https://repo.jenkins-ci.org/releases? > > P4-Plugin: https://github.com/jenkinsci/p4-plugin > > Thanks > Sandeep Kumar > [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/1e67637a-6da6-499e-9e0c-5c746d746ff6n%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/1e67637a-6da6-499e-9e0c-5c746d746ff6n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6403749B-05E2-49EA-82F6-864E57FE5CE1%40notmyfault.dev.
