If you plan to contribute on a regular basis, please consider filing a [contributor license agreement][cla].

Making Trivial Changes
----------------------

For changes of a trivial nature to comments and documentation, it is not always
necessary to create a new ticket in JIRA.  In this case, it is appropriate to
start the first line of a commit with '(doc)' instead of a ticket number.

Additional Resources

            properties.put("license." + i + ".name", license.getName());
            properties.put("license." + i + ".url", license.getUrl());
            properties.put("license." + i + ".comments", license.getComments());
            properties.put("license." + i + ".distribution", license.getDistribution());
        }

        result.setProperties(properties);

        setArtifactProperties(result, model);

  </organization>
  <licenses>
    <license>
      <name>project-license</name>
      <url>https://project.url/license</url>
      <distribution>repo</distribution>
      <comments>free</comments>
    </license>
  </licenses>

  <developers>
    <developer>
      <id>dev</id>
      <name>project-developer</name>
      <email>developer@</email>
      <url>https://developer</url>

  </organization>
  <licenses>
    <license>
      <name>project-license</name>
      <url>https://project.url/license</url>
      <distribution>repo</distribution>
      <comments>free</comments>
    </license>
  </licenses>

  <developers>
    <developer>
      <id>dev</id>
      <name>project-developer</name>
      <email>developer@</email>
      <url>https://developer</url>

    -->
    <prop0>A <![CDATA[ Test ]]> Project<![CDATA[ ]]>Property</prop0>

    <!--
    This checks the coalescing of CHARACTERS events that are interleaved with comments. Note that inner whitespace
    formed by whitespace-only events must be retained.
    -->
    <prop1><!-- X -->That's<!-- X --> <!-- X -->a<!-- X --> <!-- X -->test!<!-- X --></prop1>

    <!--

        assertEquals("https://project.url/license", pom.getValue("licenses[1]/url"));
        assertEquals("repo", pom.getValue("licenses[1]/distribution"));
        assertEquals("free", pom.getValue("licenses[1]/comments"));

        assertEquals(1, ((List<?>) pom.getValue("developers")).size());
        assertEquals("dev", pom.getValue("developers[1]/id"));
        assertEquals("project-developer", pom.getValue("developers[1]/name"));

          </association>
        </field>
      </fields>
      <comment>We could probably have a specific element for a dev mailing list for things like CI,
        and maybe even a specific element for the user and scm mailing lists. Then leave the more
        lose structure for any other type of mailing list.</comment>
      <codeSegments>
        <codeSegment>
          <version>4.0.0+</version>

    </mailingList>
    <mailingList>
      <name>Commons User List</name>
      <subscribe>commons******@****.***</subscribe>
      <unsubscribe>commons******@****.***</unsubscribe>
      <archive>http://nagoya.apache.org/eyebrowse/SummarizeList?listName=commons******@****.***</archive>
    </mailingList>

b7de43bb310eb1dbfd00a34cec30500fa13cb577  /home/projects/maven/repository-staging/to-ibiblio/maven2/commons-logging/commons-logging/1.0.3/commons-logging-1.0.3.pom...

    </mailingList>
    <mailingList>
      <name>Maven Commits List</name>
      <subscribe>commits******@****.***</subscribe>
      <unsubscribe>commits******@****.***</unsubscribe>
      <archive>http://mail-archives.apache.org/mod_mbox/maven-commits</archive>
      <otherArchives>
        <otherArchive>http://www.mail-archive.com/commits@maven.apache.org</otherArchive>