commit e6dd918478acc38ddb5cce292d5b0953a28e1392
author mparker <mparker> Fri Jul 02 21:56:59 2010 +0000
committer mparker <mparker> Fri Jul 02 21:56:59 2010 +0000
tree a58049558b46a32b9621b7559ddc5c6729f44dc3
parent 08c05c72e002d66f7e47ddbad0f74dcf1d432293

Update build info.

developers/_building.html

diff --git a/developers/_building.html b/developers/_building.html
index 654a1ca..5b96dd7 100644
--- a/developers/_building.html
+++ b/developers/_building.html
@@ -64,7 +64,16 @@
 				<ol>
 								<li>Select Run &rarr; Run Configurations..</li>
 								<li>Select Eclipse Application and click "New Launch Configuration".</li>
-								<li>Use "All Workspace and Enabled Target Plugins.." option. (You can customize this later if desired.)</li>
+								<li>The default "All Workspace and Enabled Target Plugins.." option is fine. If you want to specify individual plugins, you will probably need at least:
+								<uL>
+								<li>org.eclipse.amp.amf.ide</li>
+								<li>org.eclipse.amp.escape.amf.ide</li>
+								<li>org.eclipse.amp.amf.ide</li>
+								<li>org.eclipse.amp.amf.data.editor</li>
+								<li>org.eclipse.amp.amf.paramters.ui</li>
+								<li>org.eclipse.amp.amf.testing.ide</li>
+								<li>org.eclipse.sdk</li>
+								</ul>Then, select the "Add Required Plugins" button.</li>
 								<li>Click the Run button.</li>
 								<li>A new Eclipse application should launch. Note that you can also launch using the Debugger which is
 								helpful for debugging issues with AMP models.</li>