<groupId>org.apache.maven.its.mng3843.child</groupId>
  <artifactId>child-2</artifactId>
  <version>0.2</version>
  <packaging>jar</packaging>

  <developers>
    <developer>
      <name>child-developer</name>
    </developer>
  </developers>

<project>
    <modelVersion>4.0.0</modelVersion>
    <groupId>test</groupId>
    <artifactId>artifact</artifactId>
    <version>1.0</version>

    <developers>
        <developer>
            <organization/>
            <organizationUrl/>
        </developer>
    </developers>

      </roles>
      <timezone>+10</timezone>
    </developer>
    <developer>
      <id>evenisse</id>
      <name>Emmanuel Venisse</name>
      <email>******@****.***</email>
      <organization>ASF</organization>
      <roles>
        <role>PMC Member</role>
      </roles>
      <timezone>+1</timezone>
    </developer>
    <developer>
      <id>kenney</id>
      <name>Kenney Westerhof</name>

        </license>
    </licenses>

    <developers>
        <developer>
            <id>dsaff</id>
            <name>David Saff</name>
            <email>******@****.***</email>
        </developer>
        <developer>
            <id>kcooney</id>
            <name>Kevin Cooney</name>
            <email>******@****.***</email>
        </developer>
        <developer>
            <id>stefanbirkner</id>

the bundle id before installing a new app. If the uninstalled app is the last app by
the developer identity, the device might also remove the permission to run apps from
that developer, and the exec wrapper will fail to install the new app. To avoid that,
install another app with the same developer identity but with a different bundle id.
That way, the permission to install apps is held on to while the primary app is

      <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>developer</organization>
      <organizationUrl>https://devel.org</organizationUrl>
      <roles>
        <role>devel</role>
      </roles>

      <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>developer</organization>
      <organizationUrl>https://devel.org</organizationUrl>
      <roles>
        <role>devel</role>
      </roles>

The process that happens when your API app calls the *external API* is named a "callback". Because the software that the external developer wrote sends a request to your API and then your API *calls back*, sending a request to an *external API* (that was probably created by the same developer).

    <developerConnection>developer-connection</developerConnection>
    <url>repository-url</url>
  </scm>

  <mailingLists>
    <mailingList>
      <name>Maven User List</name>
      <subscribe>subscribe</subscribe>
      <unsubscribe>unsubscribe</unsubscribe>
      <archive>archive</archive>
    </mailingList>
  </mailingLists>

  <developers>
    <developer>
      <name>Jason van Zyl</name>

         * it will be reported as "external". It is up to developer to correctly interpret output (GAV) of issues
         * and realize that in this case he wears two hats:" "user" and "(plugin) developer".
         */
        EXTERNAL
    }

    /**
     * Reports plugin issues applicable to the plugin as a whole.
     * <p>