example illustrates the typical declaration and use of a logger that is named (by convention) after the calling class: import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; public class Foo { static Log log = LogFactory.getLog(this.class); public void foo() { ... try { if (log.isDebugEnabled()) { log.debug("About to do something to object " + name); } name.bar(); } catch (IllegalStateExceptio e) { log.error("Something bad happened to " + name, e); } ... } Unless you configure...

                RequestTrace.newChild(null, "foo").newChild("bar").newChild("baz");
        assertThat(ReverseTreeRepositoryListener.lookupCollectStepData(doesNotHaveIt), nullValue());

        final CollectStepData data = mock(CollectStepData.class);

        RequestTrace haveItFirst = RequestTrace.newChild(null, data)
                .newChild("foo")
                .newChild("bar")
                .newChild("baz");

          <groupId>org.apache.maven.its.plugins</groupId>
          <artifactId>maven-it-plugin-b</artifactId>
          <version>1.0-SNAPSHOT</version>
            <executions>
              <execution>
                <id>foo</id>
                <goals>
                  <goal>a</goal>
                </goals>
              </execution>
            </executions>
        </plugin>
      </plugins>
    </pluginManagement>

     * </ul>
     * Example filter expression: {@code "h(5);s;e(org.foo:bar:1)} will cause: ranges are filtered for "top 5" (instead
     * full range), snapshots are banned if root project is not a snapshot, and if range for {@code org.foo:bar} is
     * being processed, version 1 is omitted.
     *
     * @since 4.0.0
     */

foo...

foo...

foo...

foo...

foo...

foo...