Re: Why no mvn daemon?

Hi Yes doesn't look to be an issue. We can definitely simply create the git repo and push the current one. The project is already under ASF license and 2 main contributors are ASF committers. Not sure we need to search for a needle in the haystack with this simple case? Thoughts? an ip clearance

Re: Why no mvn daemon?

Yes, we're still willing to donate it to maven. The IP has already been looked upon some time ago. The two main committers are Peter Palage and me and we already are ASF committers. The other contributors' contributions do not exceed more than a few lines so I don't think this should be an issue,

Re: Why no mvn daemon?

Hi What is the status regarding this? @Guillaume Still keen to donate it? Should be very easy as It looks the license is already ASF and most of the contributors are already Apache folks. let me know. cheers Olivier On Thu, 8 Apr 2021 at 10:08, Olivier Lamy wrote: > Sounds great Guillaume! >

Re: Why no mvn daemon?

Sounds great Guillaume! Not sure to have it part of default distribution but looks to be a great addition here. Not sure about ip clearance etc... something to manage of course... Not tested but should make our plugins build faster? I mean all build using invoker plugin and keep restarting jvm

Re: Why no mvn daemon?

Le mer. 7 avr. 2021 à 19:32, Tibor Digana a écrit : > What was the third run? It was one thread with GraalVM? > 2nd run with mvnd (i skipped the first one since normally you start it once for you work day) mvnd client is a graalvm binary but that is a detail since it runs in a jvm an actual

Re: Why no mvn daemon?

What was the third run? It was one thread with GraalVM? $ time mvnd install -DskipTests -Dinvoker.skip=true real 0m11,295s user 0m0,354s sys 0m0,176s On Wed, Apr 7, 2021 at 7:09 PM Romain Manni-Bucau wrote: > Le mer. 7 avr. 2021 à 17:08, Tibor Digana a > écrit : > > > Romain, our builds are

Re: Why no mvn daemon?

Le mer. 7 avr. 2021 à 17:08, Tibor Digana a écrit : > Romain, our builds are always downloading the artifacts. > The I/O cannot be 0 time. We invest in safety builds rather than > performance and so we rather download fresh artifacts. > Other teams may cach the artifacts which may not be always

Re: Why no mvn daemon?

Romain, our builds are always downloading the artifacts. The I/O cannot be 0 time. We invest in safety builds rather than performance and so we rather download fresh artifacts. Other teams may cach the artifacts which may not be always so safe - other preferences. If you think that the Cache or

Re: Why no mvn daemon?

Hi Tibor, I see what you mean but I think this topic is actually unrelated to IO since this remote latency is actually 0 in the case we are discussing and this case is generally solved by caching on all CI (jenkins, gh actions, travis for the ones I can speak about out of my head) - and locally

Re: Why no mvn daemon?

I think two years ago we were talking about Maven dockerization. We had the work in progress and I think I will be able to find it again. The Docker image included local repo. I think the biggest latencies are when you are downloading artifacts. Of course, you have one local repo, but that's

Re: Why no mvn daemon?

Fwiw, Peter and I would be happy to donate mvnd to the Apache Maven project, should you choose to accept it. Cheers, Guillaume Le lun. 29 mars 2021 à 12:21, Romain Manni-Bucau a écrit : > Up 4 years later ;) > > Now mvnd exists and proves it is very interesting to have such a feature, > should

Re: Why no mvn daemon?

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: Why no mvn daemon?

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: Why no mvn daemon?

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

Re: Why no mvn daemon?

equired to do it, run it on CI >> (in time) and maintain it - will not help much for the same daemon goal >> reason >> >> So is it worth doing a daemon -> clearly, this is what mvnd proves >> (leveraging a mvnd client in native mode when possible btw). >> &g

Re: Why no mvn daemon?

Le mar. 30 mars 2021 à 22:16, Jochen Wiedmann a écrit : > On Tue, Mar 30, 2021 at 7:58 PM Benjamin Marwell > wrote: > > > Other than that, I use mvnd at work and we never had problems on any > > project. We consistently save time without the need of adding the -T > > parameter manually. Another

Re: Why no mvn daemon?

On Tue, Mar 30, 2021 at 7:58 PM Benjamin Marwell wrote: > Other than that, I use mvnd at work and we never had problems on any > project. We consistently save time without the need of adding the -T > parameter manually. Another big question is probably: is there enough > community demand to

Re: Why no mvn daemon?

maintain it - will not help much for the same daemon goal > > reason > > > > So is it worth doing a daemon -> clearly, this is what mvnd proves > > (leveraging a mvnd client in native mode when possible btw). > > > > > > > > > > -Markus > > > > > > > &g

Re: Why no mvn daemon?

ng a daemon -> clearly, this is what mvnd proves > (leveraging a mvnd client in native mode when possible btw). > > > > > > -Markus > > > > > > -Ursprüngliche Nachricht- > > Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] > >

Re: Why no mvn daemon?

-Ursprüngliche Nachricht- > Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] > Gesendet: Montag, 29. März 2021 12:21 > An: Maven Developers List > Cc: Jason Dillon > Betreff: Re: Why no mvn daemon? > > Up 4 years later ;) > > Now mvnd exists and proves it is

AW: Why no mvn daemon?

: Why no mvn daemon? Up 4 years later ;) Now mvnd exists and proves it is very interesting to have such a feature, should it be something which can fit maven standard delivery? If overall yes we can start by asking mvnd if it can be contributed with main codebase and if not we can either decide

Re: Why no mvn daemon?

Up 4 years later ;) Now mvnd exists and proves it is very interesting to have such a feature, should it be something which can fit maven standard delivery? If overall yes we can start by asking mvnd if it can be contributed with main codebase and if not we can either decide to do our own (hope

Re: Why no mvn daemon?

Thanks! It's running just fine. :-) It's very cool. Really nice directory traversal and completion, colors, and commands/features I don't know yet! Very interesting timing diffs (for each casual test, I ran the command for each multiple times to seed infra caches): * on some asciidoc gen

Re: Why no mvn daemon?

On Wed, Mar 9, 2016 at 3:59 PM, Jason Dillon wrote: > On March 8, 2016 at 7:45:53 AM, Jeff Jensen ( > jeffjen...@upstairstechnology.com) wrote: > > FYI Just cloned and tried build but Jansi 1.2 is not in Central: "Could not > > find artifact

Re: Why no mvn daemon?

Jason, if you have a built version, do you mind adding it as a download to  the release files?  I can make a binary of this, though I do plan on fixing it up so that folks can build it in the near future. Build up here for the moment:

Re: Why no mvn daemon?

On March 8, 2016 at 7:45:53 AM, Jeff Jensen (jeffjen...@upstairstechnology.com) wrote: FYI Just cloned and tried build but Jansi 1.2 is not in Central: "Could not  find artifact org.fusesource.jansi:jansi:jar:1.2". 

Re: Why no mvn daemon?

FYI Just cloned and tried build but Jansi 1.2 is not in Central: "Could not find artifact org.fusesource.jansi:jansi:jar:1.2". http://search.maven.org/#search|gav|1|g%3A%22org.fusesource.jansi%22%20AND%20a%3A%22jansi%22 I noted the issue tracker no longer exists so replying here to start. jansi

Re: Why no mvn daemon?

Some months ago I was looking for something like this. Due to this thread, I will soon set it up and try it. (Thanks for sharing Tamás!) On Sat, Mar 5, 2016 at 10:31 PM, Jason Dillon wrote: > On March 3, 2016 at 5:42:56 AM, Tamás Cservenák (ta...@cservenak.net) >

Re: Why no mvn daemon?

On March 3, 2016 at 5:42:56 AM, Tamás Cservenák (ta...@cservenak.net) wrote: Maven Shell?  https://github.com/jdillon/mvnsh  Does anyone actually use this? —jason

Re: Why no mvn daemon?

Good catch but something not changing user shell would be great and part of maven distribution would be awesome. Romain Manni-Bucau @rmannibucau | Blog | Github | LinkedIn

Re: Why no mvn daemon?

Maven Shell? https://github.com/jdillon/mvnsh On Thu, Mar 3, 2016 at 2:13 PM Romain Manni-Bucau wrote: > Hi guys, > > Wonder why maven doesnt have any daemon and din't find anything satisfying > to answer this question with our preferred search engine. > > Idea would be

Why no mvn daemon?

Hi guys, Wonder why maven doesnt have any daemon and din't find anything satisfying to answer this question with our preferred search engine. Idea would be - a bit like gradle I guess - to cache computations and classloaders. Asking cause: - computing the reactor could be long on big projects