o cleanup

PR:
Obtained from:
Submitted by:
Reviewed by:


git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@162628 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jason van Zyl 2004-04-08 02:45:58 +00:00
parent 1bea7e4e00
commit c5ccb6de89
6 changed files with 2 additions and 688 deletions

View File

@ -1,4 +0,0 @@
We need to try and stay compatible with the changes in Maven 1.x as far as
the POM goes:
- ${basedir} has been removed as a requirement for paths. It is implicit.

View File

@ -1,19 +0,0 @@
Goal 1
------
Be able to bootstrap marvin by simply building itself with the compiler
component. This simple goal assumes the functioning of the ProjectBuilder
and its cooperation with the compiler plugin which is control by Werkz
selecting the goals and using the OGNL glue to select the parts of the
components that need to be executed.
Goal 2
------
Building from Goal 1 we will add testing with SureFire.
Goal 3
------
Come up with a coherent plan for reporting and create a checkstyle component
for the first test report to generate.

View File

@ -1,10 +0,0 @@
I have tried to separate each of the components by concern. We have the
following:
maven:
This is the actual maven thingy itself. Currently is very small but the
central notion is that a goal is a mapping to a method in a component. You
can also hand off parameters too. I am using OGNL to bind goals to bits to
execute in components. There is a simple test that displays the mapping. I
will incorporate Werkz in here to handle everything.

View File

@ -1,6 +0,0 @@
#!/bin/sh
( cd maven-model ; maven clean jar:install )
( cd maven-model-xpp3 ; maven clean jar:install )
( cd maven-project ; maven clean jar:install )
( cd maven-core ; maven clean jar:install )

View File

@ -1,648 +0,0 @@
<?xml version="1.0"?>
<document>
<properties>
<author email="dev@modello.codehaus.org">Maven Development Team</author>
<title>Maven Model Documentation</title>
</properties>
<body>
<section name="Model">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>extend</td>
<td>
The location of the parent project, if one exists. Values from the parent project will be
the default for this project if they are left unspecified.
The path may be absolute, or relative to the current project.xml file.
</td>
</tr>
<tr>
<td>modelVersion</td>
<td>The version of this model you are using.</td>
</tr>
<tr>
<td>groupId</td>
<td>The primary grouping for your project.</td>
</tr>
<tr>
<td>artifactId</td>
<td>The identifier used when generating the artifact for your project.</td>
</tr>
<tr>
<td>name</td>
<td>Human readable name of the project.</td>
</tr>
<tr>
<td>version</td>
<td>The currently version of the project.</td>
</tr>
<tr>
<td>shortDescription</td>
<td>An abbreviated description of the project.</td>
</tr>
<tr>
<td>description</td>
<td>
A detailed description of the project. This element is
usually specified as CDATA to enable the use of HTML tags
within the description. This description is used to
generate the <a href="plugins/site/index.html">front page</a>
of the project's web site.
</td>
</tr>
<tr>
<td>type</td>
<td>The type of artifact produced by the project.</td>
</tr>
<tr>
<td>url</td>
<td>The URL where the project can be found.</td>
</tr>
<tr>
<td>logo</td>
<td>The logo for the project.</td>
</tr>
<tr>
<td>issueTrackingUrl</td>
<td>The URL where the issue tracking system used by the project can be found.</td>
</tr>
<tr>
<td>inceptionYear</td>
<td>The year the project started.</td>
</tr>
<tr>
<td>gumpRepositoryId</td>
<td>Hint for the gump continuous integration build system.</td>
</tr>
<tr>
<td>siteAddress</td>
<td>The FQDN of the host where the project's site is uploaded.</td>
</tr>
<tr>
<td>siteDirectory</td>
<td>The directory on the site host where site documentation is placed when the site is uploaded.</td>
</tr>
<tr>
<td>distributionSite</td>
<td>The FQDN of the host where the project's artifacts are uploaded.</td>
</tr>
<tr>
<td>distributionDirectory</td>
<td>The directory on the distribution host where artifacts are placed when uploaded.</td>
</tr>
<tr>
<td>mailingLists</td>
<td>The mailing lists for the project.</td>
</tr>
<tr>
<td>developers</td>
<td>
This element describes all of the developers associated with a
project. Each developer is described by a
<code>developer</code> element, which is then described by
additional elements (described below). The auto-generated site
documentation references this information.
</td>
</tr>
<tr>
<td>contributors</td>
<td>
This element describes all of the contributors associated with a
project who are not developers. Each contributor is described by a
<code>contributor</code> element, which is then describe by additional
elements (described below). The auto-generated site documentation
references this information.
</td>
</tr>
<tr>
<td>dependencies</td>
<td>
This element describes all of the dependencies associated with a
project. Each dependency is described by a
<code>dependency</code> element, which is then described by
additional elements (described below).
</td>
</tr>
<tr>
<td>licenses</td>
<td>
This element describes all of the licenses for this project. Each license is described by a
<code>license</code> element, which is then describe by additional
elements (described below). The auto-generated site documentation
references this information. Projects should only list the license(s) that
applies to the project and not the licenses that apply to dependencies.
</td>
</tr>
<tr>
<td>versions</td>
<td>The released versions of the project.</td>
</tr>
<tr>
<td>branches</td>
<td>The SCM branches create for the project.</td>
</tr>
<tr>
<td>packageGroups</td>
<td>Package groups required for complete javadocs.</td>
</tr>
<tr>
<td>reports</td>
<td>
This element includes the specification of reports to be
included in a Maven-generated site. These reports will be run
when a user executes <code>maven site</code>. All of the
reports will be included in the navigation bar for browsing in
the order they are specified.
</td>
</tr>
<tr>
<td>repository</td>
<td>Specification for the SCM use by the project.</td>
</tr>
<tr>
<td>build</td>
<td>Information required to build the project.</td>
</tr>
<tr>
<td>organization</td>
<td>
This element describes various attributes of the organziation to
which the project belongs. These attributes are utilized when
documentation is created (for copyright notices and links).
</td>
</tr>
</table>
</p>
</section>
<section name="Branch">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>tag</td>
<td>
The branch tag in the version control system
(e.g. cvs) used by the project for the source
code associated with this branch of the
project.
</td>
</tr>
</table>
</p>
</section>
<section name="Build">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>nagEmailAddress</td>
<td>
An address to which notifications regarding the status of builds
for this project can be sent. This is intended for use by tools
which do unattended builds, for example those providing for
continuous integration. Currently this is used by the
<a href="build-file.html#maven:gump-descriptor">maven:gump-descriptor</a>
target.
</td>
</tr>
<tr>
<td>sourceDirectory</td>
<td>
This element specifies a directory containing the source
of the project. The generated build system will compile
the source in this directory when the project is built.
The path given is relative to the project descriptor.
</td>
</tr>
<tr>
<td>unitTestSourceDirectory</td>
<td>
This element specifies a directory containing the unit test
source of the project. The generated build system will
compile these directories when the project is being tested.
The unit tests must use the JUnit test framework.
The path given is relative to the project descriptor.
</td>
</tr>
<tr>
<td>aspectSourceDirectory</td>
<td>
This element specifies a directory containing Aspect
sources of the project. The generated build system will
compile the Aspects in this directory when the project is
built if Aspects have been enabled (see the <a
href="plugins/aspectj/goals.html">Aspectj goals</a> document).
The path given is relative to the project descriptor.
</td>
</tr>
<tr>
<td>sourceModifications</td>
<td>
This element describes all of the sourceModifications associated with a
project. Each source modification is described by a
<code>sourceModification</code> element, which is then described by
additional elements (described below). These modifications are used
to exclude or include various source depending on the environment
the build is running in.
</td>
</tr>
<tr>
<td>unitTest</td>
<td>This element specifies unit tests associated with the project.</td>
</tr>
<tr>
<td>resources</td>
<td>
This element describes all of the resources associated with a project or unit tests.
Each resource is described by a resource element, which is then described by additional
elements (described <a href="#resource">below</a>). These resources are used to
complete the jar file or to run unit test.
</td>
</tr>
</table>
</p>
</section>
<section name="Contributor">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>name</td>
<td>The full name of the contributor.</td>
</tr>
<tr>
<td>email</td>
<td>The email address of the contributor.</td>
</tr>
<tr>
<td>url</td>
<td>The URL for the homepage of the contributor.</td>
</tr>
<tr>
<td>organization</td>
<td>The organization to which the contributor belongs.</td>
</tr>
<tr>
<td>roles</td>
<td>
The roles the contributor plays in the project. Each role is
describe by a <code>role</code> element, the body of which is a
role name.
</td>
</tr>
<tr>
<td>timezone</td>
<td>
The timezone the contributor is in. This is a number in the range -14 to 14.
</td>
</tr>
</table>
</p>
</section>
<section name="Dependency">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>groupId</td>
<td>
The project group that produced the dependency, e.g. <code>geronimo</code>.
</td>
</tr>
<tr>
<td>artifactId</td>
<td>
The unique id for an artifact produced by the project group, e.g.
<code>germonimo-jms</code>
</td>
</tr>
<tr>
<td>version</td>
<td>
The version of the dependency., e.g. <code>3.2.1</code>
</td>
</tr>
<tr>
<td>url</td>
<td>
This url will be provided to the user if the jar file cannot be downloaded
from the central repository.
</td>
</tr>
<tr>
<td>artifact</td>
<td>the description</td>
</tr>
<tr>
<td>type</td>
<td>
Other known and recognised dependency types are:
<code>ejb</code> and <code>plugin</code>.
</td>
</tr>
<tr>
<td>properties</td>
<td>
Properties about the dependency. Various plugins allow you to
<code>mark</code> dependencies with properties. For example the
<a href="plugins/war/index.html">war</a> plugin looks for a
<code>war.bundle</code> property, and if found will include the dependency
in <code>WEB-INF/lib</code>. For example syntax, check the war plugin docs.
</td>
</tr>
</table>
</p>
</section>
<section name="Developer">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>id</td>
<td>The username of the developer.</td>
</tr>
</table>
</p>
</section>
<section name="License">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>name</td>
<td>The full legal name of the license.</td>
</tr>
<tr>
<td>url</td>
<td>The official url for the license text.</td>
</tr>
<tr>
<td>distribution</td>
<td>
The primary method by which this project may be distributed.
<dl>
<dt>repo</dt>
<dd>may be downloaded from the Maven repository</dd>
<dt>manual</dt>
<dd>user must manually download and install the dependency.</dd>
</dl>
</td>
</tr>
<tr>
<td>comments</td>
<td>the description</td>
</tr>
</table>
</p>
</section>
<section name="MailingList">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>name</td>
<td>The name of the mailing list.</td>
</tr>
<tr>
<td>subscribe</td>
<td>
The email address or link that can be used to subscribe to the mailing list.
If this is an email address, a <code>mailto:</code> link will automatically be created when
the documentation is created.
</td>
</tr>
<tr>
<td>unsubscribe</td>
<td>
The email address or link that can be used to unsubscribe to
the mailing list. If this is an email address, a
<code>mailto:</code> link will automatically be created
when the documentation is created.
</td>
</tr>
<tr>
<td>archive</td>
<td>The link to a URL where you can browse the archive.</td>
</tr>
</table>
</p>
</section>
<section name="Organization">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>name</td>
<td>The full name of the organization.</td>
</tr>
<tr>
<td>url</td>
<td>The URL to the organization's home page.</td>
</tr>
<tr>
<td>logo</td>
<td>
The URL to the organization's logo image. This can be an URL relative
to the base directory of the generated web site,
(e.g., <code>/images/org-logo.png</code>) or an absolute URL
(e.g., <code>http://my.corp/logo.png</code>). This value is used
when generating the project documentation.
</td>
</tr>
</table>
</p>
</section>
<section name="PackageGroup">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>title</td>
<td>the description</td>
</tr>
<tr>
<td>packages</td>
<td>the description</td>
</tr>
</table>
</p>
</section>
<section name="PatternSet">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>includes</td>
<td>the description</td>
</tr>
<tr>
<td>excludes</td>
<td>the description</td>
</tr>
</table>
</p>
</section>
<section name="Repository">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>connection</td>
<td>
The source configuration management system URL
that describes the repository and how to connect to the
repository. This is used by Maven when <a
href="plugins/dist/index.html">building versions</a>
from specific ID.
</td>
</tr>
<tr>
<td>developerConnection</td>
<td>
Just like connection, but for developers, i.e. this scm connection
will not be read only.
</td>
</tr>
<tr>
<td>url</td>
<td>The URL to the project's browsable CVS repository.</td>
</tr>
</table>
</p>
</section>
<section name="Resource">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>directory</td>
<td>
Describe the directory where the resource is stored.
The path may be absolute, or relative to the project.xml file.
</td>
</tr>
<tr>
<td>targetPath</td>
<td>
Describe the resource target path. For example, if you want that resource
appear into a specific package (<code>org.apache.maven.messages</code>), you must specify this
element with this value : <code>org/apache/maven/messages</code>
</td>
</tr>
<tr>
<td>filtering</td>
<td>Describe if resources are filtered or not.</td>
</tr>
</table>
</p>
</section>
<section name="SourceModification">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>className</td>
<td>
If the class with this name can <strong>not</strong> be
loaded, then the includes and excludes specified below
will be applied to the contents of the
<a href="#sourceDirectory">sourceDirectory</a>
</td>
</tr>
<tr>
<td>property</td>
<td>the description</td>
</tr>
</table>
</p>
</section>
<section name="UnitTest">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>resources</td>
<td>the description</td>
</tr>
</table>
</p>
</section>
<section name="Version">
<p>
<table>
<tr>
<th>Element</th>
<th>Description</th>
</tr>
<tr>
<td>name</td>
<td>
The external version number under which this release was distributed. Examples include:
<code>1.0</code>, <code>1.1-alpha1</code>, <code>1.2-beta</code>, <code>1.3.2</code> etc.
</td>
</tr>
<tr>
<td>tag</td>
<td>
The name given in the version control system (e.g. cvs) used by the project for the source
code associated with this version of the project.
</td>
</tr>
<tr>
<td>id</td>
<td>
A unique identifier for a version. This ID is
used to specify the version that <a href="plugins/dist/index.html"><code>maven:dist</code></a> builds.
</td>
</tr>
</table>
</p>
</section>
</body>
</document>

View File

@ -10,7 +10,8 @@
<gumpRepositoryId>jakarta</gumpRepositoryId>
<description></description>
<shortDescription>Java Project Management Tools</shortDescription>
<url>http://maven.apache.org</url>
<organization>
<name>Apache Software Foundation</name>
<url>http://www.apache.org/</url>