RAT (Release Audit Tool) results

The following document contains the results of RAT (Release Audit Tool).

*****************************************************
Summary
-------
Notes: 2
Binaries: 2
Archives: 0
Standards: 21

Apache Licensed: 17
Generated Documents: 1

JavaDocs are generated and so license header is optional
Generated files do not required license headers

3 Unknown Licenses

*******************************

Archives (+ indicates readable, $ unreadable): 

 
*****************************************************
  Files with AL headers will be marked L
  Binary files (which do not require AL headers) will be marked B
  Compressed archives will be marked A
  Notices, licenses etc will be marked N
  GEN   build.xml
  N     LICENSE.txt
  N     NOTICE.txt
  AL    pom.xml
  AL    project.properties
 !????? project.xml
  AL    src/share/org/apache/commons/mapper/Mapper.java
  AL    src/share/org/apache/commons/mapper/MapperAdapter.java
  AL    src/share/org/apache/commons/mapper/MapperException.java
  AL    src/share/org/apache/commons/mapper/MapperFactory.java
  AL    src/share/org/apache/commons/mapper/MapperFactoryEvent.java
  AL    src/share/org/apache/commons/mapper/MapperFactoryListener.java
  AL    src/share/org/apache/commons/mapper/ObjectNotFoundException.java
  AL    src/share/org/apache/commons/mapper/UniqueFieldAlreadyExistsException.java
  AL    src/share/org/apache/commons/mapper/util/ObjectFactory.java
  B     src/site/resources/images/logo.png
  AL    src/site/site.xml
  AL    src/test/org/apache/commons/mapper/MapperFactoryTest.java
  AL    src/test/org/apache/commons/mapper/TestMapper.java
  AL    src/test/org/apache/commons/mapper/TestMapperFactoryListener.java
  AL    src/test/org/apache/commons/mapper/util/ObjectFactoryTest.java
  B     xdocs/images/logo.png
 !????? xdocs/index.xml
  AL    xdocs/navigation.xml
 !????? xdocs/todo.xml
 
 *****************************************************
 Printing headers for files without AL header...
 
 
 =======================================================================
 ==project.xml
 =======================================================================
 <?xml version="1.0"?>
<project>
  <extend>../commons-build/sandbox-project.xml</extend>
  <name>Commons Mapper</name>
  <id>commons-mapper</id>
  <currentVersion>0.7-dev</currentVersion>

  <logo>/images/logo.png</logo>
  
  <inceptionYear>2003</inceptionYear>
  <package>org.apache.commons.mapper</package>

  <shortDescription>Commons Mapper</shortDescription>

  <description>
    Mapper is a thin abstraction layer around a project's chosen data 
    mapping technology.
  </description>

  <developers>

    <developer>
      <name>David Graham</name>
      <id>dgraham</id>
      <email>dgraham@apache.org</email>
      <organization></organization>
    </developer>

  </developers>
  
  <dependencies>

    <dependency>
      <id>junit</id>
      <version>3.8.1</version>
      <url>http://www.junit.org/</url>
    </dependency>
    
  </dependencies>

  <build>
    <sourceDirectory>src/share</sourceDirectory>
    <unitTest>
      <includes>
        <include>**/*Test.java</include>
      </includes>
    </unitTest>
  </build>
</project>

 =======================================================================
 ==xdocs/index.xml
 =======================================================================
 <?xml version="1.0"?>

<document>

 <properties>
   <title>Data Mapping Abstraction Component</title>
 </properties>

<body>

<section name="Mapper: Data Mapping Abstraction Component">

<p>
Most Java applications must store data to a data store whether it's XML files or
a relational database.  Changes to the mapping technology should be transparent
to the rest of the application allowing changes to be localized in the mapping
layer.
</p>

<p>
Commons Mapper is a thin abstraction layer around a project's chosen data mapping
technology.  It allows the developer to vary the mapping technique behind
this layer (often combining several technologies) so that the rest of the 
application doesn't change.  Technologies such as these can be used to map 
Java objects to a data store:
</p>

<ul>
<li>
    <a href="http://java.sun.com/products/jdbc/">JDBC</a> -Using 
    <a href="http://commons.apache.org/dbutils/">Apache Commons DbUtils</a> 
    will make JDBC coding significantly easier.
</li>
<li><a href="http://java.sun.com/products/jdo/">JDO</a></li>
<li><a href="http://java.sun.com/products/ejb/">EJB</a></li>
<li><a href="http://www.hibernate.org/">Hibernate</a></li>
<li><a href="http://www.ibatis.com/">iBatis</a></li>
<li>XML</li>
</ul>

<p>
The purpose of Mapper is similar to Commons Logging.  It isn't a mapping technology
itself, it merely exposes common functionality of other mapping APIs.
</p> 

<p>
Commons Mapper is based on the Data Mapper pattern presented in "Patterns of 
Enterprise Application Architecture" by Martin Fowler.
</p>


 =======================================================================
 ==xdocs/todo.xml
 =======================================================================
 <?xml version="1.0"?>

<document>
  <properties>
    <title>TODO</title>
  </properties>

  <body>
    <section name="TODO"> 
      <p>
        The following is a list of items that need to be completed in
        Mapper.  Contributions are welcome!.
      </p>
      
<table border="1">

  <tr>
    <th>Action Item</th>
    <th>Volunteer</th>
  </tr>

  <tr>
    <td>
        <strong>Documentation</strong> - Provide more examples and a basic 
        User's Guide information in a <code>package.html</code> file.
    </td>
    <td align="center"></td>
  </tr>

</table>

    </section>
  </body>
</document>