extends org.apache.maven.plugin.AbstractMojo { public void TestMojo(); public void execute(); } pom.xml 4.0.0 org.apache.maven.plugins maven-plugin-plugin 0.1 maven-plugin Maven Integration Test Plugin A test plugin to assist testing of Maven core. 2009 maven-core-it file:///${basedir}/repo true true org.apache.maven maven-plugin-api 2.0 . pom.xml src/** src/main/resources src/main/java/org/apache/maven/plugins/coreit/ItMojo.java src/main/java/org/apache/maven/plugins/coreit/ItMojo.java package org....

extends org.apache.maven.plugin.AbstractMojo { public void TestMojo(); public void execute(); } pom.xml 4.0.0 org.apache.maven.plugins maven-resources-plugin 0.1 maven-plugin Maven Integration Test Plugin A test plugin to assist testing of Maven core. 2009 maven-core-it file:///${basedir}/repo true true org.apache.maven maven-plugin-api 2.0 . pom.xml src/** src/main/resources src/main/java/org/apache/maven/plugins/coreit/ItMojo.java src/main/java/org/apache/maven/plugins/coreit/ItMojo.java package org....

~~ specific language governing permissions and limitations
~~ under the License.

 -----
 Introduction
 -----
 Hervé Boutemy
 -----
 2013-07-27
 -----

Maven Core

 Maven Core classes managing the whole build process.

* Reference Documentation

 * {{{./lifecycles.html}lifecycles}} and {{{./default-bindings.html}plugin bindings to <<<default>>> lifecycle}},

import org.apache.maven.api.cli.extensions.CoreExtension;

/**
 * Core extension selector: selects which entries to load from {@link InvokerRequest#coreExtensions()}.
 *
 * @param <C> The context type.
 */
public interface CoreExtensionSelector<C extends LookupContext> {
    /**
     * Selects core extensions to be loaded from list of all sources detected.
     */
    @Nonnull

  <packaging>maven-plugin</packaging>

  <name>Maven Integration Test Plugin</name>
  <description>
    A test plugin to assist testing of Maven core.
  </description>
  <inceptionYear>2009</inceptionYear>

  <distributionManagement>
    <repository>
      <id>maven-core-it</id>
      <url>file:///${basedir}/repo</url>
    </repository>
  </distributionManagement>

  <properties>

  <packaging>maven-plugin</packaging>

  <name>Maven Integration Test Plugin</name>
  <description>
    A test plugin to assist testing of Maven core.
  </description>
  <inceptionYear>2009</inceptionYear>

  <distributionManagement>
    <repository>
      <id>maven-core-it</id>
      <url>file:///${basedir}/repo</url>
    </repository>
  </distributionManagement>

  <properties>

<inherits name="com.google.common.collect.testing.Testing" />
<inherits name="com.google.common.primitives.Primitives" />
<inherits name="com.google.common.testing.Testing" />
<inherits name="com.google.gwt.core.Core" />
<inherits name="com.google.gwt.junit.JUnit" />
<inherits name="com.google.gwt.user.User" />

app.flags = flags

# These symbols appear because we import the python package which
# in turn imports from tensorflow.core and tensorflow.python. They
# must come from this module. So python adds these symbols for the
# resolution to succeed.
# pylint: disable=undefined-variable
del python
del core

#ifndef TENSORFLOW_C_C_OP_REQUIRES_H_
#define TENSORFLOW_C_C_OP_REQUIRES_H_

#include "tensorflow/core/platform/macros.h"

namespace tensorflow {

// Convenience macros for asserting and handling exceptional conditions, for
// C structs, including `TF_OpKernelContext`, `TF_Status`, etc. This is analogus
// to the macros in tensorflow/core/framework/op_requires.h. This is provided
// for plugin OpKernel developer's convenience.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.gwt.core.Core" />
<inherits name="com.google.gwt.user.User" />