~~ KIND, either express or implied.  See the License for the
~~ specific language governing permissions and limitations
~~ under the License.

 -----
 Introduction
 -----
 Vincent Siveton
 -----
 2006-11-04
 -----

Maven 4 API - Immutable Toolchains Model

 This is strictly the immutable model for Maven toolchains in <<<org.apache.maven.api.toolchain>>> package.

~~ KIND, either express or implied.  See the License for the
~~ specific language governing permissions and limitations
~~ under the License.

 -----
 Introduction
 -----
 Jason van Zyl
 Vincent Siveton
 Hervé Boutemy
 -----
 2011-06-12
 -----

Maven 4 API - Immutable Maven Model

~~ KIND, either express or implied.  See the License for the
~~ specific language governing permissions and limitations
~~ under the License.

 -----
 Introduction
 -----
 Vincent Siveton
 -----
 2006-11-04
 -----

Maven 4 API - Immutable Settings Model

 This is strictly the immutable model for Maven settings in <<<org.apache.maven.api.settings>>> package.

Copyright (c) 2015 Vincent Batts, Raleigh, NC, USA

All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice,

******@****.*** ASF PMC Member +1 jdcasey John Casey ******@****.*** ASF PMC Member -5 kenney Kenney Westerhof ******@****.*** Neonics PMC Member +1 trygvis Trygve Laugstol ******@****.*** ASF PMC Member +1 vmassol Vincent Massol ******@****.*** ASF PMC Member +1 vsiveton Vincent Siveton ******@****.*** ASF Committer -5 The Apache Software License, Version 2.0 http://www.apache.org/licenses/LICENSE-2.0.txt repo scm:svn:http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0/maven-plugin-api...

      <organization>ASF</organization>
      <roles>
        <role>PMC Member</role>
      </roles>
      <timezone>+1</timezone>
    </developer>
    <developer>
      <id>vmassol</id>
      <name>Vincent Massol</name>
      <email>******@****.***</email>
      <organization>ASF</organization>
      <roles>
        <role>PMC Member</role>
      </roles>
      <timezone>+1</timezone>
    </developer>

    given-names: Benoit
  - family-names: Sutskever
    given-names: Ilya
  - family-names: Talwar
    given-names: Kunal
  - family-names: Tucker
    given-names: Paul
  - family-names: Vanhoucke
    given-names: Vincent
  - family-names: Vasudevan
    given-names: Vijay
  - family-names: Viégas
    given-names: Fernanda
  - family-names: Vinyals
    given-names: Oriol
  - family-names: Warden
    given-names: Pete

    </developer>
    <developer>
      <id>vmassol</id>
      <name>Vincent Massol</name>
      <email>******@****.***</email>
      <organization>ASF</organization>
      <roles>
        <role>PMC Member</role>
      </roles>
      <timezone>+1</timezone>
    </developer>
    <developer>
      <id>vsiveton</id>
      <name>Vincent Siveton</name>
      <email>******@****.***</email>

      <organization>ASF</organization>
      <roles>
        <role>PMC Member</role>
      </roles>
      <timezone>+1</timezone>
    </developer>
    <developer>
      <id>vmassol</id>
      <name>Vincent Massol</name>
      <email>******@****.***</email>
      <organization>ASF</organization>
      <roles>
        <role>PMC Member</role>
      </roles>
      <timezone>+1</timezone>
    </developer>

 for use in elements like the <developerConnection/>. It would be idea if we
 could encapsulate everything we need about the project in the POM including
 plugin parameters and anything else.

 We once had a document that Vincent and I agreed upon and I was about to
 implement it and then I disappeared for 8 months so it never came to pass.

 So I guess it's important to figure out what people are using properties