Use the Failsafe plugin, though a separate module is good practice too:
http://maven.apache.org/plugins/maven-failsafe-plugin/
Danny
-Original Message-
From: Clebert Suconic [mailto:clebert.suco...@gmail.com]
Sent: 17 September 2012 14:05
To: Maven Users List
Subject: Re: Improving
Hi,
I was trying to configure a TestNG group exclusion based on profile and finding
the tests weren't being excluded. After checking everything I could think of
and getting nowhere, I checked out the Surefire code and attached a debugger.
I found this must have been broken since TestNG
/SUREFIRE-805)
which actually broke the feature for TestNG (only in 2.11=. You may want to
test surefire 2.10 while we're releasing 2.12, which should be pretty soon.
If it does not work with 2.10, you should file a bug towards surefire.
Kristian
2012/1/25 Danny Thomas danny.tho...@blackboard.com
I explicitly exclude TestNG's Guice 2.0 dependency and it uses 3.0 RC2 very
happily, which is what you're doing anyway by moving the 2.0 jars to the end of
the classpath. I'm also using TestNG's Guice support now it binds all of the
modules at once, it's pretty flexible.
Danny
did? I tried that too but was not
successful. Guice 2 does not show up in the dependency tree anyways, but
Surefire still adds it.
Thanks,
Reinhard
Am 14.02.2011 10:51, schrieb Danny Thomas:
I explicitly exclude TestNG's Guice 2.0 dependency and it uses 3.0 RC2 very
happily, which is what
services which include both a client jar and a
war for the service but we only need 1 execution.
Ron
On 14/12/2010 1:36 AM, Danny Thomas wrote:
Hi,
I'm using the assembly plugin to package my project. I currently have two
assembly descriptors with two executions for my project which generates
Hi,
I'm using the assembly plugin to package my project. I currently have two
assembly descriptors with two executions for my project which generates
distributions of the project for two different audiences:
!-- Client distribution --
execution
idclient/id
