I am pretty sure somebody provided an example project that showed memory
increase in Maven 3.2.x some time last year iirc. Could have been direct
email, not 100% sure. From what I remember, the problem was triggered by
specific way to reference parent pom, this is why only few projects are
affected
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/100
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
You still do not have any publicly available project to reproduce this ?
Every time you complain about this I have compared 3.0.5 and 3.3.3,
and every time I get the same result; 3.3.3 might have about 10% more
allocated objects overall when compared to 3.0.5. There is something
about your project
It's not completely ugly, but it does entangle dependencies further which I
view as ugly.
There is an existing todo above this code to move the validation to a
different module, so I believe this will all get removed at that time
On Thursday, July 23, 2015, Benson Margulies wrote:
> If this cha
If this change is so ugly, why are there no comments explaining the ugly?
On Jul 23, 2015 10:48 AM, "jvanzyl" wrote:
> Github user jvanzyl commented on the pull request:
>
> https://github.com/apache/maven/pull/60#issuecomment-124129817
>
> I'm out in the middle of nowhere, but i'll canc
Hi,
>
= %< =
$ MAVEN_OPTS=-Xmx4096m mvn validate
Why are you setting to 4 GiB ?
but for Maven 3.0.5 you only setting to 1.5 GiB ?
Back to M305 now, -Xmx1500m is enough ...
Kind regards
Karl Heinz Marbaise
GitHub user pkozelka opened a pull request:
https://github.com/apache/maven/pull/61
fix release profile to use source:jar-no-fork instead of source:jar
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pkozelka/maven pk/fix-release
Github user atanasenko closed the pull request at:
https://github.com/apache/maven/pull/59
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/60#issuecomment-124129817
I'm out in the middle of nowhere, but i'll cancel the vote, test and
re-roll once I'm back to civilization.
---
If your project is set up for it, you can reply to this em
Github user stephenc commented on the pull request:
https://github.com/apache/maven/pull/60#issuecomment-124128970
After no comments against merging this and with @ifedorenko saying go for
it I decided to merge... if people object they can revert it out. I am not in
love with this fix
Github user asfgit closed the pull request at:
https://github.com/apache/maven/pull/60
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enable
Jörg Schaible wrote:
> Hi Anton,
>
> Anton Tanasenko wrote:
>
>> Hi Jörg,
>>
>> The error message you posted says that java is unable to allocate 500mb
>> of heap. The machine you were running it on didn't have that much
>> available at the time.
>
> If you think it is normal that I have to cl
Hi Anton,
Anton Tanasenko wrote:
> Hi Jörg,
>
> The error message you posted says that java is unable to allocate 500mb of
> heap. The machine you were running it on didn't have that much available
> at the time.
If you think it is normal that I have to close Eclipse just to call "mvn
validate
Hi Jörg,
The error message you posted says that java is unable to allocate 500mb of
heap. The machine you were running it on didn't have that much available at
the time.
2015-07-23 15:47 GMT+03:00 Jörg Schaible :
> Hi folks,
>
> M335 needs even more memory (see also
> http://thread.gmane.org/gma
Hi folks,
M335 needs even more memory (see also
http://thread.gmane.org/gmane.comp.jakarta.turbine.maven.devel/116287).
Maven 3.3.x is for me now simply unusable at all:
= %< =
$ MAVEN_OPTS=-Xmx4096m mvn validate
[INFO] Scanning for projects...
Downloading:
That's what I do in such case.
Den 22 jul 2015 17:56 skrev "Stephen Connolly" <
stephen.alan.conno...@gmail.com>:
> Do we not just rename the version number?
>
> On 22 July 2015 at 15:55, Paul Benedict wrote:
>
> > All,
> >
> > I noticed that the next set of unresolved tickets are always assigned
16 matches
Mail list logo