Are you planning to create a baseline project or selecting a range of projects to be used as a baseline, so that perceived improvements can be monitored? So that anyone wanting to help out or give feedback can submit their own build performance.
i.e. 1. Equipment OS, Ram, CPU, physical, virtual, docker, openshift, other 2. Java version 3. Maven version 4. Speedtest results 5. Direct Internet Connection or via Http Proxy or via Nexus/Artifactory 6. Clean/Fresh Local Repo Execution Time 7. 2nd Execution Time, after everything downloaded As using Maven since 2005, I've found each new release has gotten faster and faster, and most performance issues have been around what OS I'm using, SSD vs HDD and also do you have enough free RAM etc. As I'm surprised how quickly my builds are running at the moment, the only issue is when I see maven perform internet connections downloading new dependencies or say the versions plugin to check. Any thoughts about adding a HTTP/2 Server Push support so if it's Maven Aware and you request the pom it can also push back the hashes and maybe the jar too. Regarding a "zombie" maven instance, it should be opt in so i need to explicitly enable it as often i'm jumping around between lots of projects so don't want each having a "zombie" progress and i might not be building that project again for another week maybe. John On Tue, 25 Aug 2020 at 12:27, Jeff Jensen <jeffjen...@upstairstechnology.com> wrote: > > In case this helps, Jason Dillon has a "Maven Shell" that does what you > seek for CLI - launches a Maven instance and runs interactive commands with > it, saving the startup time. > https://github.com/jdillon/mvnsh > > > On Tue, Aug 25, 2020 at 12:27 AM Jaroslav Tulach <jaroslav.tul...@gmail.com> > wrote: > > > > And it's Apache Maven, over the corner at https://maven.apache.org/ so > > > I suppose that community would be happy to get such contributions. > > > > > > -Bertrand > > > > You are right, Bertrand. Why not ask! > > > > Hello Maven guys, > > we had a discussion on the NetBeans mailing list recently and here is a > > summary: > > * Apache NetBeans IDE is delegating most of its work directly to Maven > > * Users however complain that the speed isn't great > > * One of the ideas was to launch a "zombie" instance of Maven in advance > > * then actions like build, exec or test would be faster > > > > Have you thought about something like this already? Any advices? > > > > Best regards. > > Jaroslav Tulach > > NetBeans Platform Architect > > > > ne 23. 8. 2020 v 9:06 odesílatel Jaroslav Tulach < > > jaroslav.tul...@gmail.com> > > napsal: > > > > > > I agree with others, Ant is much faster day to day. But the pom.xml has > > > > become the universal project file for Java, > > > > > > Thank you all for sharing your thoughts. I know Maven start is slower, > > but > > > I > > > learned to live with it. It is interesting to hear that some of you > > > maintain a > > > dual Ant based copy of your project metadata. Once we were trying a > > > different > > > approach: > > > > > > There is a way to speed Maven in the IDE. Launch Maven, let it read all > > > XML & > > > co. files and stop it. As soon as we need to build/run/test, wake up this > > > zombie Maven process, tell it what to do and let it continue. If the XML > > > files > > > are modified, throw the process away and initialize it again. Tomáš > > Stupka > > > implemented a prototype of this and there were no issues, as far as I > > know > > > (nobody tested it thoroughly however). > > > > > > Maybe the support is even in and there is a property to turn it on. If > > the > > > Maven startup is the biggest problem for you guys, we shall investigate > > > how to > > > turn Tomáš's work on... > > > > > > -jt > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
