Re: plexus-utils 4.x and Xpp3DomBuilder

can you try plexus-xml 3.0.0 and confirm this works as you expected initially, please? Regards, Hervé Le mardi 25 juillet 2023, 20:56:04 CEST Slawomir Jaranowski a écrit : > Hi > > I'm trying to update plexus-utils 3.5.x to plexus-utils/plexus-xml 4.x in > maven-enforcer > > In maven-enf

Re: [VOTE] Release Apache Maven Javadoc Plugin version 3.6.0

Thank you for the feedback. I am clearly rusty with apache releases (and this is not my regular computer, as I am traveling) On Tue, Sep 12, 2023 at 10:51 AM Tamás Cservenák wrote: > Howdy, > > Staging repository > https://repository.apache.org/content/repositories/maven-1989 - closed the repo

Re: [VOTE] Release Apache Maven Javadoc Plugin version 3.6.0

MJAVADOC-747 and MJAVADOC-764 are listed as blockers. Please reclassify these if they're not truly release blockers. On Tue, Sep 12, 2023 at 2:23 AM Henning Schmiedehausen wrote: > > Hi, > > We solved 16 > issues:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=1

Re: [VOTE] Release Apache Maven Javadoc Plugin version 3.6.0

Howdy, Staging repository https://repository.apache.org/content/repositories/maven-1989 But few nits more aside of GPG signature: - JIRA contains one open issue (!) - JIRA contains an unassigned issue, which is kinda strange (who fixed it?) - not a deal breaker - JIRA contains several non-closed

Re: How to fix MNG-7855 (dependencies wrongly put on class-path rather than module-path)?

+1 to drop any magic by default in a new major, seems the most reliable for end users. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: [VOTE] Release Apache Maven Javadoc Plugin version 3.6.0

Hi Please add your signing key to - https://svn.apache.org/repos/asf/maven/project/KEYS Your key should be also available on public key server, like: - https://pgp.mit.edu/ - https://keyserver.ubuntu.com/ You also can consider to be listed at: https://maven.apache.org/team.html - please update

Re: How to fix MNG-7855 (dependencies wrongly put on class-path rather than module-path)?

A possible improvement to Maven default behaviour (when no option is provided by the user) could be as below. The current rule followed by Maven is to put a JAR on the module-path if and only if the two following conditions are true: 1. The JAR is JPMS 2. The application using that JAR is itse

Re: How to fix MNG-7855 (dependencies wrongly put on class-path rather than module-path)?

Le 2023-09-12 à 07 h 16, Henning Schmiedehausen a écrit : Maven spends a lot of time trying to deal with corner cases and I am not sure that we get them right. The thing is that putting a JAR on the module-path versus class-path can change application behaviour, no matter if JPMS or not. This