specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>maven</groupId>
  <artifactId>project-which-needs-directory-alignment</artifactId>
  <name>Maven</name>
  <version>1.0-beta-9</version>
  <inceptionYear>2001</inceptionYear>
  <description>Description</description>
  <url>http://maven.apache.org/</url>

specific language governing permissions and limitations
under the License.
-->

<project>

  <extend>../project-which-needs-directory-alignment.xml</extend>

  <parent>
    <groupId>maven</groupId>
    <artifactId>project-which-needs-directory-alignment</artifactId>
    <version>1.0-beta-9</version>
  </parent>

specific language governing permissions and limitations
under the License.
-->

<project>

  <extend>project-which-needs-directory-alignment.xml</extend>

  <parent>
    <groupId>maven</groupId>
    <artifactId>project-which-needs-directory-alignment.xml</artifactId>
    <version>1.0-beta-9</version>
  </parent>

  <groupId>maven</groupId>
  <artifactId>maven-foo</artifactId>

Michael Osipov <******@****.***> 1416744059 +0100

  // Returns the device which created the handle.
  virtual const char* DeviceName(Status* status) const = 0;
  // Returns the device where the tensor was placed.
  virtual const char* BackingDeviceName(Status* status) const = 0;
  // Returns the device type which created the handle.
  virtual const char* DeviceType(Status* status) const = 0;
  // Returns the device ID which created the handle.

During the development of a plugin we would want to make it easy for a developer to create a plugin which means we would allow the direct use of a POM to state the dependencies of a given plugin and any tooling we created would be responsible for turning the dependency information in the POM into plugin metadata which described the dependencies of the plugin.

than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form.  A
"Major Component", in this context, means a major essential component

 *       typically because the type forbids nullable type arguments: For example, {@code
 *       ImmutableList.get} returns {@code E}, but that value is never {@code null}. (Accordingly,
 *       {@code ImmutableList} is declared to forbid {@code ImmutableList<@Nullable String>}.)
 *   <li>methods whose return type is a type variable but which can return {@code null} regardless

 *       typically because the type forbids nullable type arguments: For example, {@code
 *       ImmutableList.get} returns {@code E}, but that value is never {@code null}. (Accordingly,
 *       {@code ImmutableList} is declared to forbid {@code ImmutableList<@Nullable String>}.)
 *   <li>methods whose return type is a type variable but which can return {@code null} regardless

 *       typically because the type forbids nullable type arguments: For example, {@code
 *       ImmutableList.get} returns {@code E}, but that value is never {@code null}. (Accordingly,
 *       {@code ImmutableList} is declared to forbid {@code ImmutableList<@Nullable String>}.)
 *   <li>methods whose return type is a type variable but which can return {@code null} regardless