Re: [VOTE] Release Maven Project Info Reports Plugin version 3.6.0

+1 On 2024/06/13 16:48:06 Michael Osipov wrote: > Hi, > > we solved 6 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821&version=12354774 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MPIR/issues > > Staging repo:

Re: [VOTE] Release Maven Project Info Reports Plugin version 3.6.0

+1 czw., 13 cze 2024 o 18:49 Michael Osipov napisał(a): > Hi, > > we solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821&version=12354774 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MPIR/issues > > Stag

[VOTE] Release Maven Release version 3.1.0

Hi, we solved 11 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824&version=12354221 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MRELEASE/issues Staging repo: https://repository.apache.org/content/repositories/maven-214

Re: [VOTE] Release Maven Project Info Reports Plugin version 3.6.0

+1 pt., 14 cze 2024, 09:48 użytkownik Slawomir Jaranowski < s.jaranow...@gmail.com> napisał: > +1 > > czw., 13 cze 2024 o 18:49 Michael Osipov napisał(a): > > > Hi, > > > > we solved 6 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821&version=12354774 >

[VOTE] Release Apache Maven mvnd 1.0.0

Howdy, Note: mvnd 1.x will from now on wrapping Maven 3.9.x and 2.x will wrap Maven 4.x. This release provides distribution on Apache Maven 3.9.8 (under vote, staged only). The release candidate is here: https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0.0/ Release notes: (visible to committ

Re: [VOTE] Release Maven Release version 3.1.0

+1 pt., 14 cze 2024, 10:43 użytkownik Michael Osipov napisał: > Hi, > > we solved 11 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824&version=12354221 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MRELEASE/issu

Re: [VOTE] Release Apache Maven 3.9.8

+1 pt., 14 cze 2024, 08:33 użytkownik Karl Heinz Marbaise napisał: > Hi, > > +1 from me. > > Kind regards > Karl Heinz Marbaise > On 13.06.24 10:49, Tamás Cservenák wrote: > > Howdy, > > > > We solved 16 issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&vers

Re: [VOTE] Release Apache Maven mvnd 1.0.0

Tested with Trino locally: +1 nb. Thanks! This is gonna to be a great release 🎉 🎉 🎉 On Fri, Jun 14, 2024 at 10:04 AM Tamás Cservenák wrote: > Howdy, > > Note: mvnd 1.x will from now on wrapping Maven 3.9.x and 2.x will wrap > Maven 4.x. > > This release provides distribution on Apache Maven 3.

Re: [VOTE] Release Apache Maven mvnd 1.0.0

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

[DISCUSS] Maven should ALWAYS install/deploy at end

Howdy, As history proved, the original "interleaved" install/deploy is just call for problems, and causes in need for circumventions like https://issues.apache.org/jira/browse/MNG-8054 to make classic "snapshot TS lock-down" possible on large(r) projects. Also, no wonder our users were asking for

Re: [VOTE] Release Maven Release version 3.1.0

Am 2024-06-14 um 10:43 schrieb Michael Osipov: Hi, we solved 11 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824&version=12354221 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MRELEASE/issues Staging repo: https://repo

[RESULT] [VOTE] Release Maven Surefire version 3.3.0

Hi, The vote has passed with the following result: +1: Michael Osipov, Sylwester Lachiewicz, Romain Manni-Bucau, Slawomir Jaranowski, Karl Heinz Marbaise PMC quorum: reached I will promote the artifacts to the central repo, the source release ZIP file and add this release the board report.

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

Hi all, Install by default locally is probably OK for devs, especially for multi-module projects, but deploy by default is a bad IMO: I often work in one repo and install, then switch to another repo and test the new snapshot jars. Round and round until my changes are fully baked. This usually mea

Re: [VOTE] Release Apache Maven mvnd 1.0.0

+1 nb Tested on a couple different projects without issue. On Fri, Jun 14, 2024 at 12:02 PM Romain Manni-Bucau wrote: > +1 > > Romain Manni-Bucau > @rmannibucau | Blog > | Old Blog > | Gith

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

Le 2024-06-14 à 18 h 28, Gary Gregory a écrit : Install by default locally is probably OK for devs, especially for multi-module projects, but deploy by default is a bad IMO. I believe that Tamas's proposal is not to deploy by default, but *if* users asked for deployment, then makes it happen

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

On Fri, Jun 14, 2024 at 1:08 PM Martin Desruisseaux wrote: > > Le 2024-06-14 à 18 h 28, Gary Gregory a écrit : > > > > Install by default locally is probably OK for devs, especially for > > multi-module projects, but deploy by default is a bad IMO. > > > I believe that Tamas's proposal is not to d

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

Le 2024-06-14 à 19 h 11, Gary Gregory a écrit : Thank you Martin for clarifying this! If I understand correctly: If I said 'mvn clean deploy foo bar' in a multi-module project, then 'mvn clean foo bar' happens first for all modules followed by 'mvn deploy' for all modules? This is my unders

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

On Fri, Jun 14, 2024 at 1:18 PM Martin Desruisseaux wrote: > > Le 2024-06-14 à 19 h 11, Gary Gregory a écrit : > > > > Thank you Martin for clarifying this! If I understand correctly: If I > > said 'mvn clean deploy foo bar' in a multi-module project, then 'mvn > > clean foo bar' happens first for

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

Le 2024-06-14 à 19 h 19, Gary Gregory a écrit : Yeah, we need clarification, I can't imagine test/verify would be skipped. I should have said "mvn package for all modules, followed by mvn deploy for all modules". The package phase include tests if I remember right.     Martin

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

+1 (nb) to make installAtEnd and deployAtEnd properties true by default. BTW, there is a note of "experimental" on the install plugin. On Fri, Jun 14, 2024, 19:16 Martin Desruisseaux < martin.desruisse...@geomatys.com> wrote: > Le 2024-06-14 à 19 h 11, Gary Gregory a écrit : > > > > Thank you

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

Howdy Yes, Martin is right: am talking about the two plugin *AtEnd parameters, and only about flipping their defaults. T On Fri, Jun 14, 2024, 18:29 Gary Gregory wrote: > Hi all, > > Install by default locally is probably OK for devs, especially for > multi-module projects, but deploy by defau

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

And Jorge actually wrote down the two parameter names fully :) thanks, i hope it is clear now. T On Fri, Jun 14, 2024, 19:25 Jorge Solórzano wrote: > +1 (nb) to make installAtEnd and deployAtEnd properties true by default. > > BTW, there is a note of "experimental" on the install plugin. > > >

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

Would flipping the defaults make this a backward incompatible change? If users are not aware of this change, it will change their build/deploy in a significant way... Maarten On 14/06/2024 19:49, Tamás Cservenák wrote: Howdy Yes, Martin is right: am talking about the two plugin *AtEnd param

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

Howdy, If for example sake, we define "maven" as mvn CLI and "build end" as "user got on console "BUILD SUCCESS/FAILED" output and CLI process exited, then at that point, this change would cause ZERO difference for SUCCESS builds. Where difference WILL happen, is in case of FAILED builds: nothing

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

Just to clarify, the "snapshot lock down technique" as explained here: https://www.mojohaus.org/versions/versions-maven-plugin/examples/lock-snapshots.html It WORKS even today if dependency in question is one artifact. But, it USUALLY becomes impossible, if you depend on some multi module build.

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

Hi I'm mixed about it since I have a lot of projects using the fact a previous module was installed in default repo. While I can understand the intent I also think both make sense so I don't think why we should break existing projects (when there are two values and both are needed I'd priviledge t

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

Howdy, Everybody has "quirks", and your project "using the fact a previous module was installed" is probably an exception. For example no Maven project expects this (and we have circa 200 of them?). Anyway, -DdeployAtEnd=false is your friend then (maybe best in .mvn/maven.config). Thanks T On Fr

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

Hi, maybe an artifact recorder is in fact the real need here… so if some module is built, the generated artifacts should be accessible to subsequent maven executions…. this way an install would be superfluous and multiple builds could be run after each other without changing the installed heap.

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

Hi Kemal, Interesting idea... Maven4 has something for this ("project repo" that is project-local as opposed to "local repo" that is global). But my discussion is about Maven3 and local repo and remote repo (both are global). Thanks T On Fri, Jun 14, 2024 at 9:29 PM Kemal Soysal < kemal.soy...@

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

Yes, Tamás, I wrote that for maven 3 in 2017. It is quite simple. I used an XML-file to log the artifacts in the build along with all needed identifications. When already built artifacts were needed just loaded them from there - especially the extra attached artifacts were problematic for us. Bac

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

nexus-staging-maven-plugin does something similar (was authored by me while at Sonatype), hence, it could even do "two phase deploy", one phase collect and in next mvn run deploy collected artifacts... And yes, this was in 2010s, when "parallel" was not yet a thing :) T On Fri, Jun 14, 2024 at

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

@Tamas was not project but projects, maybe not 200 but diverse ones compared to maven which are 4-5 types only so don't think it is just a random exception. As discussed since 10+ years now - without consensus I agree, we are no more in a world we just build a simple jar with only classes in there.

Re: Apache Maven mvnd 1.0.0 "early access"

I have tested the latest build and confirmed that it can successfully compile Jenkins core. Very nice! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven mvnd 1.0.0

Tested on a few maven plugins and extension, works flawlessly. Thanks Tamas, this is awesome ! 🚀 On Fri, Jun 14, 2024 at 7:04 PM Brian Demers wrote: > +1 nb > > Tested on a couple different projects without issue. > > On Fri, Jun 14, 2024 at 12:02 PM Romain Manni-Bucau > > wrote: > > > +1 > > >

Re: [VOTE] Release Apache Maven mvnd 1.0.0

+1 Guillaume Nodet Le ven. 14 juin 2024 à 16:04, Tamás Cservenák a écrit : > Howdy, > > Note: mvnd 1.x will from now on wrapping Maven 3.9.x and 2.x will wrap > Maven 4.x. > > This release provides distribution on Apache Maven 3.9.8 (under vote, > staged only). > > Th