A document has been updated:
http://cocoon.zones.apache.org/daisy/documentation/1214.html
Document ID: 1214
Branch: main
Language: default
Name: How to mount the Cocoon 2.2 projects in Eclipse (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 1/20/07 1:35:38 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: 1506 bytes (previous version: 1569 bytes)
Content diff:
<html>
<body>
--- <p>After checking out Cocoon 2.2, see the <a href="daisy:798">Quickstart
--- page</a>, you can mount the projects in Eclipse.</p>
+++ <p>After following the <a href="daisy:798">Working with Cocoon 2.2 from
+++ trunk</a> page you can mount the projects in Eclipse.</p>
<p>From the directory where you installed Cocoon trunk, we refer to it as
--- /trunk, run mvn eclipse:clean first to remove any left over eclipse files.
Then
--- run mvn eclipse:eclipse.</p>
+++ /trunk, run</p>
--- <p>Next go to eclipse, and make sure you haven't got trunk mounted as a
project
+++ <pre>mvn eclipse:clean
+++ </pre>
+++
+++ <p>first to remove any left over eclipse files. Then run</p>
+++
+++ <pre>mvn eclipse:eclipse</pre>
+++
+++ <p>This creates <tt>classpath</tt> and <tt>.project</tt> files for each
module.
+++ </p>
+++
+++ <p>Next start Eclipse and make sure you haven't got trunk mounted as a
project
already. Also remove <tt>.classpath</tt> and <tt>.project</tt> files
possibly
--- remaining in /trunk from a previous project mount. Do
File-Import->Existing
--- projects into workspace, then point to your /trunk directory and it should
--- detect the newly created blocks as projects.</p>
+++ remaining in <tt>/trunk</tt> from a previous project mount. Do
+++ <em>File-Import->Existing</em> projects into workspace, then point to
your
+++ <tt>/trunk</tt> directory and it should detect the newly created blocks as
+++ projects.</p>
<p class="note">Note that you need to declare the M2_REPO classpath
variable in
--- your workspace, it should point to your local m2 repository.</p>
+++ your workspace, it should point to your local m2 repository. The Maven
eclipse
+++ plugin offers a goal for this purpose: <tt>mvn eclipse:add-maven-repo
+++ -Dworkspace=[path-to-your-local-maven-repo]</tt></p>
--- <p>You can also get Eclipse to download the sources of the dependent
libraries
--- and attach them to the jars in Eclipse :</p>
+++ <p>You can also get Eclipse to download the sources of dependent libraries
and
+++ attach them to the jars in Eclipse :</p>
--- <pre>$ mvn -Declipse.downloadSources=true eclipse:eclipse</pre>
+++ <pre>$ mvn -DdownloadSources=true eclipse:eclipse</pre>
--- <p>For further information about the maven eclipse plugin visit
--- <tt>http://maven.apache.org/plugins/maven-eclipse-plugin/</tt>.</p>
+++ <p>For further information about the Maven Eclipse plugin visit
+++ <a
href="http://maven.apache.org/plugins/maven-eclipse-plugin/";>http://maven.apache.org/plugins/maven-eclipse-plugin/</a>.
+++ </p>
--- <p class="fixme">Note below should be evaluated and either removed if
untrue or
--- incorporated in the text above.</p>
---
--- <p class="note">Normally it would have been sufficient to just run <tt>mvn
--- eclipse:clean eclipse:eclipse </tt>but a bug in the plugin prevents it from
--- generating correct eclipse project references during a reactor build if the
--- projects are not installed during the same run.</p>
---
</body>
</html>
