Hi Igor,
This would be cool imagination to fix it by myself, but last days I have
slept only few hours.
So I don't want to kill myself and thus better relax and sleep now longer.
I am going to fix issue in surefire, then introduce SPI and
surefire-extentions module in my Git branch and invite
Sure, go for it.
On Mar 29, 2015, at 12:46 PM, Tibor Digana tibordig...@apache.org wrote:
@Jason, the Maven performance and memory consumption is important for me as
well.
Can I assign this issue MNG-5669 to JIRA Issues to be reviewed for 3.x?
--
View this message in context:
@Jason, the Maven performance and memory consumption is important for me as
well.
Can I assign this issue MNG-5669 to JIRA Issues to be reviewed for 3.x?
--
View this message in context:
http://maven.40175.n5.nabble.com/3-3-1-Memory-Usage-tp5829534p5830609.html
Sent from the Maven Developers
Do you plan to investigate a fix? If you do, you probably want to assign
the jira to yourself to indicate it is being worked on.
--
Regards,
Igor
On Sun, Mar 29, 2015, at 12:46 PM, Tibor Digana wrote:
@Jason, the Maven performance and memory consumption is important for me
as
well.
Can I
Hi,
I already reported this for 3.2.3
(http://thread.gmane.org/gmane.comp.jakarta.turbine.maven.devel/113979),
provided Igor with an archive containing anything to run validate (I have it
still) and this resulted in https://jira.codehaus.org/browse/MNG-5669.
However, the issue in still
If you tried the staged versions and didn't always notify us after we do the
release we might actually remember to look before it's too late.
I encourage you next release to try the staged versions, or keep reminding us
when someone says there are thinking about doing a release.
On Mar 23,
The main issue is the change to make the model immutable after building and it
exposed an issue where large dependencyManagement sections are re-built over
and over and are not cached properly.
If you want to take a look happy to point you at the code, but it will be
something we'll look at in
Does anyone have a publcly available project (that does not require a
ton of in-house artifacts/private repositories) that reproduce this ?
At one point in time I thought I had such a test case, but it turned
out to be an environmental issue.
Kristian
2015-03-21 15:18 GMT+01:00 Karl Heinz
Hi,
have you pinned all plugins correctly and get no difference in the
plugins version during the different executions?
Have you defined any kind of profiles etc. or memory configurations?
Which JDK are you using? OS is of course interesting as well...
Are you using the exact same machine?
It also seems to be a time-issue.
I would like to see these numbers over, let's say, 10 runs. (OS and JDK
the same of course)
One thing worth investigating is if the buildplan related instances can be
cleaned up.
thanks,
Robert
Op Wed, 18 Mar 2015 11:19:33 +0100 schreef Jörg Schaible
I would recommend trying to flesh out this:
https://github.com/takari/maven-performance-tests
On Mar 21, 2015, at 11:29 AM, Kristian Rosenvold kristian.rosenv...@gmail.com
wrote:
Does anyone have a publcly available project (that does not require a
ton of in-house artifacts/private
Hi,
it seems to get my standard complaint about every new Maven version, but
we're currently stuck to Maven 3.0.5. One reason is the vast memory usage of
any later version.
We have currently ~450 projects in the reactor, now compare the results of a
simple validate:
Maven 3.0.5:
12 matches
Mail list logo
