* similar to the way Maven configures plugins from the POM, i.e. some configuration like {@code <param>value</param>}
 * is mapped to an equally named property of the bean and converted. The properties of the bean are supposed to either
 * have a public setter or be backed by an equally named field (of any visibility).
 *
 * @since 3.0
 */
public interface BeanConfigurator {

        while (properties.hasNext()) {
            final Map.Entry property = (Map.Entry) properties.next();
            final String key = (String) property.getKey();
            final StringBuilder value = new StringBuilder();
            final Iterator values = ((List) property.getValue()).iterator();
            while (values.hasNext()) {
                value.append(values.next());

    /*
       - The below two ignored files are generated during test execution
       by the test: okhttp/src/test/java/okhttp3/osgi/OsgiTest.java

       - The compressed index.xml file contains a timestamp property which
       changes with every test execution, such that running the test
       actually changes the test classpath itself. This means that it
       can"t benefit from incremental build acceleration, because on every

                                                key="labels.labeltype_name"/></label>
                                        <div class="col-sm-10">
                                            <la:text styleId="name" property="name" styleClass="form-control"/>
                                        </div>
                                    </div>
                                    <div class="form-group row">

                            <la:form action="/admin/searchlist" styleClass="form-inline" method="GET">
                                <div class="form-group">
                                    <la:text styleClass="query form-control" property="q"
                                             title="Search" size="50" maxlength="1000"
                                             placeholder="Type a search query"/>
                                </div>

        </executions>
      </plugin>
    </plugins>
  </build>

  <profiles>
    <profile>
      <id>create-distribution-in-dir</id>
      <activation>
        <property>
          <name>distributionTargetDir</name>
        </property>
      </activation>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>

 defined the maven.multiproject.includes property in any of his properties
 files for the current project. if yes. then I'm able to find projects that
 can be offered to be opened together with the current project.
 problems with the current solution are:
 1. information is duplicate. once in POM's dependencies and once in the
 maven.multiproject.includes property.

                factory.setAttribute(XMLConstants.ACCESS_EXTERNAL_SCHEMA, "");
            } catch (final Exception e) {
                if (logger.isDebugEnabled()) {
                    logger.debug("Failed to set a property.", e);
                }
            }
        }
        try {
            factory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true);
        } catch (final ParserConfigurationException e) {

 * under the License.
 */
package org.apache.maven.configuration;

/**
 * Preprocesses a value from a bean configuration before the bean configurator unmarshals it into a bean property. A
 * common use case for such preprocessing is the evaluation of variables within the configuration value.
 *
 */
public interface BeanConfigurationValuePreprocessor {

    /**

import static java.util.Objects.requireNonNull;

/**
 * A dependency traverser that excludes the dependencies of fat artifacts from the traversal. Fat artifacts are
 * artifacts that have the property {@link MavenArtifactProperties#INCLUDES_DEPENDENCIES} set to
 * {@code true}.
 *
 * @see org.eclipse.aether.artifact.Artifact#getProperties()
 * @see MavenArtifactProperties
 * @since 4.0.0