In particular this includes all subpackages. Despite the element name one can also only expose individual classes of a particular package by adding its binary name as value.
          ]]></description>
        </field>
        <field>
          <name>exportedArtifacts</name>
          <version>1.0.0</version>

import org.apache.maven.model.Plugin;
import org.apache.maven.plugin.MojoExecution;
import org.apache.maven.plugin.descriptor.MojoDescriptor;
import org.apache.maven.project.MavenProject;

/**
 * <p>
 * Wraps individual MojoExecutions, containing information about completion status and scheduling.
 * </p>
 * <strong>NOTE:</strong> This class is not part of any public api and can be changed or deleted without prior notice.
 *
 * @since 3.0

import org.apache.maven.plugin.descriptor.MojoDescriptor;
import org.apache.maven.project.MavenProject;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

/**
 * <p>
 * Executes an individual mojo
 * </p>
 * <strong>NOTE:</strong> This class is not part of any public api and can be changed or deleted without prior notice.
 *
 * @since 3.0
 */
@Named
@Singleton
public class MojoExecutor {

import org.apache.maven.api.services.model.PluginConfigurationExpander;
import org.apache.maven.api.xml.XmlNode;

/**
 * Handles expansion of general build plugin configuration into individual executions.
 *
 */
@Named
@Singleton
public class DefaultPluginConfigurationExpander implements PluginConfigurationExpander {

    @Override

import org.apache.maven.api.services.ModelProblemCollector;

/**
 * Handles expansion of general build plugin configuration into individual executions.
 *
 */
public interface PluginConfigurationExpander {

    /**
     * Merges values from general build plugin configuration into the individual plugin executions of the given model.
     *

default implementation. Configuring the Underlying Logging System The basic principle is that the user is totally responsible for the configuration of the underlying logging system. Commons-logging should not change the existing configuration. Each individual Log implementation may support its own configuration properties. These will be documented in the class descriptions for the corresponding implementation class. Finally, some Log implementations (such as the one for Log4J) require an external configuration...

default implementation. Configuring the Underlying Logging System The basic principle is that the user is totally responsible for the configuration of the underlying logging system. Commons-logging should not change the existing configuration. Each individual Log implementation may support its own configuration properties. These will be documented in the class descriptions for the corresponding implementation class. Finally, some Log implementations (such as the one for Log4J) require an external configuration...