Hi all, in PLC4X we have a maven-plugin that we use to generate code for PLC4X itself. In order to avoid super-messy releases, we have that plugin and similar build-tools in a separate repo. This is released using the normal release process.
It does help however to cut the build-tools to work in a modular way, so while our code-generator plugin is in the build-tools, the templates themselves are in the main repo. This reduces the frequency in which we need releases of the tools dramatically. So having the plugin look for templates in the runtime classpath of the module, makes the build super-easy. Perhaps something worth considering. But yes: If you want the artifacts in Maven-Central, then you'll need a full release cycle. You could probably however stage a RC in repository.apache.org and close it. Then you get a temporary maven repo URL. If you then add this url to the project, so Maven/SBT is able to use that, and then you could create and stage an RC for the main project in parallel ... you would then have two closed repos in Nexus and could do the vote on both artifacts in one round. If the vote passes, then you simply release both repositories. Chris Am 04.07.23, 13:22 schrieb "Ryan Skraba" <rskr...@apache.org <mailto:rskr...@apache.org>>: Hello! I think, in principle, the vote is the right thing to do. Is this artifact likely to change frequently? My experience with sbt plugins is that they are usually pretty tightly integrated with the projects that depend on them. If this is the case you might want to have it released at the same cadence as the projects that are using it (i.e. validated with the project that uses it). I know this is tricky with sbt. In any case, I can definitely be more present for validating these releases and getting these through. The "incubator process" shouldn't prevent you from doing the right thing for your project and community! All my best, Ryan On Tue, Jul 4, 2023 at 11:52 AM PJ Fanning <fannin...@gmail.com <mailto:fannin...@gmail.com>> wrote: > > Thanks Claude but I am not familiar with the terminology of 'Petri > route'. Would you be able to provide more detail? > > So far based on the existing feedback - the aim is to just set up an > RC for this component and go through the regular voting process on it. > A Pekko community discussion and vote followed by an Incubator team > vote. > > > On Tue, 4 Jul 2023 at 10:44, Claude Warren <cla...@apache.org > <mailto:cla...@apache.org>> wrote: > > > > You could try the Petri route if the devs are ASF members. > > > > On Mon, Jul 3, 2023 at 5:12 PM Sheng Wu <wush...@apache.org > > <mailto:wush...@apache.org>> wrote: > > > > > Hi > > > > > > If we want that jar under asf package on maven central, yes, a new version > > > is required a vote on dev first, then incubator. > > > Meanwhile, if we have all mentors(ipmc members as well) voted, we just > > > need to carry votes to incubator mail list, and another 3 days. > > > > > > Just one thing, if the jar has dependencies, we need to check license > > > compatibility. > > > > > > PJ Fanning <fannin...@gmail.com <mailto:fannin...@gmail.com>>于2023年7月3日 > > > 周一17:06写道： > > > > > >> Adding the Pekko mentors to the thread if that's ok. > > >> > > >> It's not a blocker for us to use a snapshot version of the > > >> Pekko-specific build tool but it would be tidier if we could release a > > >> stable version to Maven Central. If this requires us to release a > > >> source artifact via the full voting procedure then that is fine. I > > >> just want to make sure that this is a necessary step before going that > > >> route. > > >> > > >> On Wed, 28 Jun 2023 at 18:38, PJ Fanning <fannin...@apache.org > > >> <mailto:fannin...@apache.org>> wrote: > > >> > > > >> > Hi everyone, > > >> > > > >> > The Apache Pekko community has a tool that is used as part of building > > >> > our web site [1]. > > >> > sbt-paradox-pekko [2] applies the theme to the Pekko web site. It is > > >> > not useful for outside users. > > >> > We require that a Java/Scala jar is published because this tool is > > >> > used in a number of different Pekko projects (ie different Apache git > > >> > repos that the Pekko team maintain). > > >> > We haven't yet released an official 1.0.0 jar and are using a snapshot > > >> jar. > > >> > If we wanted to publish an official 1.0.0 jar, would we need to have > > >> > an Incubator PMC vote on it. We will have a Pekko discussion and > > >> > possibly a vote if it seems appropriate. > > >> > > > >> > Any insights would be appreciated. > > >> > > > >> > Regards, > > >> > PJ > > >> > > > >> > [1] https://pekko.apache.org <https://pekko.apache.org> > > >> > [2] https://github.com/apache/incubator-pekko-sbt-paradox > > >> > <https://github.com/apache/incubator-pekko-sbt-paradox> > > >> > > > -- > > > Sheng Wu 吴晟 > > > > > > Apache SkyWalking > > > Apache Incubator > > > Apache ShardingSphere, ECharts, DolphinScheduler podlings > > > Zipkin > > > Twitter, wusheng1108 > > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org <mailto:general-unsubscr...@incubator.apache.org> For additional commands, e-mail: general-h...@incubator.apache.org <mailto:general-h...@incubator.apache.org>
