)
just completed.
Arun
On Thu, Nov 21, 2013 at 6:11 AM, Tomaž Cerar <tomaz.cerar(a)gmail.com> wrote:
Also looking trough your build log, you might want to upgrade
maven-compiler-plugin to 3.1
it should lower compiler memory footprint and also speedup compile.
--
tomaz
On Thu, Nov 21, 2013 at 2:53 PM, Arun Gupta <arun.gupta(a)gmail.com> wrote:
>
> I was using:
>
> export MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=128m"
>
> and now bumped to:
>
> export MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=256m"
>
> Started another run and will find out.
>
> Arun
>
> On Thu, Nov 21, 2013 at 5:52 AM, Tomaž Cerar <tomaz.cerar(a)gmail.com>
> wrote:
> >
> > On Thu, Nov 21, 2013 at 2:37 PM, Arun Gupta <arun.gupta(a)gmail.com>
> > wrote:
> >>
> >> I've been tinkering with running the Java EE 7 tests on WildFly at:
> >>
> >>
> >>
> >>
https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil...
> >>
> >> There are still some issues with aggregated results and inconsistency
> >> between running them on my machine and Jenkins. But working to resolve
> >> them.
> >
> >
> >
> > You need to increase permgen for your test jobs
> > this is cause currently it fails with "java.lang.OutOfMemoryError:
> > PermGen
> > space"
> >
> > you should probably just tweak maven jvm settings a bit.
> >
>
>
>
> --
>
http://blog.arungupta.me
>
http://twitter.com/arungupta