running sureFire twice in a build

I've run into this a couple of times in my experience with maven2. A single module web project, nothing to complex, just some servlets and a simple data access layer. What I wanted to be able to do was run both unit tests and integration tests both written with JUnit. So initially I started with:

<plugin>
 <artifactId>maven-surefire-plugin</artifactId>
 <configuration>
     <skip>true</skip>
 </configuration>
 <executions>
     <execution>
         <id>integration-test</id>
         <phase>integration-test</phase>
         <goals>
             <goal>test</goal>
         </goals>
         <configuration>
             <skip>false</skip>
         </configuration>
     </execution>
 </executions>
</plugin>

This seemed like at least half the solution. It moves the test run to integration-test, where both the unit test and integration tests run. Not so bad I figured, I worked with this for the last couple of months and it's been bugging me. Last week I came up with:

<plugin>
 <artifactId>maven-surefire-plugin</artifactId>
 <configuration>
     <skip>true</skip>
 </configuration>
 <executions>
     <execution>
         <id>test</id>
         <phase>test</phase>
         <goals>
             <goal>test</goal>
         </goals>
         <configuration>
             <skip>false</skip>
             <excludes>
                 <exclude>**/*IntegrationTest.java</exclude>
             </excludes>                        
         </configuration>
     </execution>
     <execution>
         <id>integration-test</id>
         <phase>integration-test</phase>
         <goals>
             <goal>test</goal>
         </goals>
         <configuration>
             <skip>false</skip>
             <includes>
                 <include>**/*IntegrationTest.java</include>
             </includes>                        
         </configuration>
     </execution>
 </executions>
</plugin>
            
        

It requires that the tests are named correctly, but that isn't such a big deal. So now the test phase runs just the unit tests (named *Test.java) and integration-test runs everything but in two phases, first "test" and second in integration-test.