I thinks the asignee stuff got mixed up, im not involved in the maven plugin development.. :)
On Mon, Nov 18, 2013 at 2:45 PM, Marco Miller <[email protected]> wrote: > Hi Mads, > > You might want to review this other related thread, > in case anything in there could help: > > https://groups.google.com/forum/#!topic/jenkinsci-dev/P_KSh9xVBOg > -entitled "maven-plugin tests not running or..?". > > Cheers, > Marco. > > > On Sunday, November 17, 2013 7:03:32 AM UTC-5, hrmohr wrote: >> >> Hi, >> >> I’ve made a simple patch that adds the parsed project version as >> environment variables: >> >> https://github.com/jenkinsci/maven-plugin/pull/11 >> >> But the test seems to fail. I have run the tests on three different >> systems now, and they all fail but at different times/tests. It looks like >> a problem with memory as the error message in the build is “Maven JVM >> terminated unexpectedly with exit code 137” >> >> https://jenkins.ci.cloudbees.com/job/plugins/job/maven-plugin/37 >> >> Can anyone please help me out here? >> >> Cheers, Mads. >> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- *Mads NielsenConsultantPraqma A/S* *Tel: +45 50 98 18 09Mail: [email protected] <[email protected]>web: www.praqma.net <http://www.praqma.net/>* -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
