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: 1/20/07 2:24:02 PM
Updated by: Reinhard Pötz
A new version has been created, state: publish
Parts
=====
Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name: (unchanged)
Size: 3165 bytes (previous version: 3255 bytes)
Content diff:
<html>
<body>
--- <h1>TODO </h1>
+++ <h1><img src="daisy:1319"/></h1>
--- <h2><img src="daisy:1319"/></h2>
---
<p>The Cocoon project uses <a
href="http://subversion.tigris.org";>Subversion</a>
for source code version management... details <a href="TODO">here</a>.</p>
--- <h2><img src="daisy:1283"/></h2>
+++ <h1><img src="daisy:1283"/></h1>
<p>The Cocoon project uses Apache <a
href="http://maven.apache.org";>Maven</a>
in several roles:</p>
<ul>
--- <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>
+++ <li>For <strong>Cocoon users</strong>: as the downloader for getting the
+++ artifacts 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
--- (<a href="http://";>details</a>).</li>
+++ for Cocoon, e.g. to run in an instance of the Jetty servlet container
(details).
+++ </li>
<li>For Cocoon <strong><em>application</em> developers</strong> building web
--- 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 frees 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>
+++ apps using Cocoon + custom Java code: it's recommended that you set up your
+++ projects to use Maven as your build tool. This frees 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="daisy:798">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
source
+++ code submission. <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>
+++ you can set up initially <a href="daisy:1159">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>
+++ <h1>Eclipse</h1>
<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
+++ <a href="daisy:1214">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><img src="daisy:1320"/></h2>
+++ <h1><img src="daisy:1320"/></h1>
<p>The Cocoon project uses Atlassian JIRA for bug/issue tracking. Anyone
can
<a href="https://issues.apache.org/jira/browse/COCOON";>browse the
issues</a>.
Anyone can create or comment on an issue too, you just have to
<a href="https://issues.apache.org/jira/secure/Signup!default.jspa";>create a
login</a> on Apache's JIRA first.</p>
--- <h2><img src="daisy:1321"/></h2>
+++ <h1><img src="daisy:1321"/></h1>
<p>The Cocoon project uses Maven
<a href="http://maven.apache.org/continuum/";>Continuum</a> to run its
(7 equal lines skipped)
