> We have a few sbt plugins that we use in our builds that are Pekko specific but that were developed outside the Pekko podling to lessen the release overhead. It is probably best to bring them under the Apache Pekko project now especially since they are relatively stable now.
Strongly agreed although for other reasons that aren't just about release difficulty. Having critical parts of pekko build sitting in personal repo's isn't really in the spirit/ethos of ASF as it creates a kind of gatekeeping that we are sought of experiencing right now[1] 1: https://github.com/pjfanning/sbt-pekko-build/pull/14#issuecomment-2071015192 > addSbtPlugin("org.mdedetrich" % "sbt-apache-sonatype" % "0.1.11") addSbtPlugin("com.github.pjfanning" % "sbt-source-dist" % "0.1.12") addSbtPlugin("com.github.pjfanning" % "sbt-pekko-build" % "0.3.3") > sbt-pekko-build depends on sbt-apache-sonatype so it is best to leave that until we get sbt-apache-sonatype imported. > Anyone with any objections? This isn't an objection, but purely on technical terms only sbt-pekko-build are purely Pekko specific. sbt-apache-sonatype/sbt-source-dist are actually generic to any Apache project that happens to use sbt, i.e. there isn't anything Pekko specific there. This was raised before about where those projects should be placed, i.e. a better place for those projects might be INFRA or maybe for them to be their own project albeit this can be considered quite excessive. On Fri, Apr 19, 2024 at 9:41 PM PJ Fanning <fannin...@apache.org> wrote: > > Hi everyone, > > We have a few sbt plugins that we use in our builds that are Pekko > specific but that were developed outside the Pekko podling to lessen > the release overhead. It is probably best to bring them under the > Apache Pekko project now especially since they are relatively stable > now. > > addSbtPlugin("org.mdedetrich" % "sbt-apache-sonatype" % "0.1.11") > addSbtPlugin("com.github.pjfanning" % "sbt-source-dist" % "0.1.12") > addSbtPlugin("com.github.pjfanning" % "sbt-pekko-build" % "0.3.3") > > sbt-pekko-build depends on sbt-apache-sonatype so it is best to leave > that until we get sbt-apache-sonatype imported. > > Anyone with any objections? > > Regards, > PJ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > For additional commands, e-mail: dev-h...@pekko.apache.org > -- Matthew de Detrich Aiven Deutschland GmbH Immanuelkirchstraße 26, 10405 Berlin Alexanderufer 3-7, 10117 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen m: +491603708037 w: aiven.io e: matthew.dedetr...@aiven.io --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org For additional commands, e-mail: dev-h...@pekko.apache.org
