You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Jaroslav Tulach <ja...@gmail.com> on 2020/08/25 05:27:02 UTC
Re: Speed of Maven build
> 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 <ja...@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
>
>
>
>
>
>
Re: Speed of Maven build
Posted by Jaroslav Tulach <ja...@gmail.com>.
Dne úterý 25. srpna 2020 13:26:33 CEST, Jeff Jensen napsal(a):
> 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
Thanks Jeff. The idea seems fine. Too bad the project doesn't even build:
https://github.com/jdillon/mvnsh/issues/38
-jt
>
>
> On Tue, Aug 25, 2020 at 12:27 AM Jaroslav Tulach <ja...@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.tulach@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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Speed of Maven build
Posted by Jaroslav Tulach <ja...@gmail.com>.
Dne úterý 25. srpna 2020 13:26:33 CEST, Jeff Jensen napsal(a):
> 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
Thanks Jeff. The idea seems fine. Too bad the project doesn't even build:
https://github.com/jdillon/mvnsh/issues/38
-jt
>
>
> On Tue, Aug 25, 2020 at 12:27 AM Jaroslav Tulach <ja...@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.tulach@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-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Speed of Maven build
Posted by Michael Bien <mb...@gmail.com>.
this would be an interesting use case for a native image, but the
modular nature of maven is at the same time also the worst case scenario
for native images :)
best regards,
-michael
On 06.09.20 06:43, Jaroslav Tulach wrote:
> Thanks Jesse, Tim.
> I've modified https://issues.apache.org/jira/browse/NETBEANS-4746 with links to
> your posts - I assume both are part of the problem: cold JVM for small
> projects, a lot of I/O for large project structures.
>
> -jt
>
> Dne pátek 4. září 2020 5:26:21 CEST, Tim Boudreau napsal(a):
>> For larger multi-module projects, I'd tend to suspect that a substantial
>> chunk of the time is I/O-bound, parsing
>> XML - build one project with a substantial dependency tree. How many POM
>> files both in the project and
>> under ~/.m2 need to parsed? It would be interesting to instrument Maven
>> and get some timings out of that.
>>
>> My fairly sprawling Antlr-IDE-support +
>> build-ide-plugins-with-a-compiled-antlr-grammar-and-some-annotations
>> framework clocks in at 68 pom files (probably 20 of these are projects for
>> tests to run against and test-support
>> libraries). Certainly there are other in-the-ide performance issues
>> (change the version of one thing in the
>> dependency management section of the parent POM and plan not to use the IDE
>> for a few minutes while
>> scanning the universe brings the IDE to its knees).
>>
>> It would be worth doing some measurements of. I'd imagine if that proves
>> to be a root cause, some sort of
>> fast and queriable binary cache not unlike those the IDE uses for layer
>> contents and such in its cache
>> directory could be very helpful. The trick would be identifying those
>> changes to POM files that do *not* require
>> invalidating the cached POM of every project that depends on it.
>>
>> The 1.5 second improvement of a warm VM would be helpful on small projects,
>> but in any large tree of projects
>> where a build can take several minutes, it's not going to be significant.
>>
>> I don't know if small monolithic single-pom projects are the common case,
>> or multi-module projects. If multi-module
>> projects are the more common case, the warm-VM approach may not be worth
>> the engineering effort, given the
>> things that can go wrong and the effort required to defend against them.
>> You could have it internally cache and
>> keep hot information about dependencies to avoid I/O on subsequent builds,
>> but that could start to have a
>> substantial memory footprint.
>>
>> My experience running with, say, -T 8 can have a substantial impact on
>> build times, but it appears not to take
>> into account test dependencies when sorting the projects into a build
>> order, so if you run tests, at some point
>> you wind up running against something that is in the process of being built
>> and it crashes.
>>
>> -Tim
>>
>> On Thu, Sep 3, 2020 at 4:10 PM Jesse Glick <ty...@gmail.com> wrote:
>>> On Thu, Aug 27, 2020 at 1:30 AM Jaroslav Tulach
>>>
>>> <ja...@gmail.com> wrote:
>>>> Hypothesis: Probably different Ant and Maven integration into the
>>> NetBeans IDE.
>>>
>>>> While Ant is executed in the same JVM as the IDE in an isolated
>>> classloader,
>>>
>>>> Maven is probably always started as a separate process.
>>> Yes this likely accounts for a lot of the difference.
>>>
>>> For a regular edit-test-edit-test cycle you can use the misleadingly
>>> named “compile on save” feature to save time, but in the case of Maven
>>> projects it still does launch `mvn`, just with a minimal set of mojos.
>>> At one point Maven CoS used the IDE’s built-in test runner
>>> (incidentally implemented with in-JVM Ant), just passing along the
>>> classpath introspected from the POM, but we switched to launching
>>> actual Maven to get better compatibility with projects with subtler
>>> configuration (IIRC).
>>>
>>> At any rate, I like the idea of reusing a JVM in the style of `mvnsh`
>>> for repeated Maven invocations in routine developer workflows. It
>>> would be important to keep not only Maven core loaded, but mojo class
>>> loaders, since these are often large and expensive to initialize. You
>>> would have to tune it in various ways, for example
>>>
>>> · Shut down automatically after some idle period.
>>> · Avoid sharing an instance between projects.
>>> · Run a regular forked `mvn` for executions that smell production-y,
>>> such as anything using the `clean` or `install` phases.
>>>
>>> It is possible that given a warm JVM, we could dispense with any
>>> special CoS tricks and still get reasonable performance from the stock
>>> lifecycle up to the `test` phase. It depends in part on the project
>>> config: if your POM is requesting a ton of plugins run in earlier
>>> phases (CheckStyle, etc.), there will still be lots of overhead unless
>>> the IDE passes a bunch of `-DskipSomething` properties.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>>> For additional commands, e-mail: dev-help@netbeans.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Speed of Maven build
Posted by Jaroslav Tulach <ja...@gmail.com>.
Thanks Jesse, Tim.
I've modified https://issues.apache.org/jira/browse/NETBEANS-4746 with links to
your posts - I assume both are part of the problem: cold JVM for small
projects, a lot of I/O for large project structures.
-jt
Dne pátek 4. září 2020 5:26:21 CEST, Tim Boudreau napsal(a):
> For larger multi-module projects, I'd tend to suspect that a substantial
> chunk of the time is I/O-bound, parsing
> XML - build one project with a substantial dependency tree. How many POM
> files both in the project and
> under ~/.m2 need to parsed? It would be interesting to instrument Maven
> and get some timings out of that.
>
> My fairly sprawling Antlr-IDE-support +
> build-ide-plugins-with-a-compiled-antlr-grammar-and-some-annotations
> framework clocks in at 68 pom files (probably 20 of these are projects for
> tests to run against and test-support
> libraries). Certainly there are other in-the-ide performance issues
> (change the version of one thing in the
> dependency management section of the parent POM and plan not to use the IDE
> for a few minutes while
> scanning the universe brings the IDE to its knees).
>
> It would be worth doing some measurements of. I'd imagine if that proves
> to be a root cause, some sort of
> fast and queriable binary cache not unlike those the IDE uses for layer
> contents and such in its cache
> directory could be very helpful. The trick would be identifying those
> changes to POM files that do *not* require
> invalidating the cached POM of every project that depends on it.
>
> The 1.5 second improvement of a warm VM would be helpful on small projects,
> but in any large tree of projects
> where a build can take several minutes, it's not going to be significant.
>
> I don't know if small monolithic single-pom projects are the common case,
> or multi-module projects. If multi-module
> projects are the more common case, the warm-VM approach may not be worth
> the engineering effort, given the
> things that can go wrong and the effort required to defend against them.
> You could have it internally cache and
> keep hot information about dependencies to avoid I/O on subsequent builds,
> but that could start to have a
> substantial memory footprint.
>
> My experience running with, say, -T 8 can have a substantial impact on
> build times, but it appears not to take
> into account test dependencies when sorting the projects into a build
> order, so if you run tests, at some point
> you wind up running against something that is in the process of being built
> and it crashes.
>
> -Tim
>
> On Thu, Sep 3, 2020 at 4:10 PM Jesse Glick <ty...@gmail.com> wrote:
> > On Thu, Aug 27, 2020 at 1:30 AM Jaroslav Tulach
> >
> > <ja...@gmail.com> wrote:
> > > Hypothesis: Probably different Ant and Maven integration into the
> >
> > NetBeans IDE.
> >
> > > While Ant is executed in the same JVM as the IDE in an isolated
> >
> > classloader,
> >
> > > Maven is probably always started as a separate process.
> >
> > Yes this likely accounts for a lot of the difference.
> >
> > For a regular edit-test-edit-test cycle you can use the misleadingly
> > named “compile on save” feature to save time, but in the case of Maven
> > projects it still does launch `mvn`, just with a minimal set of mojos.
> > At one point Maven CoS used the IDE’s built-in test runner
> > (incidentally implemented with in-JVM Ant), just passing along the
> > classpath introspected from the POM, but we switched to launching
> > actual Maven to get better compatibility with projects with subtler
> > configuration (IIRC).
> >
> > At any rate, I like the idea of reusing a JVM in the style of `mvnsh`
> > for repeated Maven invocations in routine developer workflows. It
> > would be important to keep not only Maven core loaded, but mojo class
> > loaders, since these are often large and expensive to initialize. You
> > would have to tune it in various ways, for example
> >
> > · Shut down automatically after some idle period.
> > · Avoid sharing an instance between projects.
> > · Run a regular forked `mvn` for executions that smell production-y,
> > such as anything using the `clean` or `install` phases.
> >
> > It is possible that given a warm JVM, we could dispense with any
> > special CoS tricks and still get reasonable performance from the stock
> > lifecycle up to the `test` phase. It depends in part on the project
> > config: if your POM is requesting a ton of plugins run in earlier
> > phases (CheckStyle, etc.), there will still be lots of overhead unless
> > the IDE passes a bunch of `-DskipSomething` properties.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Speed of Maven build
Posted by Tim Boudreau <ni...@gmail.com>.
For larger multi-module projects, I'd tend to suspect that a substantial
chunk of the time is I/O-bound, parsing
XML - build one project with a substantial dependency tree. How many POM
files both in the project and
under ~/.m2 need to parsed? It would be interesting to instrument Maven
and get some timings out of that.
My fairly sprawling Antlr-IDE-support +
build-ide-plugins-with-a-compiled-antlr-grammar-and-some-annotations
framework clocks in at 68 pom files (probably 20 of these are projects for
tests to run against and test-support
libraries). Certainly there are other in-the-ide performance issues
(change the version of one thing in the
dependency management section of the parent POM and plan not to use the IDE
for a few minutes while
scanning the universe brings the IDE to its knees).
It would be worth doing some measurements of. I'd imagine if that proves
to be a root cause, some sort of
fast and queriable binary cache not unlike those the IDE uses for layer
contents and such in its cache
directory could be very helpful. The trick would be identifying those
changes to POM files that do *not* require
invalidating the cached POM of every project that depends on it.
The 1.5 second improvement of a warm VM would be helpful on small projects,
but in any large tree of projects
where a build can take several minutes, it's not going to be significant.
I don't know if small monolithic single-pom projects are the common case,
or multi-module projects. If multi-module
projects are the more common case, the warm-VM approach may not be worth
the engineering effort, given the
things that can go wrong and the effort required to defend against them.
You could have it internally cache and
keep hot information about dependencies to avoid I/O on subsequent builds,
but that could start to have a
substantial memory footprint.
My experience running with, say, -T 8 can have a substantial impact on
build times, but it appears not to take
into account test dependencies when sorting the projects into a build
order, so if you run tests, at some point
you wind up running against something that is in the process of being built
and it crashes.
-Tim
On Thu, Sep 3, 2020 at 4:10 PM Jesse Glick <ty...@gmail.com> wrote:
> On Thu, Aug 27, 2020 at 1:30 AM Jaroslav Tulach
> <ja...@gmail.com> wrote:
> > Hypothesis: Probably different Ant and Maven integration into the
> NetBeans IDE.
> > While Ant is executed in the same JVM as the IDE in an isolated
> classloader,
> > Maven is probably always started as a separate process.
>
> Yes this likely accounts for a lot of the difference.
>
> For a regular edit-test-edit-test cycle you can use the misleadingly
> named “compile on save” feature to save time, but in the case of Maven
> projects it still does launch `mvn`, just with a minimal set of mojos.
> At one point Maven CoS used the IDE’s built-in test runner
> (incidentally implemented with in-JVM Ant), just passing along the
> classpath introspected from the POM, but we switched to launching
> actual Maven to get better compatibility with projects with subtler
> configuration (IIRC).
>
> At any rate, I like the idea of reusing a JVM in the style of `mvnsh`
> for repeated Maven invocations in routine developer workflows. It
> would be important to keep not only Maven core loaded, but mojo class
> loaders, since these are often large and expensive to initialize. You
> would have to tune it in various ways, for example
>
> · Shut down automatically after some idle period.
> · Avoid sharing an instance between projects.
> · Run a regular forked `mvn` for executions that smell production-y,
> such as anything using the `clean` or `install` phases.
>
> It is possible that given a warm JVM, we could dispense with any
> special CoS tricks and still get reasonable performance from the stock
> lifecycle up to the `test` phase. It depends in part on the project
> config: if your POM is requesting a ton of plugins run in earlier
> phases (CheckStyle, etc.), there will still be lots of overhead unless
> the IDE passes a bunch of `-DskipSomething` properties.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
--
http://timboudreau.com
Re: Speed of Maven build
Posted by Jesse Glick <ty...@gmail.com>.
On Thu, Aug 27, 2020 at 1:30 AM Jaroslav Tulach
<ja...@gmail.com> wrote:
> Hypothesis: Probably different Ant and Maven integration into the NetBeans IDE.
> While Ant is executed in the same JVM as the IDE in an isolated classloader,
> Maven is probably always started as a separate process.
Yes this likely accounts for a lot of the difference.
For a regular edit-test-edit-test cycle you can use the misleadingly
named “compile on save” feature to save time, but in the case of Maven
projects it still does launch `mvn`, just with a minimal set of mojos.
At one point Maven CoS used the IDE’s built-in test runner
(incidentally implemented with in-JVM Ant), just passing along the
classpath introspected from the POM, but we switched to launching
actual Maven to get better compatibility with projects with subtler
configuration (IIRC).
At any rate, I like the idea of reusing a JVM in the style of `mvnsh`
for repeated Maven invocations in routine developer workflows. It
would be important to keep not only Maven core loaded, but mojo class
loaders, since these are often large and expensive to initialize. You
would have to tune it in various ways, for example
· Shut down automatically after some idle period.
· Avoid sharing an instance between projects.
· Run a regular forked `mvn` for executions that smell production-y,
such as anything using the `clean` or `install` phases.
It is possible that given a warm JVM, we could dispense with any
special CoS tricks and still get reasonable performance from the stock
lifecycle up to the `test` phase. It depends in part on the project
config: if your POM is requesting a ton of plugins run in earlier
phases (CheckStyle, etc.), there will still be lots of overhead unless
the IDE passes a bunch of `-DskipSomething` properties.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Speed of Maven build
Posted by Martin Kanters <ma...@apache.org>.
Hi Jaroslav, nice analysis. In the maven-integration-testing repository [1]
Maven can be started fully independently or embedded in the same JDK. The
latter is activated with the Maven profile "embedded".
This also gives a huge performance boost, running tests in tenths of a
second instead of seconds.
Martin
[1] https://github.com/apache/maven-integration-testing/
Op do 27 aug. 2020 om 07:30 schreef Jaroslav Tulach <
jaroslav.tulach@gmail.com>:
> Dne středa 26. srpna 2020 10:01:33 CEST, Davide Grandi napsal(a):
> > Sorry to be late, but
> > there is a project test case for Maven "slowlyness" ?
>
> This is a great question, thanks Davide!
>
> I've just tried to create such project:
> https://issues.apache.org/jira/browse/NETBEANS-4746
> and yes, Maven is slower (see the instructions in the issue):
>
> ```bash
> justtest$ mvn -quiet -Dtest=MainTest process-test-classes surefire:test
> justtest$ ant -q test-single
> ```
>
> However only 2.6s vs. 1.9s and that cannot be the problem NetBeans users
> complain about.
>
> I guess the real problem is when people open the projects in the NetBeans
> IDE.
>
> Try to remove `pom.xml` and open the folder in NetBeans IDE 12.x - it
> opens as
> an Ant project. Select `MainTest.java` class and press Ctrl+F6 - repeat -
> at
> the end it takes less then 1s!
>
> Repeat again from scratch, but remove `build.xml` file and `nbproject`
> directory. Then the project opens as Maven. Select `MainTest.java` class
> and
> press Ctrl+F6 - takes more than 2s - repeat - takes more than 2s again.
>
> What cases the difference?
>
> Hypothesis: Probably different Ant and Maven integration into the NetBeans
> IDE.
> While Ant is executed in the same JVM as the IDE in an isolated
> classloader,
> Maven is probably always started as a separate process. Given a regular
> JDK
> doesn't do anything useful for first 1-1.5s of execution we might have
> found
> the difference. Ant code is reused again and again and warms up over time.
> Maven always starts from scratch and JDK's warming delay causes the wrong
> impression.
>
> Consider verifying my claims and observations.
> -jt
>
>
> >
> > I mean : a project for which there's a time gap between
> >
> > - nb/command line mvn invocations
> > - or between ant / mavn builds (I know : how many projects have TWO
> > build files ? ...)
> >
> > for routinely rebuilds of big projects I often activate the "quiet" and
> > "parallel" build params
> > and keep an eye at mvn java memory params.
> > Usual network and I/O tricks may apply.
> >
> > bye,
> >
> > Davide
> >
> > On 25/08/2020 07:27, Jaroslav Tulach 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
> > > <ja...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Speed of Maven build
Posted by Davide Grandi <da...@email.it>.
I think that your conclusions are reasonable.
I've built your test project, that confirms the startup delay hypothesis.
However performances must be evaluated on specific test cases :
building a 10 *.java program is different from building CXF (maven) or
derby (ant).
Maybe that also the goals are different :
Maven stress repeatability of builds, even offering that some plugin
run in separate java process.
In some cases I run mvn asking for a new local repository, re-downloading
all plugins and dependencies.
So ... if the final goal is to keep nb "build system agnostic" I
think that the focus is in the interfaces towards the build systems
(running mvn "in process" like ant could be an idea - for small projects)
avoiding buffer locking and display delay.
assessing expected result for different project sizes (small 10 files -
medium 100
- big CXF) will give useful hints.
Thank-you & best regards,
Davide
On 27/08/2020 07:30, Jaroslav Tulach wrote:
> Dne středa 26. srpna 2020 10:01:33 CEST, Davide Grandi napsal(a):
>> Sorry to be late, but
>> there is a project test case for Maven "slowlyness" ?
> This is a great question, thanks Davide!
>
> I've just tried to create such project:
> https://issues.apache.org/jira/browse/NETBEANS-4746
> and yes, Maven is slower (see the instructions in the issue):
>
> ```bash
> justtest$ mvn -quiet -Dtest=MainTest process-test-classes surefire:test
> justtest$ ant -q test-single
> ```
>
> However only 2.6s vs. 1.9s and that cannot be the problem NetBeans users
> complain about.
>
> I guess the real problem is when people open the projects in the NetBeans IDE.
>
> Try to remove `pom.xml` and open the folder in NetBeans IDE 12.x - it opens as
> an Ant project. Select `MainTest.java` class and press Ctrl+F6 - repeat - at
> the end it takes less then 1s!
>
> Repeat again from scratch, but remove `build.xml` file and `nbproject`
> directory. Then the project opens as Maven. Select `MainTest.java` class and
> press Ctrl+F6 - takes more than 2s - repeat - takes more than 2s again.
>
> What cases the difference?
>
> Hypothesis: Probably different Ant and Maven integration into the NetBeans IDE.
> While Ant is executed in the same JVM as the IDE in an isolated classloader,
> Maven is probably always started as a separate process. Given a regular JDK
> doesn't do anything useful for first 1-1.5s of execution we might have found
> the difference. Ant code is reused again and again and warms up over time.
> Maven always starts from scratch and JDK's warming delay causes the wrong
> impression.
>
> Consider verifying my claims and observations.
> -jt
>
>> I mean : a project for which there's a time gap between
>>
>> - nb/command line mvn invocations
>> - or between ant / mavn builds (I know : how many projects have TWO
>> build files ? ...)
>>
>> for routinely rebuilds of big projects I often activate the "quiet" and
>> "parallel" build params
>> and keep an eye at mvn java memory params.
>> Usual network and I/O tricks may apply.
>>
>> bye,
>>
>> Davide
>>
>> On 25/08/2020 07:27, Jaroslav Tulach 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
>>> <ja...@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
--
Ing. Davide Grandi
email : davide.grandi@email.it
mobile : +39 339 7468 778
linkedin : http://linkedin.com/in/davidegrandi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Speed of Maven build
Posted by Jaroslav Tulach <ja...@gmail.com>.
Dne středa 26. srpna 2020 10:01:33 CEST, Davide Grandi napsal(a):
> Sorry to be late, but
> there is a project test case for Maven "slowlyness" ?
This is a great question, thanks Davide!
I've just tried to create such project:
https://issues.apache.org/jira/browse/NETBEANS-4746
and yes, Maven is slower (see the instructions in the issue):
```bash
justtest$ mvn -quiet -Dtest=MainTest process-test-classes surefire:test
justtest$ ant -q test-single
```
However only 2.6s vs. 1.9s and that cannot be the problem NetBeans users
complain about.
I guess the real problem is when people open the projects in the NetBeans IDE.
Try to remove `pom.xml` and open the folder in NetBeans IDE 12.x - it opens as
an Ant project. Select `MainTest.java` class and press Ctrl+F6 - repeat - at
the end it takes less then 1s!
Repeat again from scratch, but remove `build.xml` file and `nbproject`
directory. Then the project opens as Maven. Select `MainTest.java` class and
press Ctrl+F6 - takes more than 2s - repeat - takes more than 2s again.
What cases the difference?
Hypothesis: Probably different Ant and Maven integration into the NetBeans IDE.
While Ant is executed in the same JVM as the IDE in an isolated classloader,
Maven is probably always started as a separate process. Given a regular JDK
doesn't do anything useful for first 1-1.5s of execution we might have found
the difference. Ant code is reused again and again and warms up over time.
Maven always starts from scratch and JDK's warming delay causes the wrong
impression.
Consider verifying my claims and observations.
-jt
>
> I mean : a project for which there's a time gap between
>
> - nb/command line mvn invocations
> - or between ant / mavn builds (I know : how many projects have TWO
> build files ? ...)
>
> for routinely rebuilds of big projects I often activate the "quiet" and
> "parallel" build params
> and keep an eye at mvn java memory params.
> Usual network and I/O tricks may apply.
>
> bye,
>
> Davide
>
> On 25/08/2020 07:27, Jaroslav Tulach 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
> > <ja...@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-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Speed of Maven build
Posted by Jaroslav Tulach <ja...@gmail.com>.
Dne středa 26. srpna 2020 10:01:33 CEST, Davide Grandi napsal(a):
> Sorry to be late, but
> there is a project test case for Maven "slowlyness" ?
This is a great question, thanks Davide!
I've just tried to create such project:
https://issues.apache.org/jira/browse/NETBEANS-4746
and yes, Maven is slower (see the instructions in the issue):
```bash
justtest$ mvn -quiet -Dtest=MainTest process-test-classes surefire:test
justtest$ ant -q test-single
```
However only 2.6s vs. 1.9s and that cannot be the problem NetBeans users
complain about.
I guess the real problem is when people open the projects in the NetBeans IDE.
Try to remove `pom.xml` and open the folder in NetBeans IDE 12.x - it opens as
an Ant project. Select `MainTest.java` class and press Ctrl+F6 - repeat - at
the end it takes less then 1s!
Repeat again from scratch, but remove `build.xml` file and `nbproject`
directory. Then the project opens as Maven. Select `MainTest.java` class and
press Ctrl+F6 - takes more than 2s - repeat - takes more than 2s again.
What cases the difference?
Hypothesis: Probably different Ant and Maven integration into the NetBeans IDE.
While Ant is executed in the same JVM as the IDE in an isolated classloader,
Maven is probably always started as a separate process. Given a regular JDK
doesn't do anything useful for first 1-1.5s of execution we might have found
the difference. Ant code is reused again and again and warms up over time.
Maven always starts from scratch and JDK's warming delay causes the wrong
impression.
Consider verifying my claims and observations.
-jt
>
> I mean : a project for which there's a time gap between
>
> - nb/command line mvn invocations
> - or between ant / mavn builds (I know : how many projects have TWO
> build files ? ...)
>
> for routinely rebuilds of big projects I often activate the "quiet" and
> "parallel" build params
> and keep an eye at mvn java memory params.
> Usual network and I/O tricks may apply.
>
> bye,
>
> Davide
>
> On 25/08/2020 07:27, Jaroslav Tulach 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
> > <ja...@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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Speed of Maven build
Posted by Davide Grandi <da...@email.it>.
Sorry to be late, but
there is a project test case for Maven "slowlyness" ?
I mean : a project for which there's a time gap between
- nb/command line mvn invocations
- or between ant / mavn builds (I know : how many projects have TWO
build files ? ...)
for routinely rebuilds of big projects I often activate the "quiet" and
"parallel" build params
and keep an eye at mvn java memory params.
Usual network and I/O tricks may apply.
bye,
Davide
On 25/08/2020 07:27, Jaroslav Tulach 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 <ja...@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
--
Ing. Davide Grandi
email : davide.grandi@email.it
linkedin : http://linkedin.com/in/davidegrandi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Speed of Maven build
Posted by Falko Modler <f....@gmx.net>.
Maybe slightly offtopic but if you have (many) submodules, you might
want to consider automatic incremental builds (based on SCM changes)
with https://github.com/vackosar/gitflow-incremental-builder
Don't be scared by the name. You do not actually need a gitflow branch
layout.
Disclaimer: I am maintaining gitflow-incremental-builder.
Cheers,
Falko
PS: IIRC, a few months ago someone on this mailing list came up with an
idea to "cache" build results with Maven. Not sure what happened to that
idea.
Am 25.08.2020 um 23:07 schrieb Manfred Moser:
> Also the M2Eclipse integration does basically embed maven and make the Maven build incremental.
>
> The Takari plugin does that on the commandline with the eclipse compiler
>
> And the VS code integration from Red Hat might also do something along those lines.
>
> Others can chime in with more details.
>
> Manfred
>
> John Patrick wrote on 2020-08-25 13:29 (GMT -07:00):
>
>> 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
>> <je...@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 <ja...@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.tulach@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Speed of Maven build
Posted by Manfred Moser <ma...@simpligility.com>.
Mickael Istria wrote on 2020-08-25 14:17 (GMT -07:00):
> I
>
> On Tuesday, August 25, 2020, Manfred Moser <ma...@simpligility.com> wrote:
>> And the VS code integration from Red Hat might also do something along
> those lines.
>
> It embeds and uses m2eclipse.
>
Haha.. thanks for confirming. I thought that to be the case but did not want to say it explicitly since I was only 80 or so percent sure..
manfred
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Speed of Maven build
Posted by Manfred Moser <ma...@simpligility.com>.
Mickael Istria wrote on 2020-08-25 14:17 (GMT -07:00):
> I
>
> On Tuesday, August 25, 2020, Manfred Moser <ma...@simpligility.com> wrote:
>> And the VS code integration from Red Hat might also do something along
> those lines.
>
> It embeds and uses m2eclipse.
>
Haha.. thanks for confirming. I thought that to be the case but did not want to say it explicitly since I was only 80 or so percent sure..
manfred
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Speed of Maven build
Posted by Mickael Istria <mi...@redhat.com>.
I
On Tuesday, August 25, 2020, Manfred Moser <ma...@simpligility.com> wrote:
> And the VS code integration from Red Hat might also do something along
those lines.
It embeds and uses m2eclipse.
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
Re: Speed of Maven build
Posted by Mickael Istria <mi...@redhat.com>.
I
On Tuesday, August 25, 2020, Manfred Moser <ma...@simpligility.com> wrote:
> And the VS code integration from Red Hat might also do something along
those lines.
It embeds and uses m2eclipse.
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
Re: Speed of Maven build
Posted by Manfred Moser <ma...@simpligility.com>.
Also the M2Eclipse integration does basically embed maven and make the Maven build incremental.
The Takari plugin does that on the commandline with the eclipse compiler
And the VS code integration from Red Hat might also do something along those lines.
Others can chime in with more details.
Manfred
John Patrick wrote on 2020-08-25 13:29 (GMT -07:00):
> 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
> <je...@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 <ja...@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.tulach@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Speed of Maven build
Posted by Manfred Moser <ma...@simpligility.com>.
Also the M2Eclipse integration does basically embed maven and make the Maven build incremental.
The Takari plugin does that on the commandline with the eclipse compiler
And the VS code integration from Red Hat might also do something along those lines.
Others can chime in with more details.
Manfred
John Patrick wrote on 2020-08-25 13:29 (GMT -07:00):
> 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
> <je...@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 <ja...@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.tulach@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Speed of Maven build
Posted by John Patrick <nh...@gmail.com>.
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
<je...@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 <ja...@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.tulach@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-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Speed of Maven build
Posted by Will Hartung <wi...@gmail.com>.
On Tue, Aug 25, 2020 at 4:37 AM Jeff Jensen <
jeffjensen@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
>
> Is this really where the runtime for Maven goes? I always felt it was
loading the POMs, walking the dependencies, plus all the network hits
(which can be mitigated with the -o flag).
Re: Speed of Maven build
Posted by Will Hartung <wi...@gmail.com>.
On Tue, Aug 25, 2020 at 4:37 AM Jeff Jensen <
jeffjensen@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
>
> Is this really where the runtime for Maven goes? I always felt it was
loading the POMs, walking the dependencies, plus all the network hits
(which can be mitigated with the -o flag).
Re: Speed of Maven build
Posted by John Patrick <nh...@gmail.com>.
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
<je...@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 <ja...@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.tulach@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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Speed of Maven build
Posted by Jeff Jensen <je...@upstairstechnology.com>.
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 <ja...@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.tulach@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
> >
> >
> >
> >
> >
> >
>
Re: Speed of Maven build
Posted by Jeff Jensen <je...@upstairstechnology.com>.
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 <ja...@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.tulach@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
> >
> >
> >
> >
> >
> >
>