Speaking of JPMS, you might be interested that over at Apache Commons, we've started using the Moditect Maven plugin to generate module-info files automatically (see the parent POM if you're interested).
Gary On Wed, Sep 13, 2023 at 5:32 AM Volkan Yazıcı <vol...@yazi.ci> wrote: > > I support all 3 proposals: > > 1. using `bnd-maven-plugin` > 2. using it everywhere (i.e., making it a part of `logging-parent`, I > presume) > 3. using it for JMPS descriptors > > Does #3 only need to happen on `3.x`? Can't we implement this for `2.x` too? > > > On Wed, Sep 13, 2023 at 11:13 AM Piotr P. Karwasz <piotr.karw...@gmail.com> > wrote: > > > Hi, > > > > As you probably know many of our repos use `maven-bundle-plugin` (from > > Apache Felix) to create an OSGI descriptor for all our artifacts. The > > exception is `log4j-api-kotlin`, which uses `bnd-maven-plugin`. > > > > We would like to uniformise the building process and switch to the > > **exception** (`bnd-maven-plugin`) because: > > * both plugins use BND under the hood and `bnd-maven-plugin` is > > released by the same project as BND, > > * `bnd-maven-plugin` has a lifecycle coordinated with BND, so it > > always uses the newest BND version (no need to manage two > > dependencies). > > > > What do you think about this change? > > > > Moreover we could think about using BND to generate our JPMS > > descriptors in 3.x. These would be guaranteed to be compatible with > > our OSGI descriptor (see [1] for an example). > > > > Piotr > > > > [1] https://github.com/JCTools/JCTools/pull/370 > >
