that currently we have information about a project scattered across the project.xml and the
 various properties files. What needs to be done is to encapsulate all of this in the POM.

 Typically users parameterize the use of plugins, or have custom values like ${user.name}
 for use in elements like the <developerConnection/>. It would be idea if we
 could encapsulate everything we need about the project in the POM including

        </field>
        <field>
          <name>filtering</name>
          <version>3.0.0+</version>
          <description>
            Whether resources are filtered to replace tokens with parameterised values or not.
            The values are taken from the {@code properties} element and from the
            properties in the files listed in the {@code filters} element. Note: While the type

 Object, model.Statement); java.util.List getSortedRules(); static void <clinit>(); } org/junit/runners/Parameterized$UseParametersRunnerF.class package org.junit.runners; public abstract interface Parameterized$UseParametersRunnerF extends annotation.Annotation { public abstract Class value(); } org/junit/runners/parameterized/ParametersRunnerFact.class package org.junit.runners.parameterized; public abstract interface ParametersRunnerFact { public abstract org.junit.runner.Runner createRunnerF...