I replied to this thread from lists.a.o since I didn’t get Volkan’s email but I have not seen the moderation request yet. I have a few comments to this.
> On Jul 3, 2023, at 8:36 AM, Matt Sicker <m...@musigma.org> wrote: > > Reply is inline below: > >> *The distribution must contain binaries too* >> >> I disagree with this sentiment. Yet there are multiple PMC members >> practicing this "copy-pasting downloaded JARs to the server" tradition. >> Hence, the new release procedure bundles binaries too. > > Making a source release to downloads.a.o along with publishing all our usual > jar files (binaries and sources) covers our main channels here. When Log4j2 > was mainly the API and Core modules, then it seemed more reasonable that > people would be downloading the jar files without a dependency manager, but > with the increased modularity and continued industry convergence on using > dependency managers, I think this approach would be sufficient. People still download from dist.a.o. I have no idea why but I know they do as I have gotten emails regarding the asc file not containing the data in the “correct” format. > >> *What is next?* >> >> Distribute this logic in `logging-parent` POM and reuse it in >> `logging-log4j-transform` as a PoC. > > I’d love to reuse this in the Kotlin API, too. The easier this all is to use, > the easier it’ll be to maintain multiple repositories. Hence my insistence that this be a true Maven plugin, not a script. Ralph
