import org.slf4j.Logger;

/**
 * Provides backwards compatibility with Maven 3.2.3 and earlier. Clients that do not require compatibility with Maven
 * 3.2.3 and earlier are encouraged to use {@link JavaToolchainImpl}.
 * <strong>Note:</strong> This is an internal component whose interface can change without prior notice.
 *
 * @deprecated clients that do not require compatibility with Maven 3.2.3 and earlier should link to

 *   <li>missing artifacts</li>
 *   <li>network/transfer errors</li>
 *   <li>file system errors: permissions</li>
 * </ul>
 *
 * TODO carlos: all these possible has*Exceptions and get*Exceptions methods make the clients too
 *       complex requiring a long list of checks, need to create a parent/interface/encapsulation
 *       for the types of exceptions
 */
@Deprecated
public class ArtifactResolutionResult {

    <description>
      <![CDATA[
      This is a list of attachments to the main artifact produced by building the current POM.
      Attachments are derived works, based on the main build process, such as an ejb-client jar,
      project sources jar, etc.
    ]]></description>
  </expression>
</expressions>

dl war true java false org.apache.maven.artifact.handler.ArtifactHandler ear org.apache.maven.artifact.handler.DefaultArtifactHandl ear true java false org.apache.maven.artifact.handler.ArtifactHandler ejb-client org.apache.maven.artifact.handler.DefaultArtifactHandl ejb-client jar ejb client java true org.apache.maven.artifact.handler.ArtifactHandler rar org.apache.maven.artifact.handler.DefaultArtifactHandl rar java true org.apache.maven.artifact.handler.ArtifactHandler par org.apache.maven.ar...

        <artifactId>jetty</artifactId>
        <version>${jetty.version}</version>
      </dependency>
      <dependency>
        <groupId>org.mortbay.jetty</groupId>
        <artifactId>jetty-client</artifactId>
        <version>${jetty.version}</version>
      </dependency>
      <dependency>
        <groupId>junit</groupId>
        <artifactId>junit</artifactId>
        <version>4.5</version>

*--------------------+---------------+------------+------------+-----------+---------------------+-----------------------+
| <<<ejb-client>>>   | <<<client>>>  | <<<jar>>>  | <<<ejb>>>  | java      | <<<true>>>          |                       |
*--------------------+---------------+------------+------------+-----------+---------------------+-----------------------+

                // j2ee types
                new DefaultType("ejb", Language.JAVA_FAMILY, "jar", null, false, JavaPathType.CLASSES),
                new DefaultType("ejb-client", Language.JAVA_FAMILY, "jar", "client", false, JavaPathType.CLASSES),
                new DefaultType("war", Language.JAVA_FAMILY, "war", null, true),
                new DefaultType("ear", Language.JAVA_FAMILY, "ear", null, true),

    // from the plugin.xml inside a plugin.
    //
    // TODO This whole method could probably removed by injecting lifeCyclePluginAnalyzer straight into client site.
    // TODO But for some reason the whole plexus appcontext refuses to start when I try this.

    public Set<Plugin> getPluginsBoundByDefaultToAllLifecycles(String packaging) {

    public static final String PROJECT_LOCAL_REPO = "project-local-repo";

    private static final Collection<String> COMPILE_PHASE_TYPES = new HashSet<>(
            Arrays.asList("jar", "ejb-client", "war", "rar", "ejb3", "par", "sar", "wsr", "har", "app-client"));

    private static final Logger LOGGER = LoggerFactory.getLogger(ReactorReader.class);

    private final MavenSession session;
    private final WorkspaceRepository repository;

            <![CDATA[
            The type of dependency, that will be mapped to a file extension, an optional classifier, and a few other attributes.
            Some examples are {@code jar}, {@code war}, {@code ejb-client}
            and {@code test-jar}: see <a href="../maven-core/artifact-handlers.html">default
            artifact handlers</a> for a list. New types can be defined by extensions, so this is not a complete list.
            ]]>