<role>Founder</role>
        <role>Release Manager</role>
      </roles>
    </developer>
  </developers>

  <contributors>
    <contributor>
      <name>Martin van dem Bemt</name>
      <email>mvdb@mvdb.com</email>
    </contributor>
  </contributors>

  <dependencies>

    <dependency>
      <groupId>g1</groupId>
      <artifactId>d1</artifactId>
      <version>1.0</version>
      <url>d1-url</url>

sequence of steps, where each step depends on the result of the previous step and we can stop processing as soon as a step fails. These classes provide infrastructure for writing such a sequence. Based on https://github.com/npryce/maybe-java Author: Steve Freeman 2012 http://www.hamcrest.com Nested Class Summary static interface Condition.Step<I,O> Field Summary static org.hamcrest.Condition.NotMatched<java.lang.Object> NOT_MATCHED Method Summary abstract <U> Condition<U> and(Condition.Step<? super T,U>...

plexus-component-api Plexus Component API 1.0-alpha-32 maven-surefire-plugin 2.2 **/Test*.java **/Abstract*.java org.codehaus.plexus plexus-classworlds maven-surefire-report-plugin maven-pmd-plugin maven-javadoc-plugin http://java.sun.com/j2ee/1.4/docs/api http://java.sun.com/j2se/1.5.0/docs/api http://jakarta.apache.org/commons/collections/apidocs-COLLECTIONS_3_0/ http://jakarta.apache.org/commons/dbcp/apidocs/ http://jakarta.apache.org/commons/fileupload/apidocs/ http://jakarta.apache.org/commons/httpclient/apidocs/...

      <organization />
      <roles>
        <role>Developer</role>
      </roles>
    </developer>
    <developer>
      <id>dandiep</id>
      <name>Dan Diephouse</name>
      <email>dan@envoisolutions.com</email>
      <organization>Envoi solutions</organization>
      <roles>
        <role>Developer</role>
      </roles>
    </developer>
    <developer>
      <id>kasper</id>
      <name>Kasper Nielsen</name>

    </dependency>
    <dependency>
      <groupId>org.codehaus.plexus</groupId>
      <artifactId>plexus-interpolation</artifactId>
    </dependency>
    <dependency>
      <groupId>com.fasterxml.woodstox</groupId>
      <artifactId>woodstox-core</artifactId>
    </dependency>
    <dependency>
      <groupId>org.codehaus.woodstox</groupId>
      <artifactId>stax2-api</artifactId>
    </dependency>

    <dependency>
      <groupId>org.eclipse.sisu</groupId>
      <artifactId>org.eclipse.sisu.inject</artifactId>
      <classifier>no_asm</classifier>
    </dependency>
    <dependency>
      <groupId>com.google.inject</groupId>
      <artifactId>guice</artifactId>
      <classifier>classes</classifier>
    </dependency>
    <dependency>
      <groupId>org.ow2.asm</groupId>
      <artifactId>asm</artifactId>

discovery algorithm to select the name of the LogFactory implementation class this application wants to use: Check for a system property named org.apache.commons.logging.LogFactory. Use the JDK 1.3 JAR Services Discovery mechanism (see http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html for more information) to look for a resource named META-INF/services/org.apache.commons.logging.LogFactory whose first line is assumed to contain the desired class name. Look for a properties file named commons-logging.properties...

## GitHub forks?

If you are using GitHub, make a clone of the corresponding repository
mirror and create your pull requests against the main branch:

- Lucene: <https://github.com/apache/lucene>

   |-->
  <pluginGroups>
    <!-- pluginGroup
     | Specifies a further group identifier to use for plugin lookup.
    <pluginGroup>com.your.plugins</pluginGroup>
    -->
  </pluginGroups>

  <!-- TODO Since when can proxies be selected as depicted? -->
  <!-- proxies

      <name>Edwin Punzalan</name>
      <email>epunzalan@mergere.com</email>
      <organization>Mergere</organization>
      <roles>
        <role>Committer</role>
      </roles>
      <timezone>+8</timezone>
    </developer>
    <developer>
      <id>mperham</id>
      <name>Mike Perham</name>
      <email>mperham@gmail.com</email>
      <organization>IBM</organization>
      <roles>