svn commit: r485067 - /webservices/muse/site/source-code.html

[da...@apache.org]

Author: danj
Date: Sat Dec  9 13:47:04 2006
New Revision: 485067

URL: http://svn.apache.org/viewvc?view=rev&rev=485067
Log:
Instructions for setting up Eclipse workspaces.

Modified:
    webservices/muse/site/source-code.html

Modified: webservices/muse/site/source-code.html
URL: http://svn.apache.org/viewvc/webservices/muse/site/source-code.html?view=diff&rev=485067&r1=485066&r2=485067
==============================================================================
--- webservices/muse/site/source-code.html (original)
+++ webservices/muse/site/source-code.html Sat Dec  9 13:47:04 2006
@@ -126,6 +126,9 @@
 <li>
 <a href="#compatibility">Backwards Compatibility</a>
 </li>
+<li>
+<a href="#eclipse">Eclipse Development</a>
+</li>
 </ul>
 </div>
 
@@ -204,6 +207,40 @@
 each distribution's JavaDoc. Different major versions may cause compilation errors 
 due to API changes. If such changes are made, they will be documented separately 
 in the release notes in order to ease migration.
+</p>
+</div>
+
+
+<a name="N10022"></a><a name="eclipse"></a>
+<h2 class="boxed">Eclipse Development</h2>
+<div class="section">
+<p>
+You can build the individual Muse modules within Eclipse by creating a Java 
+project for each module and downloading the appropriate section of code into 
+each project. The Muse team has tried to make this very easy by creating 
+an entire set of Eclipse projects that you can import into your workspace and 
+that are pre-configured with all of the right Subversion metadata. Please follow 
+the steps below to set up your Eclipse environment with the latest Muse source code:
+<ul>
+<li>Download the <a href="http://ws.apache.org/muse/eclipse/muse-workspaces.zip">Eclipse projects</a>. 
+The .zip file should be extracted to whatever workspace you will use for Muse development.
+<br/></li><br/>
+<li>Select <b>File &gt; Import &gt; Existing Projects into Workspace</b> and traverse to the directory 
+that has all of the Muse Eclipse projects. Click <b>Select All</b> and then <b>Finish</b>.
+<br/></li><br/>
+<li>You now have all of the projects you need, but no code! To download the code, highlight all 
+of the projects, right click, and select <b>Team &gt; Update</b>. This will issue the Subversion 
+command to download any new code from the repository (in this case, that means all of the code).
+<br/></li><br/>
+<li>You're all done! Whenever you want to build an individual module into a JAR file, you can 
+right click on the <b>/build/build.jardesc</b> file in each project and select <b>Create JAR</b>. 
+This will allow you to compile your code without having to run Maven or the entire Muse build process.
+<br/><br/>
+You can also keep up-to-date on the latest changes to the code base by performing the Subversion 
+update at any time. Doing this at least once per day ensures that you're always working off the 
+same code as the development team.
+<br/></li><br/>
+</ul>
 </p>
 </div>
 



---------------------------------------------------------------------
To unsubscribe, e-mail: muse-commits-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-commits-help@ws.apache.org