+ Make sure you have a [GitHub account](https://github.com/signup/free).
+ If you're planning to implement a new feature, it makes sense to discuss your changes
  on the [dev list](https://maven.apache.org/mailing-lists.html) first.
  This way you can make sure you're not wasting your time on something that isn't
  considered to be in Apache Maven's scope.

[maven-home]: https://maven.apache.org/
[maven-download]: https://maven.apache.org/download.cgi
[users-list]: https://maven.apache.org/mailing-lists.html
[dev-ml-list]: https://www.mail-archive.com/dev@maven.apache.org/
[code-style]: http://maven.apache.org/developers/conventions/code.html
[core-it]: https://maven.apache.org/core-its/core-it-suite/

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

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

     |       anything, you could just leave off the <value/> inside the activation-property.
     |
    <profile>
      <id>env-dev</id>

      <activation>
        <property>
          <name>target-env</name>
          <value>dev</value>
        </property>
      </activation>

      <properties>
        <tomcatPath>/path/to/tomcat/instance</tomcatPath>
      </properties>

(http://www.apache.org/). This product includes software developed by ThoughtWorks (http://www.thoughtworks.com). This product includes software developed by javolution (http://javolution.org/). This product includes software developed by Rome (https://rome.dev.java.net/). about.html in archive lib/org.eclipse.sisu.inject-0.3.5.jar http://www.w3.org/1999/xhtml Content-Type text/html; charset=ISO-8859-1 About org.eclipse.sisu.inject EN-US About org.eclipse.sisu.inject November 5, 2013 License The Eclipse Foundation...

            branch=${GITHUB_REF#refs/heads/}
          fi
          if [ $branch != "master" ]; then
            git ls-remote https://github.com/$user/$repo.git | grep "refs/heads/${branch}$" > /dev/null
            if [ $? -eq 0 ]; then
              echo "Found a branch \"$branch\" in fork \"$user/$repo\", configuring this for the integration tests to be run against."
              target_branch=$branch

java.util.Map); } META-INF/maven/org.codehaus.plexus/plexus-utils/pom.xml 4.0.0 org.codehaus.plexus plexus-utils Plexus Common Utilities 1.0.4 dev@plexus.codehaus.org irc 6667 irc.codehaus.org #plexus 2001 Plexus Developer List http://lists.codehaus.org/mailman/listinfo/plexus-dev http://lists.codehaus.org/mailman/listinfo/plexus-dev http://lists.codehaus.org/pipermail/plexus-dev/ jvanzyl Jason van Zyl ******@****.*** Zenplex Developer Release Manager kaz Pete Kazmier Developer jtaylor James Taylor ******@****.***...

        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"));
        assertEquals("developer@", pom.getValue("developers[1]/email"));

            <type>String</type>
            <multiplicity>*</multiplicity>
          </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>