Can you give us the kind of error messages you got when Jetty fails ?
Jeff
On Tue, Jul 30, 2013 at 5:26 AM, ginger wrote:
> Hello, Maven gurus,
>
> We run into something very bizarre when trying to run some unit tests that
> use a embedded jetty server with surefire and cobertura. It works well
> with our original configuration like
>
>
>
>
>
> org.codehaus.mojo
> cobertura-maven-**plugin
>
> ${maven.test.skip}
>
> 30
> 30
> true
> 55
> 55
> 50
> 50
>
>
>
>
>
> clean
> check
>
>
>
>
>
>
>
>
> org.apache.maven.**plugins
> maven-compiler-**plugin
>
> 1.6
> 1.6
>
>
>
> org.apache.maven.**plugins
> maven-war-plugin
>
> cxf
>
>
>
> org.apache.maven.**plugins
> maven-dependency-**plugin
>
>
> install
> install
>
>
>
>
> org.apache.maven.**plugins
> maven-surefire-**plugin
>
> -Xms512m -Xmx1024m
> -XX:MaxPermSize=512m
> junit:**junit
>
> **/*UnitTest*
> **/*JettyTest*
>
>
>
>
> org.codehaus.mojo
> sonar-maven-**plugin
> 2.0
>
>
>
>
> org.apache.maven.**wagon
> wagon-ssh
> 1.0-beta-6
>
>
>
>
>
> But when I tried to separate the running of UnitTest and JettyTest like
> the following, so UnitTest are run all the time and JettyTests are only run
> in a specific profile,
>
>
>
>
>
>
> org.apache.maven.**plugins
> maven-surefire-**plugin
>
> -Xms512m -Xmx1024m
> -XX:MaxPermSize=512m
> junit:**junit
>
> **/*UnitTest*
>
>
>
>
>
>
>
> org.apache.maven.**plugins
> maven-compiler-**plugin
>
> 1.6
> 1.6
>
>
>
> org.apache.maven.**plugins
> maven-war-plugin
>
> cxf
>
>
>
> org.apache.maven.**plugins
> maven-dependency-**plugin
>
>
> install
> install
>
>
>
>
> org.codehaus.mojo
> sonar-maven-**plugin
> 2.0
>
>
>
>
> org.apache.maven.**wagon
> wagon-ssh
> 1.0-beta-6
>
>
>
>
> and get the JettyTest and Cobertura in a profile called all-test
>
>
>
> all-test
>
>
>
>
> org.apache.maven.**plugins
> maven-surefire-**plugin
>
> -Xms512m -Xmx1024m
> -XX:MaxPermSize=512m
> junit:**junit
>
> **/*UnitTest*
> **/*JettyTest*
>
>
>
>
> org.codehaus.mojo
> cobertura-maven-**plugin
>
> ${maven.test.skip}
>
> 30
> 30
> true
> 55
> 55
> 50
> 50
>
>
>
>
>
> clean
> check
>
>
>
>
>
>
>
>
>
>
> It runs fine in my centos 5.5 x86_64. But if I submit it to centos 5.7
> x86_64, jetty tests are giving me all kinds of errors, like the jetty
> server cannot be initiated right. But with the original configuration,
> jetty tests are OK. I'm so confused. Totally out of clues. Can any one
> please give me some hint/insights? Anything would be deeply appreciated
>
>
--
Jeff MAURY
"Legacy cod
