that's the maven/plexus/guice boostrap IMHO.
Milos
On Sat, Sep 14, 2013 at 9:06 PM, Mirko Friedenhagen wrote:
> Mark,
>
> I like the decision to use Maven whenever possible as well, nonetheless I
> could imagine being even more happy should the execution times decrease. I
> use a very small mav
Mark,
I like the decision to use Maven whenever possible as well, nonetheless I
could imagine being even more happy should the execution times decrease. I
use a very small maven projects for tests[0] with Maven 3.1.1, turned on
timestamps and it takes Maven about 2 seconds when running "mvn -o
sur
On Fri, Sep 13, 2013 at 9:47 PM, Mark Eggers wrote:
> On 9/13/2013 12:38 PM, Milos Kleint wrote:
>
>> with Compile on Save enabled, the test-compile phase should be skipped and
>> only surefire:test should be executed.
>>
>> However even with that, there's overhead of jvm startup + maven startup
On 9/13/2013 12:38 PM, Milos Kleint wrote:
with Compile on Save enabled, the test-compile phase should be skipped and
only surefire:test should be executed.
However even with that, there's overhead of jvm startup + maven startup
before the mojo gets executed. Obviously the overhead is biggest wh
with Compile on Save enabled, the test-compile phase should be skipped and
only surefire:test should be executed.
However even with that, there's overhead of jvm startup + maven startup
before the mojo gets executed. Obviously the overhead is biggest when you
run just a single test. Unfortunately
Hello everybody,
I use Netbeans 7.4 as IDE and mostly like how it uses Maven to get stuff
done. While it is nice that I do not encounter problems as I did with
Eclipse when dealing with dependency scoping I am slowed down when running
single test files or methods. Netbeans invokes "test-compile su
