Kabir,
try this:
<profile>
<id>onlyOneSurefireExecution.basic.profile</id>
<activation><property><name>test</name></property></activation>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<executions>
<execution><id>basic-integration-default-
full.surefire</id><phase>test</phase></execution>
<execution><id>basic-integration-default-
web.surefire</id><phase>none</phase></execution>
<execution><id>basic-
integration-2nd.surefire</id><phase>none</phase></execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
It works for me on basic/pom.xml.
Peter
On Tuesday, December 06, 2011 15:01:32 Kabir Khan wrote:
Not sure, it used to be possible to do it the way I put in.
I've put it back to what we used to have by commenting out the
onlyOneSurefireExecution profiles from smoke and basic. It will try to run
the test for each execution, i.e. full and web. However full is done
first, so tests should pass there. The web execution might fail if the
test targets the full profile.
On 6 Dec 2011, at 13:03, David Bosschaert wrote:
> I thought you'd always pass in the test's bare name (without the
> package), e.g.:
>
> mvn clean install -Dtest=ParseAndMarshalModelsTestCase
>
>
> Cheers,
>
> David
>
> On 06/12/2011 12:42, Kabir Khan wrote:
>> It seems the latest commit to the testsuite now breaks the ability to do
>> cd testsuite/integration/smoke
>> mvn clean install
>> -Dtest=org.jboss.as.test.smoke.embedded.parse.ParseAndMarshalModelsTest
>> Case _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev