A document has been updated:
http://cocoon.zones.apache.org/daisy/documentation/1276.html
Document ID: 1276
Branch: main
Language: default
Name: Other tools that we use (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 12/5/06 1:34:29 AM
Updated by: Mark Lundquist
A new version has been created, state: draft
Parts
=====
Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name: (unchanged)
Size: 2488 bytes (previous version: 1524 bytes)
Content diff:
(9 equal lines skipped)
<h2><img src="daisy:1283"/> Maven</h2>
--- <p>Cocoon uses <a href="http://maven.apache.org";>Maven</a> in several
roles:</p>
+++ <p>The Cocoon project uses <a href="http://maven.apache.org";>Maven</a> in
+++ several roles:</p>
<ul>
--- <li>For <strong>Cocoon users</strong>: as the downloader for getting the
--- artifacts that constitute the Cocoon binary distributions. These artifacts
--- include:</li>
+++ <li>For <strong>Cocoon users</strong>: as the downloader for
+++ <a href="http://";>getting the artifacts</a> that constitute the Cocoon
binary
+++ distributions. These artifacts include:</li>
<ul>
<li>Cocoon jars</li>
<li>Dependent jars</li>
(7 equal lines skipped)
<ul>
<li>Also for <strong>Cocoon users</strong>: optionally, as the
deployer/launcher
--- for Cocoon, e.g. to run in an instance of the Jetty servlet container.</li>
+++ for Cocoon, e.g. to run in an instance of the Jetty servlet container
+++ (<a href="http://";>details</a>).</li>
<li>For Cocoon <strong><em>application</em> developers</strong> building web
--- apps using Cocoon + custom Java code: it's recommended that you set up your
--- projects to use Maven as your build tool. This saves you from having to
deal
--- with all the usual low-level build infrastructure issues of classpaths, jar
--- dependencies and versions, etc. and lets you get on with the coding!</li>
--- <li>For <strong>Cocoon developers</strong>: as the build tool for building
--- Cocoon (all, or parts of) from the source code.</li>
+++ apps using Cocoon + custom Java code: it's recommended that you
+++ <a href="http://";>set up your projects</a> to use Maven as your build tool.
+++ This saves you from having to deal with all the usual low-level build
+++ infrastructure issues of classpaths, jar dependencies and versions, etc. and
+++ lets you get on with the coding!</li>
+++ <li>For <strong>Cocoon developers</strong>: as the build tool for
+++ <a href="http://";>building Cocoon</a> (all, or parts of) from the source
code.
+++ You are a Cocoon developer if you are working on a patch or other
+++ <a href="TODO">source code submission</a>. <strong><em>Note</em></strong>:
+++ Cocoon users / application developers should never need to build Cocoon
from the
+++ source code. It should be sufficient to specify Cocoon artifacts in your
+++ project's Maven
+++ <a href="http://maven.apache.org/pom.html#What%20is%20the%20POM?";>POM</a>,
which
+++ you can set up initially <a href="TODO">using a Maven archetype</a>.</li>
</ul>
+++ <p class="note">Maven 2.0.4 or greater is required for all of these
tasks.</p>
+++
<h2>Eclipse</h2>
+++ <p>A lot of Cocoon developers like to use the
+++ <a href="http://eclipse.org";>Eclipse</a> IDE, so the Cocoon build sets up
+++ <a href="http://";>Cocoon as an Eclipse project</a>. However, you don't
have to
+++ use Eclipse to develop with or on Cocoon. You can get by with nothing but a
+++ text editor and Maven.</p>
+++
<h2>Jira</h2>
<h2>Continuum</h2>
(3 equal lines skipped)
