Hi Amin,
according to head it shouldn't be needed to build core, as it's
currently depending on 3.5.0-Beta-4 :
http://fisheye.jboss.org/browse/Hibernate/search/trunk/pom.xml?r1=18574&r2=18691
Maybe you just need to update? This change is just two days old.
Sanne
2010/2/6 Amin Mohammed-Coleman :
Thanks I'll give that a go!
Cheers
Amin
On 6 Feb 2010, at 07:55, Strong Liu wrote:
> try add this to your .bashrc (or others if you're not using unix-like os)
>
> export MAVEN_OPTS=-Xmx1024m
>
>
> ---
> Best Regards,
>
> Strong Liu
>
>
>
> On Feb 6, 2010, at
try add this to your .bashrc (or others if you're not using unix-like os)
export MAVEN_OPTS=-Xmx1024m
---
Best Regards,
Strong Liu
On Feb 6, 2010, at 3:16 PM, Amin Mohammed-Coleman wrote:
> Hi All
>
> I'm trying to build core and followed the steps mentioned and
Hi All
I'm trying to build core and followed the steps mentioned and I'm getting the
following exception:
Failure executing javac, but could not parse the error:
The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError: Java heap space
a
If you ever have doubts whether some VM parameters are affecting your
test execution, I think you might be able to add a call to
http://java.sun.com/j2se/1.5.0/jcp/beta1/apidiffs/java/lang/management/RuntimeMBean.html#getInputArguments()
to see what VM parameters have been passed to your test.
Hello,
> turns out that MAVEN_OPTS does not help in this case at all. The surefire
> plugin per default uses the forkMode 'once', meaning a new JVM gets created
> for running the tests. Command line arguments passed via MAVEN_OPTS only apply
> for the JVM running the build.
>
> To increase the he
Hi,
turns out that MAVEN_OPTS does not help in this case at all. The surefire
plugin per default uses the forkMode 'once', meaning a new JVM gets created
for running the tests. Command line arguments passed via MAVEN_OPTS only
apply
for the JVM running the build.
To increase the heap size for s
> -Xmx1024 - that's what I used to have, mainly driven by the fact that once
> upon
> a time the docbook plugin needed to work.
>
> Btw, I also have the problem if I just try to run the Envers build.
That's very weird. I just ran all tests, a "clean install" took 1m 30s, even
with default maven
-Xmx1024 - that's what I used to have, mainly driven by the fact that once
upon
a time the docbook plugin needed to work.
Btw, I also have the problem if I just try to run the Envers build.
Have you only recently added more tests? I used to be able to build
everything just fine.
Maybe the test
I have -Xmx1024 but I'm running only Envers tests.
Adam
On Dec 21, 2009, at 4:45 PM, Hardy Ferentschik wrote:
> Hi,
>
> Even with -Xmx2048 it does not work. I keep increasing the memory until
> I reach the limit of my machine. No luck.
>
> What settings are you using?
>
> --Hardy
>
>
> On S
Hi,
Even with -Xmx2048 it does not work. I keep increasing the memory until
I reach the limit of my machine. No luck.
What settings are you using?
--Hardy
On Sat, 19 Dec 2009 07:08:54 -0300, Adam Warski wrote:
> Heh, the obvious thing to do - using Google - gave an answer.
> It's a known pro
Heh, the obvious thing to do - using Google - gave an answer.
It's a known problem when there are many tests:
http://code.google.com/p/testng/issues/detail?id=24
The only solution so far is to increase the memory for Maven.
Adam
On Dec 18, 2009, at 11:45 AM, Hardy Ferentschik wrote:
> Hi,
>
>
Turns out that Idea uses a different classpath (invalid) when running tests so
it didn't read the right log4j.properties.
Maven did, but it didn't help; I test with the 5.10 dependency.
Maybe there's simply too many tests to log info about? ;)
Adam
On Dec 18, 2009, at 2:50 PM, Adam Warski wrot
Maybe it's the huge amount of logs that gets emmited during the tests - the
place where the OOM happens would indicate that (it failed in the same place
when I updated to 5.10).
I tried changing the log4j.properties in the envers module test sources to emit
less logs but I think that some differ
Hi,
I used to have -Xmx1024m for $MAVEN_OPTS and I tried now also -Xmx512.
I also tried different maven versions 2.2.1 and 3.0 alpha 5. All with the
same result - OutOfMemoryError :(
--Hardy
On Fri, 18 Dec 2009 03:50:08 -0300, Adam Warski wrote:
> Hmm, I had this when I upgraded the TestNG
Hmm, I had this when I upgraded the TestNG dependency to 5.10, so I reverted it
back to 5.8 - do you have the latest pom?
Also, my $MAVEN_OPTS are: -Xmx512m.
Adam
On Dec 18, 2009, at 4:24 AM, Hardy Ferentschik wrote:
> Hi,
>
> just wondering whether someone could confirm that the reactor buil
16 matches
Mail list logo
