Re: JPMS support, refactored proposal

Le 2024-01-02 à 20 h 51, Romain Manni-Bucau a écrit : RMB: so you mean you don't intend to link the classpath to the type? Not directly. The code dispatching JAR files between classpath, module-path, etc., bases fully its decision on the following: * DependencyProperties * Sometime whethe

Re: JPMS support, refactored proposal

Le mar. 2 janv. 2024 à 18:46, Martin Desruisseaux < martin.desruisse...@geomatys.com> a écrit : > Hello Romain > > Le 2024-01-02 à 18 h 16, Romain Manni-Bucau a écrit : > > > In other words you deprecated isAddedToClasspath cause it was too > > rigid to put in place something as rigid which enable

Re: JPMS support, refactored proposal

Hello Romain Le 2024-01-02 à 18 h 16, Romain Manni-Bucau a écrit : In other words you deprecated isAddedToClasspath cause it was too rigid to put in place something as rigid which enables one rare (today) case so I'm not very enthusiatic about it. The proposed replacement is not as rigid, be

Re: [VOTE] Release Maven Surefire version 3.2.4

Am 2024-01-02 um 18:28 schrieb Marc Philipp: Hi all, We noticed that (due to https://github.com/apache/maven-surefire/pull/702) `error` and `failure` elements no longer contain the stack trace as their content (without a `stackTrace` element). We think this is a regression that needs to be addre

Re: [VOTE] Release Maven Surefire version 3.2.4

Hi all, We noticed that (due to https://github.com/apache/maven-surefire/pull/702) `error` and `failure` elements no longer contain the stack trace as their content (without a `stackTrace` element). We think this is a regression that needs to be addressed prior to releasing 3.2.4. Please let me k

Re: JPMS support, refactored proposal

Hi Martin, Think this propagate current lock situation where you only work in a particular subset of builds so I still think we should extract getDispatchedPaths , PathType etc to something like maven-shared (or nothing) and just make this logic owned by plugins, this is the only location it makes

Re: JPMS support, refactored proposal

Le 2024-01-02 à 17 h 44, Martin Desruisseaux a écrit : (…snip…) First, the (class, module, etc.)-paths, later the source directories (I wish Maven supports Module Source Hierarchy), in which case I will try to address multi-releases in same time. Actually, I have been silent on this topic in

Re: JPMS support, refactored proposal

Hello David Le 2024-01-02 à 17 h 36, David Lloyd a écrit : Apologies if this was already covered somewhere else, but would (or could) path accumulation support multi-release JAR layouts for all cases (whether it be modular or class-path JARs or filesystem paths)? The current proposal does no

Re: JPMS support, refactored proposal

Apologies if this was already covered somewhere else, but would (or could) path accumulation support multi-release JAR layouts for all cases (whether it be modular or class-path JARs or filesystem paths)? On Tue, Jan 2, 2024 at 10:13 AM Martin Desruisseaux < martin.desruisse...@geomatys.com> wrote

JPMS support, refactored proposal

Hello all Following the recommendations in the "Guidance on Maven 4 API issue" thread, I refactored the proposal. The new commits (only 2 at this time) replace the previous ones. Commit 1 The first commit [1] adds the following constants in the API: * In Type interface: POM, JAR, CLASS

Re: [VOTE] Release Maven Surefire version 3.2.4

+1 wt., 2 sty 2024, 16:18 użytkownik Romain Manni-Bucau napisał: > +1 > > Romain Manni-Bucau > @rmannibucau | Blog > | Old Blog > | Github < > https://github.com/rmannibucau> | > LinkedIn

Re: [VOTE] Release Maven Surefire version 3.2.4

+1 Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book

Re: mvn archetypes live?

Hello! the PR was reworked to 4 PRs. They are again eager for review. Ty! J. On 12/19/23 09:46, Jiri Vanek wrote: Hello! I have a PR fo maven arechetypes: https://github.com/apache/maven-archetypes/pull/18 And I would like to have several more on this topic (1.7->1.8 bump). To do so,I need