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.

a bit of fun with collections

A while ago a friend introduced me to hamcrest matchers and soon after that I started looking in to how I could start to use these to make working with collections. I've spent a little while working with dynamic languages such as groovy, ruby and python and they have got under my skin. In the java world you just don't have the flexiblity of fancy closures and chained method calls.

In order to satisfiy my craving for collection tools, what I really want to do is what this guy claims to be able to do. I first looked at Sam Newman's hamcrest-collections project, it's good, but it didn't do what I really wanted completely.

So in true if it wasn't invented here style I've written my own collections library.

http://code.google.com/p/logicalpractice-collections/

It's not 100% complete, but it does allow you to do some quite clever stuff:

smiths = select(from(people).getLastName(), equalToIgnoringCase("smith"));

Give it a go and let me know what you think.