Re: Why no mvn daemon?

2021-03-31 Thread Benjamin Marwell
Add my +1 to Romain's. As said, it is drop-in replacement most of the times, has a nice TUI, sane defaults and speeds up your build. If you haven't tried it yet, definitely do. As for the resident memory: no software is ever finished, there will always be something which can be done better.

Re: [VOTE] Release Apache Maven version 3.8.1

2021-03-31 Thread Elliotte Rusty Harold
On Wed, Mar 31, 2021 at 8:11 AM wrote: > > I had the same observation. I *think* it is caused by the fact that you > manually downloaded the ZIP archive - browsers on macOS set the > 'quarantine' flag on downloaded files. It also happens if I download > 3.6.3 manually (i.e., using Firefox). >

Re: [VOTE] Release Apache Maven version 3.8.1

2021-03-31 Thread Arnaud Héritier
ok, I think it makes sense then. +1 for me, all my tests are ok On Wed, Mar 31, 2021 at 10:11 AM wrote: > I had the same observation. I *think* it is caused by the fact that you > manually downloaded the ZIP archive - browsers on macOS set the > 'quarantine' flag on downloaded files. It also

Re: [VOTE] Release Apache Maven version 3.8.1

2021-03-31 Thread mthmulders
I had the same observation. I *think* it is caused by the fact that you manually downloaded the ZIP archive - browsers on macOS set the 'quarantine' flag on downloaded files. It also happens if I download 3.6.3 manually (i.e., using Firefox). I think the Homebrew package manager for macOS

Re: [VOTE] Release Apache Maven version 3.8.1

2021-03-31 Thread Romain Manni-Bucau
Except http://rubygems-proxy.torquebox.org/releases/ breaking (and HTTPS setup is not better) it works as expected +1 Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Re: [VOTE] Release Apache Maven version 3.8.1

2021-03-31 Thread Arnaud Héritier
I have a problem on macos that I didn't have with 3.6.3, when I launch maven it I have this error: “libjansi.jnilib” cannot be opened because the developer cannot be verified. macOS cannot verify that this app is free from malware. Brave downloaded this file today at 09:25. It's a popup window:

Re: [VOTE] Release Apache Maven version 3.8.1

2021-03-31 Thread Enrico Olivelli
+1 (non binding) I have tested the staged binaries againsts a few projects I have observed these logs, IIUC this is expected. [INFO] Reading assembly descriptor: assembly.xml Downloading from maven-default-http-blocker: http://0.0.0.0/joda-time/joda-time/maven-metadata.xml [WARNING] Could not

Re: Why no mvn daemon?

2021-03-31 Thread Romain Manni-Bucau
Le mer. 31 mars 2021 à 08:17, Hervé BOUTEMY a écrit : > I think mvnd is not so well known [1]: I did never test it, I should > probably > do... > > and as incremental compilation discussion have started recently, we'll > need to > have a global discussion on evaluating and eventually mixing

Re: [VOTE] Release Apache Maven version 3.8.1

2021-03-31 Thread Maarten Mulders
Retried the test that I did on 3.8.0, this time I observe the desired / correct behaviour. +1 Maarten On March 31, 2021, at 01:46, Mark Derricutt wrote: +1 non-binding - bistro zips are in the /dev/ tree - my multi-repo osgi maven tiles weirdo build works fine. From: Robert

[GitHub] [maven-site] hboutemy commented on pull request #231: Maven 3.3.4

2021-03-31 Thread GitBox
hboutemy commented on pull request #231: URL: https://github.com/apache/maven-site/pull/231#issuecomment-810805280 I suppose this PR was opened by mistake? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

Re: [DISCUSS] Next release version: 3.6.4, 3.7.0, 3.8.0 or other

2021-03-31 Thread Hervé BOUTEMY
I don't get the reasoning: what content do you expect in such a Maven 3.6.4 release compared to 3.8.1? for what benefit? Le mardi 30 mars 2021, 20:16:23 CEST Romain Manni-Bucau a écrit : > Le mar. 30 mars 2021 à 19:36, Robert Scholte a > > écrit : > > I'm preparing the 3.8.1 release > > So far

Re: Why no mvn daemon?

2021-03-31 Thread Hervé BOUTEMY
I think mvnd is not so well known [1]: I did never test it, I should probably do... and as incremental compilation discussion have started recently, we'll need to have a global discussion on evaluating and eventually mixing differents ways of improving build performance when evaluating, I