not sure the unified source directory structure addresses this issue.

 Properties

 maven.user.config.dir (system,default=${user.home}/.m2)
 maven.home            (system,user,default=${user.home}/m2)
 maven.repo.local      (system,user,default=${maven.user.config.dir}/repository)

 We need to define what happens in the when things are not setup correctly

 o ~/.m2 directory does not exist

  </description>
  <url>http://maven.apache.org/</url>
  <issueManagement>
    <system>jira</system>
    <url>http://jira.codehaus.org/browse/MPA</url>
  </issueManagement>
  <ciManagement>
    <system>continuum</system>
    <url>http://maven.zones.apache.org:8080/continuum</url>
    <notifiers>
      <notifier>
        <type>mail</type>
        <configuration>

        <url>https://github.com/junit-team/junit4</url>
      <tag>r4.13.1</tag>
  </scm>
    <issueManagement>
        <system>github</system>
        <url>https://github.com/junit-team/junit4/issues</url>
    </issueManagement>
    <ciManagement>
        <system>travis</system>
        <url>https://travis-ci.org/junit-team/junit4</url>
    </ciManagement>
    <distributionManagement>

*----------+--------------------------------------------+-----------------------+
||         || system level                              || user level 
*----------+--------------------------------------------+-----------------------+
|| POSIX   | <<</etc/mavenrc>>>\

      <archive>http://archive.plexus.codehaus.org/scm</archive>
    </mailingList>
  </mailingLists>
  <issueManagement>
    <system>JIRA</system>
    <url>http://jira.codehaus.org/browse/PLX</url>
  </issueManagement>

  <distributionManagement>
    <repository>
      <id>codehaus.org</id>
      <name>Plexus Central Repository</name>

h3. Plugins

* Execution model
* Metadata model
* Metadata tooling
 ** Metadata extractor
 ** Metadata reader
 ** Metadata writer
 ** Metadata adapter (if required for the target system)
* Maven packaging and lifecycle
* Maven test harness for plugin execution model
* Eclipse IDE tooling for plugin execution model and metadata model

- we also seem to have information like the plugin lifecycle model that's buried inside the maven execution model

  </description>
  <url>http://maven.apache.org/</url>
  <issueManagement>
    <system>jira</system>
    <url>http://jira.codehaus.org/browse/MPA</url>
  </issueManagement>
  <ciManagement>
    <system>continuum</system>
    <url>http://maven.zones.apache.org/continuum</url>
    <notifiers>
      <notifier>
        <type>mail</type>
        <configuration>

  a coordinated offline strategy. In addition, efforts to unite these failing
  behaviors behind a consistent user interface is much, much more difficult if
  the system can't tell whether it has access to the network required by these
  operations.

  Offline mode really means anticipating a lack of network connectivity, and as

  <name>Maven Wagon</name>
  <version>1.0-beta-2</version>
  <description>Tools to manage artifacts and deployment</description>
  <url>http://maven.apache.org/wagon</url>

  <issueManagement>
    <system>jira</system>
    <url>http://jira.codehaus.org/browse/WAGON</url>
  </issueManagement>
  <inceptionYear>2003</inceptionYear>
  <mailingLists>
    <mailingList>
      <name>Maven Wagon User List</name>

      <archive>http://lists.codehaus.org/pipermail/plexus-dev/</archive>
    </mailingList>
  </mailingLists>
  <issueManagement>
    <system>JIRA</system>
    <url>http://jira.codehaus.org/browse/PLX</url>
  </issueManagement>

  <distributionManagement>
    <repository>
      <id>codehaus.org</id>
      <name>Plexus Central Repository</name>