Re: Maven 5 pom extension for agents

Le 2023-10-29 à 21 h 36, Romain Manni-Bucau a écrit : Was referencing the options using module names, if you drop the dep or reference a package not supported by the module we should be able to fail. I do not want to distract this thread from the core issue (control on class-path versus

Re: Maven 5 pom extension for agents

Hi Martin, this assumes all plugins + runtimes will use the exact same option whereas this is generally not true so must be configured per mojo when forking and in jvm.config when not forking so I don't see any work done at dependency/artifact level working on jvm ecosystem. Romain Manni-Bucau

Re: Maven 5 pom extension for agents

Le 2023-11-02 à 10 h 49, Romain Manni-Bucau a écrit : this assumes all plugins + runtimes will use the exact same option whereas this is generally not true so must be configured per mojo when forking and in jvm.config when not forking so I don't see any work done at dependency/artifact level

Re: Maven 5 pom extension for agents

Howdy, Unsure about your remark "you are still not solving the transitivity": As consume-module in Maven debug outputs this (but, debug shows only scope not type, as before whole universe was "jar"): [DEBUG] org.cstamas.maven.jpms.modular:consume-module:jar:1.0.0-SNAPSHOT [DEBUG]

Re: Maven 5 pom extension for agents

@Martin: you are right they are orthogonal in terms of design but as soon as you get the set notion you don't need the others and I prefer to not multiply the way to do which is always confusing. Since the dependency option does not work generally speaking, I'm clearly on the other side *if we

Re: Maven 5 pom extension for agents

@Tamas: when you import a type=module dependency, how do I get its module transitive deps or how do I not get it when it is imported as a jar? type=module => transitive modules=module so means you assume the original pom is deployed on central (this is really an assumption even with maven where it

Re: Maven 5 pom extension for agents

Hi Tamas, You table shows exactly my point: you need to be able to compose dependencies sets (potentially named from user space) and you can *not* define types - or any similar solution - and let plugins get their config from there. If you don't you are not better than today and assume that in

Re: [VOTE] Release Apache Maven Daemon 1.0-m8

+1 czw., 26 paź 2023 o 08:44 Guillaume Nodet napisał(a): > I've staged a candidate release at > https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0-m8/ > > This release provides distributions based on Maven 3.9.5 and > 4.0.0-alpha-8 releases. > The release notes are available at : > >

Re: [VOTE] Release Maven PMD Plugin version 3.21.2

We have a release a special release notes page ... looks like incomplete https://maven.apache.org/plugins-archives/maven-pmd-plugin-LATEST/releasenotes.html pon., 30 paź 2023 o 22:11 Michael Osipov napisał(a): > Hi, > > we solved 6 issues: > >

Re: [VOTE] Release Maven PMD Plugin version 3.21.2

Last day, please have a look. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven PMD Plugin version 3.21.2

+1 wt., 31 paź 2023, 10:55 użytkownik Michael Osipov napisał: > +1 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >

Re: [VOTE] Release Maven PMD Plugin version 3.21.2

Am 2023-11-02 um 08:48 schrieb Slawomir Jaranowski: We have a release a special release notes page ... looks like incomplete https://maven.apache.org/plugins-archives/maven-pmd-plugin-LATEST/releasenotes.html I have removed this from the site because I don't know how to produce it and I am

Re: Maven 5 pom extension for agents

Just as a reminder: * type=module breaks downstream consumers not upgrading maven * transitivity is broken since everything ends in modulepath whereas in most cases you want it in the classpath So really we should move forward on something else than artifact definition as the sole solution if we

Re: Maven 5 pom extension for agents

Le 2023-11-02 à 11 h 21, Romain Manni-Bucau a écrit : you are right they are orthogonal in terms of design but as soon as you get the set notion you don't need the others and I prefer to not multiply the way to do which is always confusing. It is not necessarily a multiplication of ways of

Re: Maven 5 pom extension for agents

Le jeu. 2 nov. 2023 à 13:59, Tamás Cservenák a écrit : > Howdy, > > "not upgrading maven" can simply be extrapolated to "not upgrading java", > so what are we talking about at all here? Imposing illogical requirements > really does not make sense. (today) I'm writing app A, and I'm depending

Re: Maven 5 pom extension for agents

Le 2023-11-02 à 12 h 53, Romain Manni-Bucau a écrit : You would also note that using "type" *forces* users to care about this separation too in an unexpected way. Type is an optional element. The use of module is a workaround for the heuristic rules sometime doing the wrong choice. But

Re: Maven 5 pom extension for agents

Romain, Could you draft an example project that proves or at least showcases your points? It's probably me, but I don't get your responses :( WTH is "lifecycle of your project graph"? But really, could you draft an example project that showcases your points? T On Thu, Nov 2, 2023 at 2:08 PM

Re: Maven 5 pom extension for agents

Le jeu. 2 nov. 2023 à 12:37, Martin Desruisseaux < martin.desruisse...@geomatys.com> a écrit : > Le 2023-11-02 à 11 h 21, Romain Manni-Bucau a écrit : > > > you are right they are orthogonal in terms of design but as soon as > > you get the set notion you don't need the others and I prefer to not

Re: Maven 5 pom extension for agents

Just to chime in to Martin thoughts: - yes, the default "type" is still "jar" (so if you omit type, "jar" is applied as today) - transitivity: yes, as I show above, project-impl [type=module] depends on project-api [type=module] so the whole tree lands on "modulepath". - override: exactly as

Re: [VOTE] Release Maven Resolver 2.0.0-alpha-1

Am 2023-11-02 um 12:23 schrieb Tamás Cservenák: Howdy, Note: This is a preview release of Resolver 2.0.0, that would allow any downstream consumers to try it out and adapt. Most of the major issues were fixed, almost all of the functionality is there (compare JIRA "2.0.0" and "2.0.0-alpha-1"

Re: Maven 5 pom extension for agents

Le jeu. 2 nov. 2023 à 17:24, Tamás Cservenák a écrit : > Romain, > > Could you draft an example project that proves or at least showcases your > points? > It's probably me, but I don't get your responses :( > > WTH is "lifecycle of your project graph"? > > But really, could you draft an example

Re: Maven 5 pom extension for agents

Howdy, "not upgrading maven" can simply be extrapolated to "not upgrading java", so what are we talking about at all here? Imposing illogical requirements really does not make sense. The whole point of mvn4 is to allow progress at the same time not excluding the mvn3 universe (consumer POM).

Re: [VOTE] Release Maven PMD Plugin version 3.21.2

+1 On Mon, Oct 30, 2023, 22:11 Michael Osipov wrote: > Hi, > > we solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317621=12353789 > > There are still a couple of issues left in JIRA: > >

Re: Maven 5 pom extension for agents

Le jeu. 2 nov. 2023 à 19:49, Martin Desruisseaux < martin.desruisse...@geomatys.com> a écrit : > Le 2023-11-02 à 17 h 35, Romain Manni-Bucau a écrit : > > > Now, do the same example but with app in a classpath centric build > > (spring boot, EE, ...) which consumes lib1 as a classpath jar even if

Re: [VOTE] Release Maven PMD Plugin version 3.21.2

+1 pon., 30 paź 2023, 22:11 użytkownik Michael Osipov napisał: > Hi, > > we solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317621=12353789 > > There are still a couple of issues left in JIRA: > >

Re: Maven 5 pom extension for agents

Le 2023-11-02 à 17 h 35, Romain Manni-Bucau a écrit : Now, do the same example but with app in a classpath centric build (spring boot, EE, ...) which consumes lib1 as a classpath jar even if it is a module in its original pom (perfectly valid). Consuming lib1 on the classpath is *not*

Re: [VOTE] Release Apache Maven Daemon 1.0-m8

+1 On Thu, Nov 2, 2023 at 8:47 AM Slawomir Jaranowski wrote: > +1 > > czw., 26 paź 2023 o 08:44 Guillaume Nodet napisał(a): > > > I've staged a candidate release at > > https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0-m8/ > > > > This release provides distributions based on Maven

Re: [VOTE] Release Maven PMD Plugin version 3.21.2

+1 On Thu, Nov 2, 2023 at 7:43 PM Slawomir Jaranowski wrote: > +1 > > pon., 30 paź 2023, 22:11 użytkownik Michael Osipov > napisał: > > > Hi, > > > > we solved 6 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317621=12353789 > > > > There are still a

Re: Maven 5 pom extension for agents

Le 2023-11-02 à 20 h 07, Romain Manni-Bucau a écrit : as of today libs can't ignore classpath cause it stays the majority of consumers so it is "as if" in this thread IMHO. Maven can't ignore classpath. But for artifact producers, it is up to them to decide. They may target a niche market.

Re: [VOTE] Release Maven PMD Plugin version 3.21.2

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

[RESULT] [VOTE] Release Maven PMD Plugin version 3.21.2

Hi, The vote has passed with the following result: +1: Tamás Cservenák, Sylwester Lachiewicz, Michael Osipov, Romain Manni-Bucau, Slawomir Jaranowski, Arnaud Héritier PMC quorum: reached I will promote the artifacts to the central repo, the source release ZIP file and add this release the

[VOTE] Release Apache Maven Plugin Tools version 3.10.2

Hi, We solved 7 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12353719 There are still a couple of issues left in JIRA:

[VOTE] Release Maven Resolver 2.0.0-alpha-1

Howdy, Note: This is a preview release of Resolver 2.0.0, that would allow any downstream consumers to try it out and adapt. Most of the major issues were fixed, almost all of the functionality is there (compare JIRA "2.0.0" and "2.0.0-alpha-1" versions). IF the vote is successful, the staging