<description>
            A set of dependencies which the plugin requires in order to function. This enables the plugin to function
            independently of its POM (or at least to declare the libraries it needs to run).
          </description>
        </field>
      </fields>
      <codeSegments>
        <codeSegment>
          <version>2.0.0+</version>
          <code><![CDATA[

    <!--
      | We may potentially want to export these, but right now I'm not sure that anything Guice specific needs
      | to be made available to plugin authors. If we find people are getting fancy and want to take advantage of
      | Guice specifics we can expose that later. Really some testing needs to be done to see full hiding
      | of Guice has any impact on what we may categorize as a standard JSR-330 based Tesla/Maven plugin.

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>

          <type>String</type>
        </field>
        <field>
          <name>description</name>
          <version>3.0.0+</version>
          <description>A detailed description of the project, used by Maven whenever it needs to
            describe the project, such as on the website. While this element can be specified as
            CDATA to enable the use of HTML tags within the description, it is discouraged to allow

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>

   |
   | Default: ${user.home}/.m2/repository
  <localRepository>/path/to/local/repo</localRepository>
  -->

  <!-- interactiveMode
   | This will determine whether maven prompts you when it needs input. If set to false,
   | maven will use a sensible default value, perhaps based on some other setting, for
   | the parameter in question.
   |
   | Default: true
  <interactiveMode>true</interactiveMode>
  -->

      </activation>
      <properties>
        <!--
            Some tests need reflective access to the internals of these packages. It is only the
            tests themselves and not the code being tested that needs that access, though there's no
            obvious way to ensure that.

            We could consider arranging things so that only the tests we know need this would get

      <name>ActivationFile</name>
      <version>1.0.0</version>
      <description><![CDATA[
        This is the file specification used to activate a profile. The missing value will be a the location
        of a file that needs to exist, and if it doesn't the profile must run.  On the other hand exists will test
        for the existence of the file and if it is there will run the profile.
      ]]></description>
      <fields>
        <field>

      <name>ActivationFile</name>
      <version>1.0.0+</version>
      <description>
        This is the file specification used to activate a profile. The missing value will be the location
        of a file that needs to exist, and if it doesn't the profile must run.  On the other hand exists will test
        for the existence of the file and if it is there will run the profile.
      </description>
      <fields>
        <field>