I wonder if the changes have been ported to surefire and javadoc? Or maybe not needed as no impact? Sorry just a question from the peanut gallery (as I didn't have a look at the changes). But I remember suffering (because I was more involved at this time) a lot of issues in the past when JPMS was included as part the tooling via plexus-java and most of the plugins were not in sync regarding JPMS . Some weird (bad) workaround were needed to make all those plugins working together with JPMS.
On Thu, 24 Oct 2024 at 00:22, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > What is the easiest way to determine what has been changed? When I was > working on Log4j’s JPMS support Maven’s handling of JPMS frequently caused > problems and forced us to do some things I consider kind of ugly. > > Ralph > > > On Oct 23, 2024, at 7:12 AM, Guillaume Nodet <gno...@apache.org> wrote: > > > > Following the beta-5 release, we're going to update a bunch of plugins > > (help welcome to port a few core plugins). > > In particular, I think the maven-compiler-plugin would benefit from a merge > > of Martin Deruisseaux's work around JPMS [1]. This leverages the > > javax.tools API directly, so will remove the plexus dependency and will > > certainly lead to some disruption, but ... that's what betas are for. > > > > So unless there's a strong objection, I think we should merge Martin's > > work... > > > > [1] https://github.com/Geomatys/maven-compiler-plugin > > > > > > -- > > ------------------------ > > Guillaume Nodet > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
