apache-maven-3.9.5: JVM and Command Line Options

using documentation: https://maven.apache.org/docs/3.3.1/release-notes.html#jvm-and-command-line-options So for example if you put the following JVM options into the|.mvn/jvm.config|file getting error: org.apache.commons.cli.ParseException: Unrecognized maven.config file entries: [mx2048m

Re: NPE in AbstractMavenReport.execute, because 'this.siteTool' is null

Hello Hervé. I am sorry, if my explanations were too complicated for you. I just repeated everything from scratch for you, directly from my Git Bash console: $ git clone https://github.com/dev-aspectj/aspectj-maven-plugin.g

Re: NPE in AbstractMavenReport.execute, because 'this.siteTool' is null

I tried to build the project and see the failure, but could not and reading explanations did not help me what we need is a basic commit that works, followed by a PR upgrading Doxia and that does not work with the NPE that you are saying happens Regards, Hervé On 2023/10/10 02:44:08 Alexander K

Re: Dependency JDK convergence rule?

Hi, Did you try: https://www.mojohaus.org/extra-enforcer-rules/enforceBytecodeVersion.html wt., 10 paź 2023 o 14:40 Florent Biville napisał(a): > Hello, > > I could not find what I'm looking for in the built-in rules of the enforcer > plugin: https://maven.apache.org/enforcer/enforcer-rules/ind

Dependency JDK convergence rule?

Hello, I could not find what I'm looking for in the built-in rules of the enforcer plugin: https://maven.apache.org/enforcer/enforcer-rules/index.html. Is there something available today to make sure that all dependencies have the same JDK baseline? Is it even feasible to implement such a check?