* load into the UI - having packed or unpacked plugins, and positioning resources if necessary -
 * maven can work out of the classloader, nexus plugins probably couldn't give the js and image
 * resources
 *
 * We need to look at Maven, and Nexus as use cases and figure out what each of them needs to be
 * able to do
 *

  <bannerLeft>
    <name>${project.name}</name>
    <src>https://maven.apache.org/images/apache-maven-project.png</src>
    <href>https://maven.apache.org/</href>
  </bannerLeft>

  <bannerRight>
    <src>https://maven.apache.org/images/maven-logo-black-on-white.png</src>
    <href>https://maven.apache.org/</href>
  </bannerRight>

  <skin>

      <url>siteDistributionUrl</url>
    </site>
  </distributionManagement>

  <organization>
    <name>Apache Software Foundation</name>
    <url>http://apache.org/</url>
    <logo>/images/jakarta-logo-blue.gif</logo>
  </organization>

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

      <url>childSiteDistributionUrl</url>
    </site>
  </distributionManagement>

  <organization>
    <name>Apache Software Foundation</name>
    <url>http://apache.org/</url>
    <logo>/images/jakarta-logo-blue.gif</logo>
  </organization>

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