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

[da...@apache.org]

Author: danj
Date: Sat Jan  6 09:34:51 2007
New Revision: 493516

URL: http://svn.apache.org/viewvc?view=rev&rev=493516
Log:
Updating Eclipse/SVN instructions and providing a new muse-workspaces.zip file that does not contain SVN info. Given 
the Subclipse interface for Eclipse 3.1/3.2, I don't think we need to make SVN projects for people - there is an 
option to make projects out of each module/directory. The new .zip file will have an overlay that includes the right 
classpath and lib directory.

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=493516&r1=493515&r2=493516
==============================================================================
--- webservices/muse/site/source-code.html (original)
+++ webservices/muse/site/source-code.html Sat Jan  6 09:34:51 2007
@@ -217,30 +217,40 @@
 <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:
+each project. 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.
+<li>Install <a href="http://subclipse.tigris.org/">Subclipse</a>, if you haven't already. This will allow you to 
+work with Subversion from within Eclipse.
 <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>.
+<li>Select <b>New > Project > SVN > Checkout Project from SVN</b>. Create a new repository location 
+using the anonymous SVN URL listed above. If you're a new committer, you can use the committer URL 
+and provide your Apache credentials.
 <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/>
+<li>Subclipse will show you the current contents of the Muse directory in Apache's SVN repository. 
+Traverse to <b>/trunk/modules</b> and select all of the modules you want to work on. Click <b>Next</b>.
+<br/></li><br/>
+<li>Select the option to create a Java project for each directory (module) and click <b>Finish</b>. 
+Subversion will now download all of the Muse code into the appropriate projects.
+<br/></li><br/>
+<li>Now you have all of the code, but it doesn't compile! Subclipse created Java projects for you, but 
+you don't have the right classpath or dependencies to build each module. Fortunately, the Muse team has 
+created a set of directories that contain the .classpath, .project, and library files needed to fix this 
+problem. Just <a href="http://ws.apache.org/muse/eclipse/muse-workspaces.zip">download this .zip file</a> 
+to your Eclipse workspace directory and extract it; the directories in the .zip file will overlay the 
+ones created by Subclipse and overwite the existing .classpath and .project files.
+<br/></li><br/>
+<li>Highlight all of the Muse projects in your workspace, right click, and select <b>Refresh</b>. This 
+will bring the new project and library files into view and cause Eclipse to re-build your workspace. 
+It may take a while because many of the projects depend on others and Eclipse needs time to determine 
+the proper build order.
+<br/></li><br/>
+</ul>
 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.
+same code as the development team. Just highlight all of the Muse projects in your workspace, right click, 
+and select <b>Team > Update</b>.
 <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